我的 dojo 应用程序在构建后、加载应用程序期间中断，抛出“multipleDefine”并给出此错误：
错误{src：“dojoLoader”，信息：对象}
消息：multipleDefine
info: 对象 {pid: "dojo", mid: "dojo/nls/dojo_en-us", pack: 对象, url: "dojo/nls/dojo_en-us.js", 执行: 5…}
这是我的个人资料：
var profile = {
// `basePath` is relative to the directory containing this profile file; in this case, it is being set to the
// src/ directory, which is the same place as the `baseUrl` directory in the loader configuration. (If you change
// this, you will also need to update run.js.)
basePath: '../src/',
// This is the directory within the release directory where built packages will be placed. The release directory
// itself is defined by `build.sh`. You should probably not use this; it is a legacy option dating back to Dojo
// 0.4.
// If you do use this, you will need to update build.sh, too.
// releaseName: '',
// Builds a new release.
action: 'release',
// Strips all comments and whitespace from CSS files and inlines @imports where possible.
//cssOptimize: 'comments',
// Excludes tests, demos, and original template files from being included in the built version.
mini: true,
// Uses Closure Compiler as the JavaScript minifier. This can also be set to "shrinksafe" to use ShrinkSafe,
// though ShrinkSafe is deprecated and not recommended.
// This option defaults to "" (no compression) if not provided.
optimize: '',
// We're building layers, so we need to set the minifier to use for those, too.
// This defaults to "shrinksafe" if not provided.
//layerOptimize: 'closure',
layerOptimize: '',
// Strips all calls to console functions within the code. You can also set this to "warn" to strip everything
// but console.error, and any other truthy value to strip everything but console.warn and console.error.
// This defaults to "normal" (strip all but warn and error) if not provided.
stripConsole: 'all',
// The default selector engine is not included by default in a dojo.js build in order to make mobile builds
// smaller. We add it back here to avoid that extra HTTP request. There is also a "lite" selector available; if
// you use that, you will need to set the `selectorEngine` property in `app/run.js`, too. (The "lite" engine is
// only suitable if you are not supporting IE7 and earlier.)
selectorEngine: 'acme',
//localeList:"en-gb,en-us,de-de,es-es,fr-fr,it-it,pt-br,ko-kr,zh-tw,zh-cn,ja-jp",
// Builds can be split into multiple different JavaScript files called "layers". This allows applications to
// defer loading large sections of code until they are actually required while still allowing multiple modules to
// be compiled into a single file.
layers: {
// This is the main loader module. It is a little special because it is treated like an AMD module even though
// it is actually just plain JavaScript. There is some extra magic in the build system specifically for this
// module ID.
'dojo/dojo': {
// In addition to the loader `dojo/dojo` and the loader configuration file `app/run`, we are also including
// the main application `app/main` and the `dojo/i18n` and `dojo/domReady` modules because, while they are
// all conditional dependencies in `app/main`, we do not want to have to make extra HTTP requests for such
// tiny files.
include: [ 'dojo/i18n', 'dojo/domReady', 'app/main', 'app/run' ],
// By default, the build system will try to include `dojo/main` in the built `dojo/dojo` layer, which adds
// a bunch of stuff we do not want or need. We want the initial script load to be as small and quick to
// load as possible, so we configure it as a custom, bootable base.
boot: true,
customBase: true
},
},
// Providing hints to the build system allows code to be conditionally removed on a more granular level than
// simple module dependencies can allow. This is especially useful for creating tiny mobile builds.
// Keep in mind that dead code removal only happens in minifiers that support it! Currently, only Closure Compiler
// to the Dojo build system with dead code removal.
// A documented list of has-flags in use within the toolkit can be found at
// <http://dojotoolkit.org/reference-guide/dojo/has.html>.
staticHasFeatures: {
// The trace & log APIs are used for debugging the loader, so we do not need them in the build.
'dojo-trace-api': 0,
'dojo-log-api': 0,
// This causes normally private loader data to be exposed for debugging. In a release build, we do not need
// that either.
'dojo-publish-privates': 0,
// This application is pure AMD, so get rid of the legacy loader.
'dojo-sync-loader': 0,
// `dojo-xhr-factory` relies on `dojo-sync-loader`, which we have removed.
'dojo-xhr-factory': 0,
// We are not loading tests in production, so we can get rid of some test sniffing code.
'dojo-test-sniff': 0
}
}
这是 src/ 中的index.html
注意：
负责在以下情况下删除“isDebug”标志： 部署到生产中。如果你修改这个标志，你会 打破构建！build.sh
<script data-dojo-config="async: 1, tlmSiblingOfDojo: 0, locale:'en_US', isDebug: 1" src="dojo/dojo.js"></script>
<!-- Load the loader configuration script. Note that this module ID is hard-coded in build.sh in order to provide
an optimised build that loads as few as one script for the entire application. If you change the name or
location of this module, you will need to update build.sh too. -->
<script src="app/run.js"></script>
这是在dist/中生成的index.html
<!DOCTYPE html>
<html>
<head>
<meta charset="utf-8">
<link rel="stylesheet" href="app/resources/app.css">
</head>
<body class="claro">
<script data-dojo-config=
"async: 1, tlmSiblingOfDojo: 0, locale:'en_US', deps:['app/run']"
src="dojo/dojo.js"></script>
</body>
</html>
我检查以确保 dojo/nls/dojo_en-us.js 存在并且没有问题。我被困在这一点上，没有任何线索！
感谢任何解决此问题的帮助。
您可以在 run.js 中发布您的需求吗？ 您在那里需要“dojo/_base/config”吗？
[刚刚注意到同样的错误，因为我忘记了;)]
来自文档：
需要注意 dojoConfig 和 dojo/_base/config 之间的区别。 dojoConfig 纯粹用于输入目的——这就是我们将配置参数传递给加载器和模块的方式。在引导过程中，dojo/_base/config 将从这些参数中填充，以便稍后通过模块代码查找。
我也遇到了类似的错误问题
多重定义
当尝试将 greensock 库包含到我的 dojo 项目中时。
当 dojo 之外的另一个库声明自己的
define解决方案是确保在加载使用
define所以 dojo 应该是您的脚本中最新加载到 html 中的
head<head>
<script src="yourLibrary.js"></script>
<script src="dojo/dojo.js"></script>
</head>
使用 jQuery UI 和其他库也可以看到这个问题。
加载器文档中对此有一个注释（无论如何，在做出此响应时）。
多重定义
AMD 定义被称为引用一个模块，该模块具有 已经被定义了。此问题最常见的原因是加载 通过 HTML 文档中的元素来实现模块。使用装载机； 不要使用元素。第二个最常见的原因是通过 要定义的显式模块标识符；也不要这样做。
https://dojotoolkit.org/reference-guide/1.10/loader/amd.html
许多库现在都实现了 UMD，它基本上会尝试自动检测 AMD 加载程序的存在。例如，Bootstrap——流行的前端框架——实现了 UMD。
因此以下示例将起作用（请注意，引导程序将全局加载）：
<script src="path/to/bootstrap.js"></script><!--UMD packaged library-->
<script src="path/to/dojo/dojo.js"></script><!--then dojo loader-->
但是下面的第二个示例将不起作用，因为 UMD 代码将检测 AMD 加载程序并使用它来注册自身。根据文档，这将触发 multipleDefine 错误。
<script src="path/to/dojo/dojo.js"></script><!--dojo loader first-->
<script src="path/to/bootstrap.js"></script><!--then UMD library-->
如果您想全局加载库，请使用上面的第一个示例并在 dojo 加载器之前加载它。如果您想将库作为 AMD 模块加载，请使用加载器。