Javascript Require.js+;TypeError:优化后主干未定义
主干应用程序运行良好,经过预优化。在使用r.js(与almond一起使用)之后,我成功地生成了一个输出文件,该文件似乎总是在紧跟主干之后的模块中抛出“TypeError:Backbone is undefined”错误 例如,当r.js的输出如下所示:Javascript Require.js+;TypeError:优化后主干未定义,javascript,scala,backbone.js,playframework,requirejs,Javascript,Scala,Backbone.js,Playframework,Requirejs,主干应用程序运行良好,经过预优化。在使用r.js(与almond一起使用)之后,我成功地生成了一个输出文件,该文件似乎总是在紧跟主干之后的模块中抛出“TypeError:Backbone is undefined”错误 例如,当r.js的输出如下所示: /consumer/public/javascripts/vendor/almond.js /consumer/public/javascripts/vendor/jquery-1.7.2.js /consumer/public/javascri
/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
({
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"
}
})`
在浏览器中加载优化后的文件时,在引用主干时,上面的错误将被抛出到“propm.js”模块中。使用要求2.0.5、主干0.9.2和杏仁0.1.4。提前感谢您的帮助
PS:build.js如下所示:
/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
({
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"
}
})`
您可以尝试使用
inlineText:true
来确保主干位于编译的.js
文件中
此外,为了避免必须关注存储路径的两个对象,我建议使用类似于maincigfile的东西:“main.js”
-效果很好;)
编辑:为什么要设置
maincigfile
选项和路径?FWIW:如果有人遇到这个问题……使用amd版本的主干和下划线似乎可以解决问题。也就是说,amd版本的工作和垫片没有
当我忘记包含我的
垫片时,我遇到了这个问题。我通过在构建配置中将maincigfile
设置为我的main.js
文件解决了这个问题,例如如下所示:谢谢,尝试添加inlineText:true但没有成功…我在build.js中设置了mainConfig和path,因为我使用的是Scala Play框架,它将编译好的coffeescript放入baseUrl之外的“托管资源”目录中。因此,我使用mainConfig文件仅在一个位置设置供应商路径(和垫片),但使用build.js中的路径覆盖并设置播放编译的咖啡脚本的实际物理位置(在托管资源中)。但这可能是错误的方法?…sry,我不熟悉coffeescript:/但可能您正在加载主干,但忘记将其作为参数传递(至少错误似乎是由类似的原因引起的)