You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Just a thought, but it would be cool to expose the "global"s of include files wrapped in a closure so you don't have to chuck everything on window for bindings to work.
In .go files I guess this would maybe look something like js.Binding.Call("hello") scoped to the closure instead of polluting global.
The text was updated successfully, but these errors were encountered:
tj
changed the title
Scope *.inc.js files
Scope *.inc.js files to prevent global pollution
Feb 20, 2017
Hmm realizing now that the js include files are not a fantastic solution for a larger number of dependencies, since you have to produce stand-alone builds of NPM modules it ends up producing a lot of duplicate dependencies.
Uh oh!
There was an error while loading. Please reload this page.
Just a thought, but it would be cool to expose the "global"s of include files wrapped in a closure so you don't have to chuck everything on
window
for bindings to work.In .go files I guess this would maybe look something like
js.Binding.Call("hello")
scoped to the closure instead of polluting global.The text was updated successfully, but these errors were encountered: