Let's be very careful in recommending anything to our users as our bikeshed require implementation is no where close to what most people consider is "require.js".
Also we should definitely document what is/isn't supported by our require. No async loading, for example. I'll create a JIRA ticket to document that stuff in the README - anywhere else that documentation should exist you guys think? On 12-02-22 10:46 AM, "Brian LeRoux" <[email protected]> wrote: >> - our require.js adds a "define.remove()" function which no one else >> implements. I'm happy with that, but we should probably make the tests >> sensitive to it - only do the "remove" tests if "define.remove()" is >>present > >+1 > >> - issues w/almond and requirejs not throwing exceptions when modules are >> multiply defined or missing for require(). I've noted this issue with >> almond before, and there's an open bug at almond for it. Seems like >> requirejs is also not doing this. For this reason alone, I'd recommend >> folks not use almond or requirejs as difficult-to-diagnose failures will >> occur if, for some reason, a required module is absent. > > >So we *can* support alternate loaders but we'd recommend just using >https://github.com/callback/callback-js/blob/master/lib/require.js ??
