Entirely earnest question -- wouldn't it be disadvantageous to create a library using Require.js? AFAIK you can't compile out the Require.js dependency. Even Almond.js leaves this cruft. Shouldn't you design consumable libraries to be entirely clear of runtime dependency mapping/loading?
As a part of my workflow, libraries are built at compile time by a Grunt task. These modules are concatenated based on an externally specified dependency graph. The end result is no Require.js in the final production code.
I'm kind of against R.js as it adds complexity at runtime. Has anyone found a way around this? If it were compile time overhead alone, I wouldn't be so opposed.
Comments
Entirely earnest question -- wouldn't it be disadvantageous to create a library using Require.js? AFAIK you can't compile out the Require.js dependency. Even Almond.js leaves this cruft. Shouldn't you design consumable libraries to be entirely clear of runtime dependency mapping/loading?
As a part of my workflow, libraries are built at compile time by a Grunt task. These modules are concatenated based on an externally specified dependency graph. The end result is no Require.js in the final production code.
I'm kind of against R.js as it adds complexity at runtime. Has anyone found a way around this? If it were compile time overhead alone, I wouldn't be so opposed.