All geek questions in one place

Require.js + TypeError: Backbone - undefined after optimization

Backbone application works fine, pre-optimized. After using r.js (with almonds), I successfully generated a single output file, which always seems to throw a "TypeError: Backbone is undefined" error into the module immediately after the baseline.

For example, when the output from r.js looks like this:

/consumer/public/javascripts/vendor/almond.js /consumer/public/javascripts/vendor/jquery-1.7.2.js /consumer/public/javascripts/vendor/underscore.js /consumer/public/javascripts/vendor/bootstrap.js /consumer/public/javascripts/vendor/backbone.js /consumer/public/javascripts/rjs/src/mnp/prop_m.js /consumer/public/javascripts/rjs/src/mnp/prop_c.js /consumer/public/javascripts/vendor/play-mustache.js ... /consumer/public/javascripts/main.js

When loading an optimized file in a browser, the error above will be indicated in the 'prop_m.js' module when linking to Backbone. Use requires 2.0.5, Backbone 0.9.2 and Almond 0.1.4. Thank you in advance for any help.

PS: build.js looks like this:

  ({ baseUrl: "./", mainConfigFile: "main.js", paths: { 'almond': 'vendor/almond', // need a path to the cs-compiled .js file 'app' : '../../target/scala-2.9.1/resource_managed/main/public/javascripts/rjs/src/app', 'mnp/router' : '../../target/scala-2.9.1/resource_managed/main/public/javascripts/rjs/src/mnp/router', 'mnp/search_form_v' : '../../target/scala-2.9.1/resource_managed/main/public/javascripts/rjs/src/mnp/search_form_v', 'mnp/prop_c' : '../../target/scala-2.9.1/resource_managed/main/public/javascripts/rjs/src/mnp/prop_c', 'mnp/prop_m' : '../../target/scala-2.9.1/resource_managed/main/public/javascripts/rjs/src/mnp/prop_m', 'mnp/prop_list_v' : '../../target/scala-2.9.1/resource_managed/main/public/javascripts/rjs/src/mnp/prop_list_v', 'mnp/prop_item_v' : '../../target/scala-2.9.1/resource_managed/main/public/javascripts/rjs/src/mnp/prop_item_v' }, /*not compatible with modules*/ name: 'vendor/almond', include: ["main"], out: "dist/app.js", /*not compatible with modules*/ keepBuildDir: false, preserveLicenseComments: false, optimize: "none", wrap: { start: "(function(global, define) {\n"+ // check for amd loader on global namespace " var globalDefine = global.define;\n", end: " var library = require('main');\n"+ " if(typeof module !== 'undefined' && module.exports) {\n"+ // export library for node " module.exports = library;\n"+ " } else if(globalDefine) {\n"+ // define library for global amd loader that is already present " (function (define) {\n"+ " define(function () { return library; });\n"+ " }(globalDefine));\n"+ " } else {\n"+ // define library on global namespace for inline script loading " global['main'] = library;\n"+ " }\n"+ "}(this));\n" } })`
+4
source share
3 answers

FWIW: If someone is facing this problem ... using amd versions and trunk seems to solve everything. i.e. amd versions worked, but the gasket wasn’t

Loading base and dressing rooms using RequireJS

+2
source

I had this problem when I forgot to include my shim s. I solved this by setting mainConfigFile in my main.js file in the build configuration, for example. as shown here: https://github.com/jrburke/r.js/blob/master/build/example.build.js

+1
source

you can try using inlineText: true to make sure the base unit is in the .js file compiled

Also, to avoid having to keep track of two path-saving objects, I would recommend something like mainConfigFile: "main.js" - works like a charm;) EDIT: why do you set the mainConfigFile option and paths?

0
source

Source: https://habr.com/ru/post/1435725/

More articles:


All Articles