Open aelaguiz opened 10 years ago
Looks like this commit on r.js broke it:
014dd9da
25827
25828 //If buildPath and sourcePath are the same, throw since this
25829 //would result in modifying source. This condition can happen
25830 //with some more tricky paths: config and appDir/baseUrl
25831 //setting, which is a sign of incorrect config.
25832 if (module._buildPath === module._sourcePath) {
25833 throw new Error('Module ID \'' + module.name +
25834 '\' has a source path that is same as output path: ' +
25835 module._sourcePath +
25836 '. Stopping, config is malformed.');
25837 }
25838
Thanks for heads up. I do have a lot on my schedule atm., I will try to analyse the issue soon; but it might take some time until a fix could be ready. I´ll notice you when I found something.
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:
modules: [
{name: "app"}
]
... instead of:
modules: [
{name: "scripts/app.js"}
]
The downside is that everything must have an alias to actually work.
This still seems to be an issue on 2.1.16
Bummer!
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