node-sass: Cannot download "https://github.com/sass/node-sass/releases/download/v4.13.0/win32-x64-79_binding.node"

I’m getting this same error in OS x after updating to Catalina…I will leave my solution:

npm uninstall node-sass npm install node-sass

After that everything is up again…

For anyone else struggling with this issue I received a similar error message when working on OSX after upgrading my version of npm. Try removing your project’s local package-lock file and rerun npm install to see if it resolves the error.

@FlyRocketDrones This is a problem with your network proxy not allowing connections to Github and Amazon S3. There is nothing we can do here, worst case you can download the file from https://github.com/sass/node-sass/releases/tag/v4.13.0 and set environment variable SASS_BINARY_PATH to the full path of thie binding (please note it will not be copied though!)

C:\Users\saper\Downloads>wget -q https://github.com/sass/node-sass/releases/download/v4.13.0/win32-x64-64_binding.node

C:\Users\saper\Downloads>copy win32-x64-64_binding.node ..\safe_node_module
        1 file(s) copied.

C:\Users\saper\Downloads>set SASS_BINARY_PATH=C:\Users\saper\safe_node_module\win32-x64-64_binding.node

C:\Users\saper\Downloads>cd ..\ns10

C:\Users\saper\ns10>npm install node-sass

> node-sass@4.13.0 install C:\Users\saper\ns10\node_modules\node-sass
> node scripts/install.js

node-sass build Binary found at C:\Users\saper\safe_node_module\win32-x64-64_binding.node

> node-sass@4.13.0 postinstall C:\Users\saper\ns10\node_modules\node-sass
> node scripts/build.js

Binary found at C:\Users\saper\safe_node_module\win32-x64-64_binding.node
Testing binary
Binary is fine
npm WARN saveError ENOENT: no such file or directory, open 'C:\Users\saper\ns10\package.json'
npm notice created a lockfile as package-lock.json. You should commit this file.
npm WARN enoent ENOENT: no such file or directory, open 'C:\Users\saper\ns10\package.json'
npm WARN ns10 No description
npm WARN ns10 No repository field.
npm WARN ns10 No README data
npm WARN ns10 No license field.

+ node-sass@4.13.0
added 174 packages from 138 contributors and audited 529 packages in 20.875s
found 0 vulnerabilities

This started to give an error when I upgraded to Catalina in MAC

I solved with: run node-sass uninstall and then sudo npm install --unsafe-perm -g node-sass

