Build process rewrites define(..) to an invalid form

[djmitche]

I'm working on including moment.js in my app as a Dojo package. This works fine from source, but when I build the app, something in the build process rewrites moment.js as follows:

moment/moment.js

@@ -1206 +1206 @@
     }
     /*global define:false */
     if (typeof define === "function" && define.amd) {
-        define("moment", [], function () {
+        define("moment/moment", "moment", [], function () {
             return moment;
         });
     }

Which is too many arguments for define. This seems to happen with optimization enabled, but the above example is with optimize: ''.

[djmitche]

Changing the source line to

define([], function() {

fixes this, so it looks like dojo is just blindly prepending the mid to the define invocation.

[Rawld Gill]

Search for insertAbsMids in http://dojotoolkit.org/reference-guide/1.8/build/qref.html#build-qref and you'll see that there is a switch that controls if absolute module ids are automatically inserted (also documented in the above reference).

You can check the value of this build knob by running a build with the "--check" command line argument. If it is not what you want, you can set it either in a profile or directly on the command line (--insertAbsMids 0).

Using absolute module ids is highly discouraged. However, for some backcompat programs, it is necessary.