my CI tried to install 4.11
node scripts/install.js
Downloading binary from https://github.com/sass/node-sass/releases/download/v4.11.0/linux_musl-x64-59_binding.node
Cannot download "https://github.com/sass/node-sass/releases/download/v4.11.0/linux_musl-x64-59_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
and got a error, that stated that a variant is missing
on windows & ubuntu dev. environment all is fine; but CI build crashes
Got support dropped? or something else?
for now i will force use 4.10, but would love to be on latest again
Node 9 has been end-of-lifed so we were going unable to build the Alpine
binaries as we usually do. Our installation metrics suggested very few use
Node 9 so we decided to continue with the bug fix release until we could
figure out how to build the binaries for EOL'd node versions.
Note we will be forced to drop support for these versions imminently. The
only solution will be to update to an LTS or current release - either
6,8,10, or 11 at the time of writing.
On Mon., 10 Dec. 2018, 3:27 am Tim <[email protected] wrote:
my CI tried to install 4.11
node scripts/install.js
Downloading binary from https://github.com/sass/node-sass/releases/download/v4.11.0/linux_musl-x64-59_binding.node
Cannot download "https://github.com/sass/node-sass/releases/download/v4.11.0/linux_musl-x64-59_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:1234or configure npm proxy via
npm config set proxy http://example.com:8080and got a error, that stated that a variant is missing
on windows & ubuntu dev. environment all is fine; but CI build crashesGot support dropped? or something else?
for now i will force use 4.10, but would love to be on latest again
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/sass/node-sass/issues/2564, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAjZWGVyStNKQkPbPKPU9GJMllS-ftdmks5u3TnbgaJpZM4ZKM5Q
.
I'm getting an error on Node 10:
Cannot download "https://github.com/sass/node-sass/releases/download/v4.11.0/linux_musl-x64-59_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 /srv/node_modules/node-sass
> node scripts/build.js
Building: /usr/local/bin/node /srv/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 '/srv/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` failed Error: not found: python2
gyp verb `which` failed at getNotFoundError (/srv/node_modules/which/which.js:13:12)
gyp verb `which` failed at F (/srv/node_modules/which/which.js:68:19)
gyp verb `which` failed at E (/srv/node_modules/which/which.js:80:29)
gyp verb `which` failed at /srv/node_modules/which/which.js:89:16
gyp verb `which` failed at /srv/node_modules/isexe/index.js:42:5
gyp verb `which` failed at /srv/node_modules/isexe/mode.js:8:5
gyp verb `which` failed at FSReqWrap.oncomplete (fs.js:170:21)
gyp verb `which` failed python2 { Error: not found: python2
gyp verb `which` failed at getNotFoundError (/srv/node_modules/which/which.js:13:12)
gyp verb `which` failed at F (/srv/node_modules/which/which.js:68:19)
gyp verb `which` failed at E (/srv/node_modules/which/which.js:80:29)
gyp verb `which` failed at /srv/node_modules/which/which.js:89:16
gyp verb `which` failed at /srv/node_modules/isexe/index.js:42:5
gyp verb `which` failed at /srv/node_modules/isexe/mode.js:8:5
gyp verb `which` failed at FSReqWrap.oncomplete (fs.js:170:21)
gyp verb `which` failed stack: 'Error: not found: python2\n at getNotFoundError (/srv/node_modules/which/which.js:13:12)\n at F (/srv/node_modules/which/which.js:68:19)\n at E (/srv/node_modules/which/which.js:80:29)\n at /srv/node_modules/which/which.js:89:16\n at /srv/node_modules/isexe/index.js:42:5\n at /srv/node_modules/isexe/mode.js:8:5\n at FSReqWrap.oncomplete (fs.js:170:21)',
gyp verb `which` failed code: 'ENOENT' }
gyp verb check python checking for Python executable "python" in the PATH
gyp verb `which` failed Error: not found: python
gyp verb `which` failed at getNotFoundError (/srv/node_modules/which/which.js:13:12)
gyp verb `which` failed at F (/srv/node_modules/which/which.js:68:19)
gyp verb `which` failed at E (/srv/node_modules/which/which.js:80:29)
gyp verb `which` failed at /srv/node_modules/which/which.js:89:16
gyp verb `which` failed at /srv/node_modules/isexe/index.js:42:5
gyp verb `which` failed at /srv/node_modules/isexe/mode.js:8:5
gyp verb `which` failed at FSReqWrap.oncomplete (fs.js:170:21)
gyp verb `which` failed python { Error: not found: python
gyp verb `which` failed at getNotFoundError (/srv/node_modules/which/which.js:13:12)
gyp verb `which` failed at F (/srv/node_modules/which/which.js:68:19)
gyp verb `which` failed at E (/srv/node_modules/which/which.js:80:29)
gyp verb `which` failed at /srv/node_modules/which/which.js:89:16
gyp verb `which` failed at /srv/node_modules/isexe/index.js:42:5
gyp verb `which` failed at /srv/node_modules/isexe/mode.js:8:5
gyp verb `which` failed at FSReqWrap.oncomplete (fs.js:170:21)
gyp verb `which` failed stack: 'Error: not found: python\n at getNotFoundError (/srv/node_modules/which/which.js:13:12)\n at F (/srv/node_modules/which/which.js:68:19)\n at E (/srv/node_modules/which/which.js:80:29)\n at /srv/node_modules/which/which.js:89:16\n at /srv/node_modules/isexe/index.js:42:5\n at /srv/node_modules/isexe/mode.js:8:5\n at FSReqWrap.oncomplete (fs.js:170:21)',
gyp verb `which` failed code: 'ENOENT' }
gyp ERR! configure error
gyp ERR! stack Error: Can't find Python executable "python", you can set the PYTHON env variable.
gyp ERR! stack at PythonFinder.failNoPython (/srv/node_modules/node-gyp/lib/configure.js:484:19)
gyp ERR! stack at PythonFinder.<anonymous> (/srv/node_modules/node-gyp/lib/configure.js:406:16)
gyp ERR! stack at F (/srv/node_modules/which/which.js:68:16)
gyp ERR! stack at E (/srv/node_modules/which/which.js:80:29)
gyp ERR! stack at /srv/node_modules/which/which.js:89:16
gyp ERR! stack at /srv/node_modules/isexe/index.js:42:5
gyp ERR! stack at /srv/node_modules/isexe/mode.js:8:5
gyp ERR! stack at FSReqWrap.oncomplete (fs.js:170:21)
gyp ERR! System Linux 4.9.0-8-amd64
gyp ERR! command "/usr/local/bin/node" "/srv/node_modules/node-gyp/bin/node-gyp.js" "rebuild" "--verbose" "--libsass_ext=" "--libsass_cflags=" "--libsass_ldflags=" "--libsass_library="
gyp ERR! cwd /srv/node_modules/node-sass
gyp ERR! node -v v9.11.2
gyp ERR! node-gyp -v v3.8.0
gyp ERR! not ok
Build failed with error code: 1
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: [email protected] (node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for [email protected]: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] postinstall: `node scripts/build.js`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] postinstall script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! /root/.npm/_logs/2018-12-16T12_51_12_351Z-debug.log
The command '/bin/sh -c npm install' returned a non-zero code: 1
That is node 9
@xzyfer
That is node 9
Damn, you're right, thanks!
Same issue
[email protected] install /home/nareshthakur/Documents/projects/chs-agent/node_modules/node-sass
node scripts/install.js
Downloading binary from https://github.com/sass/node-sass/releases/download/v4.11.0/linux-x64-64_binding.node
Cannot download "https://github.com/sass/node-sass/releases/download/v4.11.0/linux-x64-64_binding.node":
gyp info using [email protected]
gyp info using [email protected] | linux | x64
Not the same issue. That file is available. Click the link to see.
On Thu., 20 Dec. 2018, 6:29 pm Naresh Thakur <[email protected]
wrote:
Same issue
[email protected] install
/home/nareshthakur/Documents/projects/chs-agent/node_modules/node-sass
node scripts/install.js
Downloading binary from
https://github.com/sass/node-sass/releases/download/v4.11.0/linux-x64-64_binding.node
Cannot download "
https://github.com/sass/node-sass/releases/download/v4.11.0/linux-x64-64_binding.node
":gyp info using [email protected]
gyp info using [email protected] | linux | x64—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/sass/node-sass/issues/2564#issuecomment-448900729,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAjZWHUui5_UyaMJTbzoCz05SjlV-USuks5u6zxHgaJpZM4ZKM5Q
.
I'll try to get vuejs Readme for the dockerize app updated if node 10 works without an issue.
Nevertheless, 9.11.1 is referenced in the documentation page: https://github.com/vuejs/vuejs.org/blob/master/src/v2/cookbook/dockerize-vuejs-app.md
I'm getting this on Node 10. Our CI server has no access to github. We are getting this only when trying npm ci on Angular 7 project. When we execute npm install everything is ok. But we need to execute npm ci
```
[email protected] install C:\temp\test\mynode_modulesnode-sass
node scripts/install.js
Downloading binary from https://github.com/sass/node-sass/releases/download/v4.11.0/win32-x64-64_binding.node
Cannot download "https://github.com/sass/node-sass/releases/download/v4.11.0/win32-x64-64_binding.node":
connect ETIMEDOUT 192.30.253.113:443
Timed out whilst downloading the prebuilt binary
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:\temp\test\mynode_modulesnode-sass
node scripts/build.js
Building: C:\Program Filesnodejsnode.exe C:\temp\test\mynode_modulesnode-gyp\binnode-gyp.js rebuild --verbose --libsass_ext= --libsass_cflags= --libsass_ldflags= --libsass_library=
gyp info it worked if it ends with ok
gyp verb cli [ 'C:\Program Files\nodejs\node.exe',
gyp verb cli 'C:\temp\test\my\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] | win32 | 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 failed Error: not found: python2
gyp verb which failed at getNotFoundError (C:\temp\test\mynode_moduleswhichwhich.js:13:12)
gyp verb which failed at F (C:\temp\test\mynode_moduleswhichwhich.js:68:19)
gyp verb which failed at E (C:\temp\test\mynode_moduleswhichwhich.js:80:29)
gyp verb which failed at C:\temp\test\mynode_moduleswhichwhich.js:89:16
gyp verb which failed at C:\temp\test\mynode_modules\isexe\index.js:42:5
gyp verb which failed at C:\temp\test\mynode_modules\isexe\windows.js:36:5
gyp verb which failed at FSReqWrap.oncomplete (fs.js:154:21)
gyp verb which failed python2 { Error: not found: python2
gyp verb which failed at getNotFoundError (C:\temp\test\mynode_moduleswhichwhich.js:13:12)
gyp verb which failed at F (C:\temp\test\mynode_moduleswhichwhich.js:68:19)
gyp verb which failed at E (C:\temp\test\mynode_moduleswhichwhich.js:80:29)
gyp verb which failed at C:\temp\test\mynode_moduleswhichwhich.js:89:16
gyp verb which failed at C:\temp\test\mynode_modules\isexe\index.js:42:5
gyp verb which failed at C:\temp\test\mynode_modules\isexe\windows.js:36:5
gyp verb which failed at FSReqWrap.oncomplete (fs.js:154:21)
gyp verb which failed stack:
gyp verb which failed 'Error: not found: python2\n at getNotFoundError (C:\temp\test\my\node_modules\which\which.js:13:12)\n at F (C:\temp\test\my\node_modules\which\which.js:68:19)\n at E (C:\temp\test\my\node_modules\which\which.js:80:29)\n at C:\temp\test\my\node_modules\which\which.js:89:16\n at C:\temp\test\my\node_modules\isexe\index.js:42:5\n
at C:\temp\test\my\node_modules\isexe\windows.js:36:5\n at FSReqWrap.oncomplete (fs.js:154:21)',
gyp verb which failed code: 'ENOENT' }
gyp verb check python checking for Python executable "python" in the PATH
gyp verb which failed Error: not found: python
gyp verb which failed at getNotFoundError (C:\temp\test\mynode_moduleswhichwhich.js:13:12)
gyp verb which failed at F (C:\temp\test\mynode_moduleswhichwhich.js:68:19)
gyp verb which failed at E (C:\temp\test\mynode_moduleswhichwhich.js:80:29)
gyp verb which failed at C:\temp\test\mynode_moduleswhichwhich.js:89:16
gyp verb which failed at C:\temp\test\mynode_modules\isexe\index.js:42:5
gyp verb which failed at C:\temp\test\mynode_modules\isexe\windows.js:36:5
gyp verb which failed at FSReqWrap.oncomplete (fs.js:154:21)
gyp verb which failed python { Error: not found: python
gyp verb which failed at getNotFoundError (C:\temp\test\mynode_moduleswhichwhich.js:13:12)
gyp verb which failed at F (C:\temp\test\mynode_moduleswhichwhich.js:68:19)
gyp verb which failed at E (C:\temp\test\mynode_moduleswhichwhich.js:80:29)
gyp verb which failed at C:\temp\test\mynode_moduleswhichwhich.js:89:16
gyp verb which failed at C:\temp\test\mynode_modules\isexe\index.js:42:5
gyp verb which failed at C:\temp\test\mynode_modules\isexe\windows.js:36:5
gyp verb which failed at FSReqWrap.oncomplete (fs.js:154:21)
gyp verb which failed stack:
gyp verb which failed 'Error: not found: python\n at getNotFoundError (C:\temp\test\my\node_modules\which\which.js:13:12)\n at F (C:\temp\test\my\node_modules\which\which.js:68:19)\n at E (C:\temp\test\my\node_modules\which\which.js:80:29)\n at C:\temp\test\my\node_modules\which\which.js:89:16\n at C:\temp\test\my\node_modules\isexe\index.js:42:5\n at C:\temp\test\my\node_modules\isexe\windows.js:36:5\n at FSReqWrap.oncomplete (fs.js:154:21)',
gyp verb which failed code: 'ENOENT' }
gyp verb could not find "python". checking python launcher
gyp verb could not find "python". guessing location
gyp verb ensuring that file exists: C:\Python27\python.exe
gyp ERR! configure error
gyp ERR! stack Error: Can't find Python executable "python", you can set the PYTHON env variable.
gyp ERR! stack at PythonFinder.failNoPython (C:\temp\test\mynode_modulesnode-gyp\lib\configure.js:484:19)
gyp ERR! stack at PythonFinder.
gyp ERR! stack at C:\temp\test\mynode_modules\graceful-fs\polyfills.js:282:31
gyp ERR! stack at FSReqWrap.oncomplete (fs.js:154:21)
gyp ERR! System Windows_NT 6.3.9600
gyp ERR! command "C:\Program Files\nodejs\node.exe" "C:\temp\test\my\node_modules\node-gyp\bin\node-gyp.js" "rebuild" "--verbose" "--libsass_ext=" "--libsass_cflags=" "--libsass_ldflags=" "--libsass_library="
gyp ERR! cwd C:\temp\test\mynode_modulesnode-sass
gyp ERR! node -v v10.15.1
gyp ERR! node-gyp -v v3.8.0
gyp ERR! not ok
Build failed with error code: 1
added 1054 packages in 89.98s
I hit this on our CI as well (AWS CodeBuild).
The build script seems to want https://github.com/sass/node-sass/releases/download/v4.11.0/linux_musl-x64-59_binding.node
but this is not among the published release files https://github.com/sass/node-sass/releases/
(note 59 vs 57).
Moving to Node 10 (in an AWS CodeBuild container) had no effect on this issue.
I confirm that switching from FROM 9-alpine to FROM node:lts-alpine in my Dockerfile did the trick. Thanks.
Closing this, as we explicitly support less node versions with Alpine.
Most helpful comment
I confirm that switching from
FROM 9-alpinetoFROM node:lts-alpinein my Dockerfile did the trick. Thanks.