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

Running npm outdated show latest 1.2.5 #180

Open
mcfarljw opened this issue Jul 14, 2017 · 7 comments

Comments

@mcfarljw
Copy link

@mcfarljw mcfarljw commented Jul 14, 2017

When I run the npm outdated it shows current/wanted as 1.2.6 but lists 1.2.5 as the latest.

screen shot 2017-07-14 at 6 25 59 pm

"devDependencies": {
  "purify-css": "1.2.x"
}
@NightkingCH

This comment has been minimized.

Copy link

@NightkingCH NightkingCH commented Aug 30, 2017

The package is also duplicated on npm:

https://www.npmjs.com/package/purify-css => 1.2.5
https://www.npmjs.com/package/purifycss => 1.2.6

Would be great if this could be fixed in the same iteration. Was a bit confused about that.

@feross

This comment has been minimized.

Copy link

@feross feross commented Nov 18, 2017

Maintainers: if you want to fix this issue, here's a handy one-liner you can run:

npm dist-tag add purify-css@1.2.6 latest

Cheers 😛

@beeplin

This comment has been minimized.

Copy link

@beeplin beeplin commented Jan 7, 2018

+1. The wrong version is annoying.

@DanielRuf

This comment has been minimized.

Copy link
Contributor

@DanielRuf DanielRuf commented Feb 6, 2018

Not sure bug it seems 1.2.5 is not released and the latest version should be already the latest release. d8a29b4

@FranckFreiburger

This comment has been minimized.

Copy link

@FranckFreiburger FranckFreiburger commented Sep 12, 2018

https://www.npmjs.com/package/purify-css?activeTab=versions

Current Tags
1.2.5
latest
1.1.7
beta
Version History
1.2.5
a year ago
1.2.6
a year ago
1.2.3
a year ago
...
@DanielRuf

This comment has been minimized.

Copy link
Contributor

@DanielRuf DanielRuf commented Sep 12, 2018

Sorry, meant 1.2.6.
The isuue is that 1.2.5 was tagged / pushed after 1.2.6. npm adds the latest to the last published / tagged version.

@DanielRuf

This comment has been minimized.

Copy link
Contributor

@DanielRuf DanielRuf commented Sep 12, 2018

I guess it as pushed as latest to the wrong repository or something else.
At least 7 months later something is different now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
6 participants
You can’t perform that action at this time.