Stefan,
While it is not straight forward to have to do something like var _ = require(“modules/underscore/ underscore.js”)._; the extra cost is only about manually exposing the needed module (the ._ at the end of the require) while the gained advantage is huge since it allows loading any library under any module name without polluting the namespace of the original scope.
Although we firmly believe in the advantage of avoiding conflicts between different libraries (or different versions of the same library) we’re also working on a feature that would allow automatically loading some variables into the main scope along with more advanced classloaders. Stay connected to blog.scriptr.io for information relating to new features we release.
Hope this helps and don’t hesitate to send any questions.
Julien Mrad
Scriptr.io
It works thank you
It worked for me. Thanks a lot!