question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

shelljs Breaks SemVer for Alpha and Pre-Release Versions

See original GitHub issue

npm published a change to their CDN configuration earlier today that exposed another issue with SemVer publishing via npm. As such, it would seem that shelljs is breaking some of the internet because of the alpha and pre-release versions that were published to NPM.

Would it be possible to get some of those versions unpublished and prevent future releases from breaking SemVer?

air:test_mar9 user$ nvm use 5.7.1
Now using node v5.7.1 (npm v3.6.0)
air:test_mar9 user$ npm install eslint
npm ERR! Darwin 15.3.0
npm ERR! argv "/Users/user/.nvm/versions/node/v5.7.1/bin/node" "/Users/user/.nvm/versions/node/v5.7.1/bin/npm" "install" "eslint"
npm ERR! node v5.7.1
npm ERR! npm  v3.6.0

npm ERR! Invalid Version: 0.0.6pre2
npm ERR!
npm ERR! If you need help, you may report this error at:
npm ERR!     <https://github.com/npm/npm/issues>

npm ERR! Please include the following file with any support request:
npm ERR!     /Users/user/test_mar9/npm-debug.log
air:test_mar9 user$ npm view shelljs versions

[ '0.0.1-alpha1',
  '0.0.1alpha1',
  '0.0.1',
  '0.0.2-pre1',
  '0.0.2pre1',
  '0.0.2',
  '0.0.3',
  '0.0.4pre1',
  '0.0.4-pre1',
  '0.0.4',
  '0.0.5pre1',
  '0.0.5-pre1',
  '0.0.5pre2',
  '0.0.5-pre2',
  '0.0.5-pre3',
  '0.0.5pre3',
  '0.0.5-pre4',
  '0.0.5pre4',
  '0.0.5',
  '0.0.6-pre1',
  '0.0.6pre1',
  '0.0.6-pre2',
  '0.0.6pre2',
  '0.0.6',
  '0.0.7',
  '0.0.8',
  '0.0.9',
  '0.1.0',
  '0.1.1',
  '0.1.2',
  '0.1.3',
  '0.1.4',
  '0.2.0',
  '0.2.1',
  '0.2.2',
  '0.2.3',
  '0.2.4',
  '0.2.5',
  '0.2.6',
  '0.3.0',
  '0.4.0',
  '0.5.0',
  '0.5.1',
  '0.5.2',
  '0.5.3',
  '0.6.0' ]

air:test_mar9 user$

Issue Analytics

  • State:closed
  • Created 8 years ago
  • Comments:18 (11 by maintainers)

github_iconTop GitHub Comments

2reactions
nfischercommented, Mar 18, 2016

If there’s a way you can change your registry, that should resolve the issue. npm config set registry https://registry.npmjs.org/.

I can reproduce this error when I use https://skimdb.npmjs.com/registry.

0reactions
JonDuffycommented, Mar 21, 2016

Fixed this by removing shelljs from the private npm repo, forcing a download which does not contain the invalid versions

Read more comments on GitHub >

github_iconTop Results From Across the Web

Guidance for versionning of pre · Issue #6 · semver ... - GitHub
As soon as a v1.0.0 exists, there can only be one major version increment indicating breaking changes between v1.0.0 and the next non-prerelease...
Read more >
Semantic Versioning 2.0.0 | Semantic Versioning
When major, minor, and patch are equal, a pre-release version has lower precedence than a normal version: Example: 1.0.0-alpha < 1.0.0. Precedence for...
Read more >
Semver: Is it acceptable for "latest pre-release" package to be ...
tag field, I am currently publishing distribution tags such that latest will be newer than alpha when we graduate our alpha packages. Eg....
Read more >
Versioning - android Git repositories
This page covers Jetpack's usage of Semantic Versioning and pre-release cycles, ... Alpha, beta, and release candidate releases are versioned sequentially ...
Read more >
semver - npm Docs
First, prerelease versions frequently are updated very quickly, and contain many breaking changes that are (by the author's design) not yet fit ...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found