-
-
Notifications
You must be signed in to change notification settings - Fork 78.8k
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
"npm install bootstrap@latest" now installs v4 alpha instead of 3.3.6 #18520
Comments
Unable to reproduce.
|
I had the same problem (see #18539 )
That's how other NPM libs do it, e.g. jQuery:
|
See NPM documentation: https://docs.npmjs.com/cli/dist-tag |
Wow, the npm docs don't surface this too well. And googling for "npm prerelease" didn't seem to yield anything mentioning dist-tags either. |
@danielweck Still confused why you were getting v4 though. The webpages I had found regarding prereleases claim that |
The dist-tags should be sorted out now:
|
@cvrebert I am not sure about the original issue committer ( @arechsteiner ), but personally I was using |
@danielweck: I am using @cvrebert: This works now, and |
And I've just sent a PR to update our internal npm release instructions accordingly, so this should be fully resolved now. |
@cvrebert I really appreciate your documentation efforts for dist-tags. I did a full write-up on dist-tags recently: https://medium.com/greenkeeper-blog/one-simple-trick-for-javascript-package-maintainers-to-avoid-breaking-their-user-s-software-and-to-6edf06dc5617 |
With npm, using
npm install bootstrap --save
causes"bootstrap": "~4.0.0-alpha.2"
being installed and added as a dependency to package.json.In bower on the other hand,
bower install bootstrap --save
installs and saves the latest stable version (3.3.6), as expected.The text was updated successfully, but these errors were encountered: