Skip to content
This repository has been archived by the owner on Jan 9, 2023. It is now read-only.

Consider using the non-minified version in bower-main #41

Closed
wgorder opened this issue Mar 7, 2015 · 1 comment
Closed

Consider using the non-minified version in bower-main #41

wgorder opened this issue Mar 7, 2015 · 1 comment
Assignees

Comments

@wgorder
Copy link
Contributor

wgorder commented Mar 7, 2015

The reason being many front end developers use gulp, grunt or a similar build tool which does this for you. If you are not using these build tools you are probably not using bower either, or you can include the minified version if you want. Having it already minified messes up these tools.

Also if your like me I like to serve the non-minified version during development. I only minify on production build. What gets served is what is defined in the main of the bower file.

Also that is the official recommendation, see here:

See bower/bower#393

Current spec description:

The primary acting files necessary to use your package. While Bower does not directly use these files, they are listed with the commands bower list map and bower list --sources, so they can be used by build tools. Do not include minified files. Files should not be versioned (Bad: package.1.1.0.js; Good: package.js).

@johannesjo
Copy link
Owner

Thanks for the suggestion. I wasn't aware that this is a bad practice to do so. I'll change that.

@johannesjo johannesjo self-assigned this Mar 8, 2015
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants