-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Should sourceMappingURL comments be included in bower distributions? #200
Comments
Hey @nikz. Thank you for your kind words. It seems the best way is not to include a src map for the concatenated files in the bower package (it does not make much sense since it points to non existent files). The regular package would keep them. |
@tivie: OK, great - would you like me to make the grunt modifications to exclude the map files? I can potentially handle that. :) |
@nikz No grunt modifications needed. The only thing needed is to make bower ignore map files. Although I'm kind of conflicted about it since map files are extremely useful for debugging. |
@tivie definitely agree, but without the files in |
@nikz If we remove the map files from bower but keep the sourcemap comments, would it fix the problem? |
@tivie I'm not 100% sure - I've just been removing the comments :) Let me give that a go today and get back to you? |
@tivie I just end up getting a message like the following:
But everything works! 👍 |
OK, so after some thought I think it might be better to include the src files in bower distributions. It increases download size a bit but, apart from that, I don't see any inconveniente. @nikz What do you think?! |
@tivie I think that would be fine, so long as they aren't getting built for distribution or anything like that. Means that the source map URLs have something to point to! |
Should be fixed now. |
Hi Team!
First off, thanks for Showdown - it's a really useful package. 👍
I'm having a bit of trouble when integrating the bower package into my workflow though, specifically with the
sourceMappingURL
comments (see my comment on the ember-cli-uglify package for more detail).In short, the bower package doesn't include any of the
src/
files, but the files indist/
have generated source maps that point to those files (and the comments that in turn point to those map files).Would you folks be open to a change to the gruntfile in order to not generate source maps when building a package for distribution? Or would you prefer an alternate solution?
Thanks!
Nik
The text was updated successfully, but these errors were encountered: