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.

Version 1.9.1 not available on npm anymore?

See original GitHub issue

Our travis builds started failing because npm cannot install gulp-sourcemaps@1.9.1 anymore since a couple of hours ago.

Since 1.9.1 was published more than 24 hours ago, unpublishing it from npm would have required an action taken by npm. I’m not sure 1.9.1 was really unpublished but it’s impossible for me or for travis to install it:

$ npm show gulp-sourcemaps versions | grep 1.9
  '1.9.0',
  '1.9.2',

Do you happen to know why this happened?

Issue Analytics

State:
Created 7 years ago
Comments:9

Top GitHub Comments

1reaction

seldocommented, Jan 9, 2017

We are looking into how this was possible. We have a support ticket from @nmccready and will reply there.

0reactions

nmccreadycommented, Jan 10, 2017

Npm put it back

Top Results From Across the Web

Doesn't install NPM · Issue #766 · coreybutler/nvm-windows

I use nvm to install node on windows as recommanded by microsoft. ... Println("Node.js v" + v + " " + a +...

Package is not publishing to npm (not in the npm registry)

Try npm login . In case of npm publish , sometimes misleading message is shown.

Common errors | npm Docs

Broken npm installation; Random errors; No compatible version found; Permissions errors ... npm not running the latest version on a Windows machine ...

Migration | Yarn - Package Manager

A step-by-step and in-depth migration guide from Yarn 1 (Classic) to Yarn 2 (Berry).

LTS Changelog - Jenkins

Explain that some plugin updates can be unavailable even on the latest version of a given release line (i.e. LTS). (pull 5462); Update...