Closed ne0guille closed 8 years ago
Are you running traceur instead of babel? Looks like you are doing on-the-fly tranpilation?
We are running babel and get this exact same issue pointing to traceur regardless
we are using babel, idk why its getting this traceur message. here is the config
System.config({ defaultJSExtensions: true, transpiler: "babel", babelOptions: { "modules": "system", "moduleIds": false, "comments": false, "compact": false, "stage": 2, "optional": [ "es7.decorators", "es7.classProperties", "runtime" ] }
I can confirm the same issue occurs here with loader-default beta-1.1.2
.
Error log from gulp bundle
(xxx inserted by me to mask local paths):
Error on instantiate for npm:aurelia-loader-default@1.0.0-beta.1.1.2/aurelia-loader-default.js at xxx/jspm_packages/npm/aurelia-loader-default@1.0.0-beta.1.1.2/aurelia-loader-default.js
Loading npm:aurelia-loader-default@1.0.0-beta.1.1.2.js
Error: Multiple anonymous defines.
at ParseTreeTransformer.AMDDependenciesTransformer.transformCallExpression (xxx/node_modules/systemjs-builder/compilers/amd.js:98:13)
at CallExpression.$__super.transform (xxx/node_modules/traceur/bin/traceur.js:6649:28)
at ParseTreeTransformer.transformAny (xxx/node_modules/traceur/bin/traceur.js:9193:44)
.. a lot more lines like above ..
@AlexanderDzhoganov @ne0guille I started getting the same error on my build server today too. It built fine last night at 3am EST and failed today at 1pm EST. Looking at systemjs-builder on github a new release (0.15.10) was released 5 hours ago and I think that release is what is causing the issues. The aurelia-bundler uses systemjs-builder as a dependency.
this might be useful to known
Thanks to @donald-slagle and @ne0guille 's information I have narrowed down the issue to this commit in systemjs/builder
which adds this check in compilers/amd.js which gets triggered by the define()
in addPlugin
in aurelia/loader-default@index.js.
How are you getting it to download the latest systemjs builder? Trying to reproduce to find a fix.
@PWKad I deleted my node_modules
and did npm install
which installed the latest builder, as the others I first encountered the issue on our build servers which do a fresh npm install
on every build
As a workaround you can do
npm install && npm install systemjs-builder@0.15.9
which will roll back systemjs/builder to 0.15.9 which didn't have this issue. This will only work with npm 3+.
Thanks for helping to narrow this down everyone I've got a hotfix I'm about to push out to get around.
I'm having an issue on my build server when running the bundler, its working fine on my local enviroment but failing on the build server
Would love to here some suggestions of how can i fix this and why its happening.
Thanks!
here is the error log.