Respect an 'after_widget' field to control the order of dependencies

[cpsievert]

See also rstudio/htmltools#76

[jcheng5]

I was going to suggest adding a separate field into the widget object (in addition to dependencies) for dependencies that are prerequisites. But are there cases where you have a prerequisite dependency that isn't known until runtime? (I.e. can't go into the yaml)

[cpsievert]

Yeah. IIRC, that was a roadblock for plotly/plotly.R#411 since mathjax needed to appear before the plotly.js bundle.

[jjallaire]

Another way to solve this is to just forgo YAML dependencies entirely and define all of them in the order required in the dependencies argument.

…

On Thursday, February 2, 2017, Carson ***@***.***> wrote: Yeah. IIRC, that was a roadblock for plotly/plotly.R#411 <plotly/plotly.R#411> since mathjax needed to appear before the plotly.js bundle. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#259 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAGXx-XgFcAjUC16LmJe-rH12Kk2eljRks5rYqEogaJpZM4L17Aq> .

[cpsievert]

@jjallaire it seems as though forgoing yaml dependencies entirely can lead to weird loading issues (they differ in certain contexts?) -- see plotly/plotly.R#1033. Any idea on the best way to proceed?

[jjallaire]

I am unsure about how YAML dependencies would differ from explicitly specified ones. @ramnathv or @jcheng5 any idea?

[ramnathv]

@jjallaire @jcheng5 I think the issue is that htmlwidgets always looks for a YAML file containing dependencies. We can update it to check for a YAML file and fetch dependencies only if it contains one. This should solve the problem encountered. I will start a new branch with the fix so @cpsievert can try it out.