For those that are using Windows, first you have to install the last version of phyton and then the “Windows build tools” with the following command (on an an elevated PowerShell or CMD.exe (run as Administrator)

npm install --global --production windows-build-tools

Then run “npm i” or “npm install node-sass” on your project.

This worked for me.

@LucasOta thanks for this https://github.com/sass/node-sass/issues/2773#issuecomment-566644144, it did fix the issue I encountered.

Ionic@5.4.13 Used powershell as administrator.

> npm install --global --production windows-build-tools # long process around 3-5 mins
> npm install # there were couple of warnings but I just ignored them
> npm run ionic:serve # script from package.json "ionic:serve": "ionic-app-scripts serve"
> ionic-hello-world@ ionic:serve C:\Users\**\Sites\bitbucket\**-ionic-app
> ionic-app-scripts serve

[16:45:59]  ionic-app-scripts 2.0.2 
[16:45:59]  watch started ... 
[16:45:59]  build dev started ... 
[16:45:59]  clean started ... 
[16:45:59]  clean finished in 7 ms 
[16:45:59]  copy started ... 
[16:45:59]  transpile started ... 
[16:46:06]  transpile finished in 6.72 s 
[16:46:06]  preprocess started ... 
[16:46:06]  deeplinks started ... 
[16:46:06]  deeplinks finished in 291 ms 
[16:46:06]  preprocess finished in 292 ms 
[16:46:06]  webpack started ... 
[16:46:07]  copy finished in 7.38 s 
[16:46:14]  webpack finished in 7.65 s 
[16:46:14]  sass started ... 
[16:46:18]  sass finished in 3.64 s 
[16:46:18]  postprocess started ... 
[16:46:18]  postprocess finished in 8 ms 
[16:46:18]  lint started ... 
[16:46:18]  build dev finished in 18.72 s 
[16:46:18]  watch ready in 19.16 s 
[16:46:18]  dev server running: http://localhost:8100/ 

Personal Gist Reference

For those who is having this issue, I think this is a windows issue. I’ve been having trouble since middle of this year (around August or September 2019 I think) with HTTPS connections in the command line. This has affected NPM installs and other scripts that need to get or call HTTPS connections.

I think is actually a windows issue. This is one of reason I HATE using Windows as a development machine. https://answers.microsoft.com/en-us/windows/forum/all/help-getting-https-to-work-in-command-line-in/6d226e12-f76b-47f8-8dac-1060f3047a08

FYI: I don’t have a network proxy or any kind of proxy setup in my network or my computers.

@saper makes sense. So for anyone who’s having this issue, it is caused by v4.13 hosted at a location that doesn’t seem secure to our networks. So unless you find a way to get this version thru proxy, you’ll have to stay at v4.12.

node-sass@4.13.0 install D:\Practice\webpack\Colt-youtube\my\node_modules\node-sass node scripts/install.js

Downloading binary from https://github.com/sass/node-sass/releases/download/v4.13.0/win32-x64-79_binding.node Cannot download “https://github.com/sass/node-sass/releases/download/v4.13.0/win32-x64-79_binding.node”:

connect ECONNREFUSED 127.0.0.1:443

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

node-sass@4.13.0 postinstall D:\Practice\webpack\Colt-youtube\my\node_modules\node-sass node scripts/build.js

Building: C:\Program Files\nodejs\node.exe D:\Practice\webpack\Colt-youtube\my\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 [ gyp verb cli ‘C:\Program Files\nodejs\node.exe’, gyp verb cli ‘D:\Practice\webpack\Colt-youtube\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 verb cli ] gyp info using node-gyp@3.8.0 gyp info using node@13.0.1 | 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 “C:\Users\Mustafa.windows-build-tools\python27\python.exe” in the PATH gyp verb which failed Error: not found: C:\Users\Mustafa.windows-build-tools\python27\python.exe gyp verb which failed at getNotFoundError (D:\Practice\webpack\Colt-youtube\my\node_modules\which\which.js:13:12) gyp verb which failed at F (D:\Practice\webpack\Colt-youtube\my\node_modules\which\which.js:68:19) gyp verb which failed at E (D:\Practice\webpack\Colt-youtube\my\node_modules\which\which.js:80:29) gyp verb which failed at D:\Practice\webpack\Colt-youtube\my\node_modules\which\which.js:89:16 gyp verb which failed at D:\Practice\webpack\Colt-youtube\my\node_modules\isexe\index.js:42:5 gyp verb which failed at D:\Practice\webpack\Colt-youtube\my\node_modules\isexe\windows.js:36:5 gyp verb which failed at FSReqCallback.oncomplete (fs.js:158:21) gyp verb which failed C:\Users\Mustafa.windows-build-tools\python27\python.exe Error: not found: C:\Users\Mustafa.windows-build-tools\python27\python.exe gyp verb which failed at getNotFoundError (D:\Practice\webpack\Colt-youtube\my\node_modules\which\which.js:13:12) gyp verb which failed at F (D:\Practice\webpack\Colt-youtube\my\node_modules\which\which.js:68:19) gyp verb which failed at E (D:\Practice\webpack\Colt-youtube\my\node_modules\which\which.js:80:29) gyp verb which failed at D:\Practice\webpack\Colt-youtube\my\node_modules\which\which.js:89:16 gyp verb which failed at D:\Practice\webpack\Colt-youtube\my\node_modules\isexe\index.js:42:5 gyp verb which failed at D:\Practice\webpack\Colt-youtube\my\node_modules\isexe\windows.js:36:5 gyp verb which failed at FSReqCallback.oncomplete (fs.js:158:21) { gyp verb which failed stack: ‘Error: not found: C:\Users\Mustafa\.windows-build-tools\python27\python.exe\n’ + gyp verb which failed ’ at getNotFoundError (D:\Practice\webpack\Colt-youtube\my\node_modules\which\which.js:13:12)\n’ + gyp verb which failed ’ at F (D:\Practice\webpack\Colt-youtube\my\node_modules\which\which.js:68:19)\n’ + gyp verb which failed ’ at E (D:\Practice\webpack\Colt-youtube\my\node_modules\which\which.js:80:29)\n’ + gyp verb which failed ’ at D:\Practice\webpack\Colt-youtube\my\node_modules\which\which.js:89:16\n’ + gyp verb which failed ’ at D:\Practice\webpack\Colt-youtube\my\node_modules\isexe\index.js:42:5\n’ + gyp verb which failed ’ at D:\Practice\webpack\Colt-youtube\my\node_modules\isexe\windows.js:36:5\n’ + gyp verb which failed ’ at FSReqCallback.oncomplete (fs.js:158:21)', gyp verb which failed code: ‘ENOENT’ gyp verb which failed } gyp verb could not find “C:\Users\Mustafa.windows-build-tools\python27\python.exe”. checking python launcher gyp verb could not find “C:\Users\Mustafa.windows-build-tools\python27\python.exe”. 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 “C:\Users\Mustafa.windows-build-tools\python27\python.exe”, you can set the PYTHON env variable. gyp ERR! stack at PythonFinder.failNoPython (D:\Practice\webpack\Colt-youtube\my\node_modules\node-gyp\lib\configure.js:484:19) gyp ERR! stack at PythonFinder.<anonymous> (D:\Practice\webpack\Colt-youtube\my\node_modules\node-gyp\lib\configure.js:509:16) gyp ERR! stack at callback (D:\Practice\webpack\Colt-youtube\my\node_modules\graceful-fs\polyfills.js:295:20) gyp ERR! stack at FSReqCallback.oncomplete (fs.js:158:21) gyp ERR! System Windows_NT 6.1.7601 gyp ERR! command “C:\Program Files\nodejs\node.exe” “D:\Practice\webpack\Colt-youtube\my\node_modules\node-gyp\bin\node-gyp.js” “rebuild” “–verbose” “–libsass_ext=” “–libsass_cflags=” “–libsass_ldflags=” “–libsass_library=” gyp ERR! cwd D:\Practice\webpack\Colt-youtube\my\node_modules\node-sass gyp ERR! node -v v13.0.1 gyp ERR! node-gyp -v v3.8.0 gyp ERR! not ok Build failed with error code: 1 npm WARN bootstrap@4.3.1 requires a peer of jquery@1.9.1 - 3 but none is installed. You must install peer dependencies yourself. npm WARN bootstrap@4.3.1 requires a peer of popper.js@^1.14.7 but none is installed. You must install peer dependencies yourself. npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.9 (node_modules\fsevents): npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.9: wanted {“os”:“darwin”,“arch”:“any”} (current: {“os”:“win32”,“arch”:“x64”})

npm ERR! code ELIFECYCLE npm ERR! errno 1 npm ERR! node-sass@4.13.0 postinstall: node scripts/build.js npm ERR! Exit status 1 npm ERR! npm ERR! Failed at the node-sass@4.13.0 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!