-
Notifications
You must be signed in to change notification settings - Fork 73
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"Module ID almond has a source path that is the same as the output path" #87
Comments
Looks like this commit on r.js broke it: 014dd9da
|
Thanks for heads up. |
Just setting the version of r.js to a couple versions back fixed it. Works in the short term for me. |
I've got the same issue and things worked out when I changed the modules names to the alias given on the path config, rather than the module path, for example:
... instead of:
The downside is that everything must have an alias to actually work. |
This still seems to be an issue on |
We explicitely want that, since we always build to a new fresh folder, hence the first step is to copy the source code in there, and then explicitly want it to be overwritten! |
Error: Error: Module ID 'almond' has a source path that is same as output path: /Users/aelaguiz/workspace/cratejoy/node_modules/grunt-requirejs/node_modules/almond/almond.j
The text was updated successfully, but these errors were encountered: