Does grunt-contrib-requirejs add semicolons to the end of sourcemaps references that do not have a newline?
tangst opened this issue · 0 comments
tangst commented
I was using grunt-contrib-requirejs and ran it with the uglify: none on RactiveJS 0.6.1, which has sourcemap comments like this
//# sourceMappingURL=ractive.js.map
In one case, the sourcemap does not break into a new line. After the task completes, there is a semicolon at the end.
//# sourceMappingURL=ractive.js.map;
This causes the browser to generate an error saying the sourcemap cannot be found.
I've already heard back from r.js (jburke), who stated that r.js doesn't cause this after running r.js on the command line via node. See requirejs/r.js#799
Is there something in this Grunt task that might be doing this?