Skip to content
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

Use current version instead of "latest" in generated bower.json? #189

Open
tsujigiri opened this issue Mar 11, 2016 · 1 comment
Open

Use current version instead of "latest" in generated bower.json? #189

tsujigiri opened this issue Mar 11, 2016 · 1 comment

Comments

@tsujigiri
Copy link

When having a Bowerfile, I was wondering if it would be better to generate the bower.json with each package's current version instead of "latest". This would be closer to what bundler does and prevent surprises when a package gets updated. Currently, the options to work around this, are checking-in the whole bower_components directory into git, or manually keeping track of each package's version in the Bowerfile itself, which is both suboptimal.

@jeffblake
Copy link

Agreed - this would be a great addition. Similar to Gemfile.lock

I like to see which packages were updated so I know what to look out for

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants