Node-sass: Cannot install node-sass 4.8.3

[harukaeru]

Overview

I could install node-sass correctly until yesterday.
The package.json I have was written like the following.

  "devDependencies": {
    ...
    "node-sass": "^4.5.0",
    ...
  }
}

However, from today it doesn't work well and cannot install that, either.

It seems https://github.com/sass/node-sass/releases/download/v4.8.3/linux-x64-47_binding.node is not found, so I downgraded the version to [email protected].
[email protected] can be installed properly.

Question

All I wanted to know why there is no linux-x64-47_binding.node on the new version's.
In addition, I'd like to know why I could install yesterday. Was there this file yesterday?

Environment

• NPM version (npm -v):
  3.6.0
• Node version (node -v):
  5.6.0
• Node Process (node -p process.versions):

{ http_parser: '2.6.1',
  node: '5.6.0',
  v8: '4.6.85.31',
  uv: '1.8.0',
  zlib: '1.2.8',
  ares: '1.10.1-DEV',
  icu: '56.1',
  modules: '47',
  openssl: '1.0.2f' }

• Node Platform (node -p process.platform):
  linux

• Node architecture (node -p process.arch):
  x64

• Others:
  It can be reproduced on Oracle Wercker

Error Messages

> [email protected] install /pipeline/source/node_modules/node-sass
> node scripts/install.js

Downloading binary from https://github.com/sass/node-sass/releases/download/v4.8.3/linux-x64-47_binding.node
Cannot download "https://github.com/sass/node-sass/releases/download/v4.8.3/linux-x64-47_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 /pipeline/source/node_modules/node-sass
> node scripts/build.js

Building: /usr/local/bin/node /pipeline/source/node_modules/node-gyp/bin/node-gyp.js rebuild --verbose --libsass_ext= --libsass_cflags= --libsass_ldflags= --libsass_library=
gyp info it worked if it ends with ok
gyp verb cli [ '/usr/local/bin/node',
gyp verb cli   '/pipeline/source/node_modules/node-gyp/bin/node-gyp.js',
gyp verb cli   'rebuild',
gyp verb cli   '--verbose',
gyp verb cli   '--libsass_ext=',
gyp verb cli   '--libsass_cflags=',
gyp verb cli   '--libsass_ldflags=',
gyp verb cli   '--libsass_library=' ]
gyp info using [email protected]
gyp info using [email protected] | linux | x64
gyp verb command rebuild []
gyp verb command clean []
gyp verb clean removing "build" directory
gyp verb command configure []
gyp verb check python checking for Python executable "python2" in the PATH
gyp verb `which` succeeded python2 /root/.pyenv/shims/python2
gyp ERR! configure error 
gyp ERR! stack Error: Command failed: /root/.pyenv/shims/python2 -c import platform; print(platform.python_version());
gyp ERR! stack pyenv: python2: command not found
gyp ERR! stack 
gyp ERR! stack The `python2' command exists in these Python versions:
gyp ERR! stack   2.7.6
gyp ERR! stack 
gyp ERR! stack 
gyp ERR! stack     at ChildProcess.exithandler (child_process.js:213:12)
gyp ERR! stack     at emitTwo (events.js:100:13)
gyp ERR! stack     at ChildProcess.emit (events.js:185:7)
gyp ERR! stack     at maybeClose (internal/child_process.js:827:16)
gyp ERR! stack     at Socket.<anonymous> (internal/child_process.js:319:11)
gyp ERR! stack     at emitOne (events.js:90:13)
gyp ERR! stack     at Socket.emit (events.js:182:7)
gyp ERR! stack     at Pipe._onclose (net.js:471:12)
gyp ERR! System Linux 4.8.11-coreos-r2
gyp ERR! command "/usr/local/bin/node" "/pipeline/source/node_modules/node-gyp/bin/node-gyp.js" "rebuild" "--verbose" "--libsass_ext=" "--libsass_cflags=" "--libsass_ldflags=" "--libsass_library="
gyp ERR! cwd /pipeline/source/node_modules/node-sass
gyp ERR! node -v v5.6.0
gyp ERR! node-gyp -v v3.6.2
gyp ERR! not ok

[xzyfer]

Sorry I forgot the binaries for Node 5. This is fixed now.

[wigogeoffrey]

@xzyfer Hi, i have the same issue. What did you mean with "I forgot the binaries for Node 5" ?

[xzyfer]

This issue has been resolved. Update to the latest node-sass

npm install node-sass@latest

On Fri., 27 Apr. 2018, 1:57 am WigoMedia, [e-mail] wrote:

@xzyfer https://github.com/xzyfer Hi, i have the same issue. What did
you mean with "I forgot the binaries for Node 5" ?

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