You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm trying to use use the Bower package for an Ember project (building with Broccoli). Since the src folder is ignored by bower problems occure when building as there is a refernce in the *.js.map files to the src-folder.
The only way I can build successfully is to dissable sourcemaps, which makes me sad.
The same kind issue has been raised in the showdownjs/showdown project: showdownjs/showdown#200
Thoughts?
Best regards,
Samuel
The text was updated successfully, but these errors were encountered:
I'm not sure what we can do about this, we were forced to remove the src directory from bower to avoid issues with other build systems packing all the files.
@dstockwell Can you provide non-minified version in bower distribution? That way we don't have to refer to source map. Otherwise we can't use this amazing library in ember project at all...
Actually, we don't need sourceMap for non-development usage. May I ask why we need source map here? I don't see any famous JS project (jQuery, moment.js ...) released source map in product.
For anyone else in the Ember community who's coming to this issue, I created an addon that does some manual heavy-lifting to get around this -- that is, it copies the contents of src to the web-animations-js directory within a consuming app's Bower directory (after bower installing web-animations-js itself into the consuming application).
Of course, I'd be very interested in any updates here that would render this unnecessary, but it's getting the job done at the moment.
Hi,
I'm trying to use use the Bower package for an Ember project (building with Broccoli). Since the src folder is ignored by bower problems occure when building as there is a refernce in the *.js.map files to the src-folder.
The only way I can build successfully is to dissable sourcemaps, which makes me sad.
The same kind issue has been raised in the showdownjs/showdown project: showdownjs/showdown#200
Thoughts?
Best regards,
Samuel
The text was updated successfully, but these errors were encountered: