gehan
commented
11 years ago It's just this bit that it misses out, the define here right at the bottom of the file.
In other libraries cram seems to pick defines like this up..@
// some AMD build optimizers, like r.js, check for specific condition patterns like the following:
if (typeof define == 'function' && typeof define.amd == 'object' && define.amd) {
// Expose Lo-Dash to the global object even when an AMD loader is present in
// case Lo-Dash was injected by a third-party script and not intended to be
// loaded as a module. The global assignment can be reverted in the Lo-Dash
// module via its `noConflict()` method.
window._ = _;
// define as an anonymous module so, through path mapping, it can be
// referenced as the "underscore" module
define(function() {
return _;
});
}
unscriptable
cram's parser needs to be more robust. It get's confused by several of the crazy things lodash does internally.