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.

Sign up for GitHub

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

Jump to bottom

Should bower install default to caret? #2144

Closed
robdodson opened this issue Jan 11, 2016 · 0 comments · Fixed by #2145
Closed

Should bower install default to caret? #2144

robdodson opened this issue Jan 11, 2016 · 0 comments · Fixed by #2145

Comments

@robdodson
Copy link

npm defaults to the caret when installing a package with the --save flag.

By not defaulting to a caret it means users who install foo#~1.2.3 will not get minor version updates.

If a user would like to force the system to install with a caret from the command line then they'll encounter weird quirks if they're on windows. #2121 (comment)

It seems like it may be advantageous to just make the caret the default behavior for installs done with --save.
@robdodson robdodson mentioned this issue Jan 11, 2016
Merged
samccone added a commit that referenced this issue Jan 11, 2016
@samccone
Default to ^ operator on --save
58d761d 
This fix brings us inline with how npm installs work and also brings us
more inline with how semver is supposed to be used.

Fixes #2144
@samccone samccone mentioned this issue Jan 11, 2016
Merged
samccone added a commit that referenced this issue Jan 11, 2016
@samccone
Default to ^ operator on --save
d06af7a 
This fix brings us inline with how npm installs work and also brings us
more inline with how semver is supposed to be used.

Fixes #2144
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Use caret on install save bower/bower
1 participant
@robdodson