You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
// The modules that you would like to set as window properties
288
+
// An array of strings (module names)
289
+
globalModules: [],
290
+
// Determines if all of your local modules are stored in a single global object (helps with scoping in certain cases)
291
+
globalObject:false,
292
+
// Determines the name of your global object that stores all of your global modules
293
+
globalObjectName:'amdclean',
281
294
// All esprima API options are supported: http://esprima.org/doc/
282
295
esprima: {},
283
296
// All escodegen API options are supported: https://github.com/Constellation/escodegen/wiki/API
@@ -310,6 +323,14 @@ __Why are define() method placeholder functions inserted into my source?__
310
323
311
324
- This is the default behavior of r.js when a module(s) is not wrapped in a define() method. Luckily, this behavior can be overridden by setting the `skipModuleInsertion` option to `true` in your build configuration.
312
325
326
+
__How would I expose one or more modules as a global window property?__
327
+
328
+
- You can use the `globalModules` option to list all of the modules that you would like to expose as a `window` property
329
+
330
+
__I am having a scope problem with all of the local module variables. What can I do?__
331
+
332
+
- You can use the `globalObject` option to store all of your modules in a global object that uses the top-most function scope.
0 commit comments