Missing dependency when building a module that contains context sensitive require

[sprabhal]

When a module containing a context-sensitive require as mentioned in ​https://dojotoolkit.org/reference-guide/1.7/loader/amd.html#context-sensitive-require is built, it results in a missing dependency error during runtime. Everything works fine in the non-built version.

I did see a comment "require must not have relative mids" in util/build/transforms/depsScan.js. Does that mean context-sensitive require can never be built.

[ben hockey]

most likely you do not have require as a dependency in your module

define(['require'], function (require) {
    var foo = require('./foo'),
        bar = require('./bar');

    // ...
});

can you provide a sample of the code that fails?

[sprabhal]

define([
	"require",
	"dojo/_base/declare"
], function (require, declare) {
	return declare(null, {
		constructor: function () {
			//constructor
		},
		
		foo: function () {
			require([
			     "./foo",
			     "./bar"
			], function (foo, bar) {
				var fooCopy = foo;
				var barCopy = bar;
				//some operation
			});
		}
	});
});

[sprabhal]

define([
        "require",
        "dojo/_base/declare"
], function (require, declare) {
        return declare(null, {
                constructor: function () {
                        //constructor
                },
                
                foo: function () {
                        require([
                             "./foo",
                             "./bar"
                        ], function (foo, bar) {
                                var fooCopy = foo;
                                var barCopy = bar;
                                //some operation
                        });
                }
        });
});

Replying to neonstalwart:

most likely you do not have require as a dependency in your module

define(['require'], function (require) {
    var foo = require('./foo'),
        bar = require('./bar');

    // ...
});

can you provide a sample of the code that fails?

[dylan]

If this is still an issue, it's kind of a big one.

Can we review and fix for 1.9, if it's an issue?

[ben hockey]

this is working as designed. using require that way is how you lazy-load other layers after a build. leaving those dependencies out is supposed to happen. if they need to be in the same layer then add them as dependencies in the call to define for this module.