Node-sass: Can't install node-sass with NPM 5.0.0

[hheexx]

> [email protected] install C:\Users\hexbo\Documents\cx_public\node_modules\node-sass
> node scripts/install.js

Downloading binary from https://github.com/sass/node-sass/releases/download/vhttps://registry.npmjs.org/node-sass/-/node-sass-4.5.3.tgz/win32-x64-48_binding.node
Cannot download "https://github.com/sass/node-sass/releases/download/vhttps://registry.npmjs.org/node-sass/-/node-sass-4.5.3.tgz/win32-x64-48_binding.node":

HTTP error 404 Not Found

Hint: If github.com is not accessible in your location
      try setting a proxy via HTTP_PROXY, e.g.

      export HTTP_PROXY=http://example.com:1234

or configure npm proxy via

      npm config set proxy http://example.com:8080

> [email protected] postinstall C:\Users\hexbo\Documents\cx_public\node_modules\node-sass
> node scripts/build.js

Can't install with NPM 5.0.0
It works with NPM 4.6.1

Node v6.9.2
Windows 10

[nschonni]

Actually the line would be https://github.com/sass/node-sass/blob/master/lib/extensions.js#L240 where is is somehow resolving pkg.version with https://registry.npmjs.org/node-sass/-/node-sass-4.5.3.tgz

[xzyfer]

This is likely due to changes to shrinkwrap in npm@5. Please try npm@latest. If the problem persist please comment on npm/npm#15050 or open an issue with npm and ping me in it.

[xzyfer]

Please don't comments on this issue. This is out of our hands for now. Downgrade to npm@4 in the mean time.

Leaving this issue open incase someone comes up with a work around. Unhelpful "me too" comments will be removed.

[oceanapplications]

I experienced this problem by running npm install with an older version of npm, updating npm and running install again.

My solution was to delete package-lock.json and run npm install while on the latest version of npm.

[marc1n]

As a workaround, manually change entry in package-lock.json or npm-shrinkwrap.json

from:

    "node-sass": {
      "version": "https://registry.npmjs.org/node-sass/-/node-sass-4.5.3.tgz/win32-x64-48_binding.node",
      "integrity": "..."
    },

to:

    "node-sass": {
      "version": "4.5.3",
      "resolved": "https://registry.npmjs.org/node-sass/-/node-sass-4.5.3.tgz/win32-x64-48_binding.node",
      "integrity": "..."
    },

[xzyfer]

rm -rf node_modules
rm package-lock.json
npm install

On 3 Jun. 2017 2:20 am, "Marcin Raczyński" [e-mail] wrote:

As a workaround, manually change entry in package-lock.json or
npm-shrinkwrap.json

from:

"node-sass": {
  "version": "http://npmcache.softax.local/node-sass/-/node-sass-4.5.3.tgz",
  "integrity": "sha1-0JydEXlkEjnRuX/8YjH9zsU+FWg="
},

to:

"node-sass": {
  "version": "4.5.3",
  "resolved": "http://npmcache.softax.local/node-sass/-/node-sass-4.5.3.tgz",
  "integrity": "sha1-0JydEXlkEjnRuX/8YjH9zsU+FWg="
},

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/sass/node-sass/issues/1991#issuecomment-305836893,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAjZWLx6XsXpoHHDC3CoKW_mYCsBRcDGks5sADZjgaJpZM4Nr4dQ
.

[seneyr]

Echoing what @xzyfer recommends...

Deleting the local npm cache and the node_modules directory and then rebuilding the shrinkwrap file is ultimately what worked for my team's project.

Depending on your preferences for installing newer dependencies you might also want to downgrade dependencies back to their previous versions using npm install @version in case they are upgraded during the npm install command.

[ruchern-chong]

I would like to report back/update that this issues seemed to be resolved with npm 5.0.2 @xzyfer

[xzyfer]

My understanding is that is due to files left over by previous npm versions.

rm -rf node_modules
rm package-lock.json
npm cache clean
npm install