Remove sourcemaps from distribution files.

What kind of issue is this? (put ‘x’ between the square brackets)

• Question. This issue tracker is not the place for questions. If you want to ask how to do something, or to understand why something isn’t working the way you expect it to, use http://stackoverflow.com/questions/ask . Provide working code, starting from http://codepen.io/marcandre/pen/jqbzyN?editors=101. We monitor the tag parsley.js.
• Bug report. If you’ve found a bug, you must provide a minimal example in a CodePen, starting from http://codepen.io/marcandre/pen/jqbzyN?editors=101 .
• Feature Request. Make sure there’s no good way to do what you want first; consider asking on http://stackoverflow.com/questions/ask first.

Hi, so I use bower, and bower installer to install dependencies, when requesting distribution files I don’t require the sourcemap, however because the sourcemap is not included in the bower file as a main file it doesn’t get installed by bower installer causing my grunt tasks to fail due to the missing sourcemap.

Can you either exclude sourcemaps from distribution files, or include the sourcemap in bower.json as a main file? Preferably the former as I have no requirement for source maps in production code.

Thanks! 😃

[dahliacreative]

It saddens me that many developers feel the same way you do. I wish more users felt that they could be part of a project, that they could contribute to it, and that as users, they were part of the project.

@marcandre This isn’t really about being part of the project, the is purely from the point of view of using the plugin in my projects. When I use it in my projects I don’t need the source map.

If I found a bug when using the plugin then I would debug it and open up an issue or if I had time a PR.

This is purely about the fact that I use parsley on pretty much every project and when I put my project live I don’t need sourcemaps!

[marcandre]

Cool, glad to hear this. So should we close this?