Trouble With Npm Install For Older Version of Sage

Hello everyone,

I am brand new to the sage theme, and the company I am currently interning with uses Sage 8. I am trying to set up Sage 8.5.3 on my local environment, however when I run npm install I run into the following issue:

> npm WARN deprecated [email protected]: Please use gulp-clean-css
> npm WARN deprecated [email protected]: gulp-util is deprecated - replace it, following the guidelines at https://medium.com/gulpjs/gulp-util-ca3b1f9f9ac5
> npm WARN deprecated [email protected]: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
> npm WARN deprecated [email protected]: please upgrade to graceful-fs 4 for compatibility with current and future versions of Node.js
> npm WARN deprecated [email protected]: Browserslist 2 could fail on reading Browserslist >3.0 config used in other tools.
> npm WARN deprecated [email protected]: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
> npm WARN deprecated [email protected]: please upgrade to graceful-fs 4 for compatibility with current and future versions of Node.js
> npm WARN deprecated [email protected]: This module relies on Node.js's internals and will break at some point. Do not use it, and update to [email protected].
> npm WARN deprecated [email protected]: This module moved to @hapi/hawk. Please make sure to switch over as this distribution is no longer supported and may contain bugs and critical security issues.
> npm WARN deprecated [email protected]: This module moved to @hapi/sntp. Please make sure to switch over as this distribution is no longer supported and may contain bugs and critical security issues.
> npm WARN deprecated [email protected]: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial).
> npm WARN deprecated [email protected]: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial).
> npm WARN deprecated [email protected]: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial).
> npm WARN deprecated [email protected]: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
> npm WARN deprecated [email protected]: please upgrade to graceful-fs 4 for compatibility with current and future versions of Node.js
> 
> > [email protected] install C:\Users\Kevin\desktop\wordpress dev\example\site\web\app\themes\example\node_modules\node-sass
> > node scripts/install.js
> 
> Downloading binary from https://github.com/sass/node-sass/releases/download/v3.13.1/win32-x64-64_binding.node
> Cannot download "https://github.com/sass/node-sass/releases/download/v3.13.1/win32-x64-64_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\Kevin\desktop\wordpress dev\example\site\web\app\themes\example\node_modules\node-sass
> > node scripts/build.js
> 
> Building: C:\Program Files\nodejs\node.exe C:\Users\Kevin\desktop\wordpress dev\example\site\web\app\themes\example\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 [ 'C:\\Program Files\\nodejs\\node.exe',
> gyp verb cli   'C:\\Users\\Kevin\\desktop\\wordpress dev\\example\\site\\web\\app\\themes\\example\\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:\Users\Kevin\desktop\wordpress dev\example\site\web\app\themes\example\node_modules\which\which.js:13:12)
> gyp verb `which` failed     at F (C:\Users\Kevin\desktop\wordpress dev\example\site\web\app\themes\example\node_modules\which\which.js:68:19)
> gyp verb `which` failed     at E (C:\Users\Kevin\desktop\wordpress dev\example\site\web\app\themes\example\node_modules\which\which.js:80:29)
> gyp verb `which` failed     at C:\Users\Kevin\desktop\wordpress dev\example\site\web\app\themes\example\node_modules\which\which.js:89:16
> gyp verb `which` failed     at C:\Users\Kevin\desktop\wordpress dev\example\site\web\app\themes\example\node_modules\isexe\index.js:42:5
> gyp verb `which` failed     at C:\Users\Kevin\desktop\wordpress dev\example\site\web\app\themes\example\node_modules\isexe\windows.js:36:5
> gyp verb `which` failed     at FSReqWrap.oncomplete (fs.js:153:21)
> gyp verb `which` failed  python2 { Error: not found: python2
> gyp verb `which` failed     at getNotFoundError (C:\Users\Kevin\desktop\wordpress dev\example\site\web\app\themes\example\node_modules\which\which.js:13:12)
> gyp verb `which` failed     at F (C:\Users\Kevin\desktop\wordpress dev\example\site\web\app\themes\example\node_modules\which\which.js:68:19)
> gyp verb `which` failed     at E (C:\Users\Kevin\desktop\wordpress dev\example\site\web\app\themes\example\node_modules\which\which.js:80:29)
> gyp verb `which` failed     at C:\Users\Kevin\desktop\wordpress dev\example\site\web\app\themes\example\node_modules\which\which.js:89:16
> gyp verb `which` failed     at C:\Users\Kevin\desktop\wordpress dev\example\site\web\app\themes\example\node_modules\isexe\index.js:42:5
> gyp verb `which` failed     at C:\Users\Kevin\desktop\wordpress dev\example\site\web\app\themes\example\node_modules\isexe\windows.js:36:5
> gyp verb `which` failed     at FSReqWrap.oncomplete (fs.js:153:21)
> gyp verb `which` failed   stack:
> gyp verb `which` failed    'Error: not found: python2\n    at getNotFoundError (C:\\Users\\Kevin\\desktop\\wordpress dev\\example\\site\\web\\app\\themes\\example\\node_modules\\which\\which.js:13:12)\n    at F (C:\\Users\\Kevin\\desktop\\wordpress dev\\example\\site\\web\\app\\themes\\example\\node_modules\\which\\which.js:68:19)\n    at E (C:\\Users\\Kevin\\desktop\\wordpress dev\\example\\site\\web\\app\\themes\\example\\node_modules\\which\\which.js:80:29)\n    at C:\\Users\\Kevin\\desktop\\wordpress dev\\example\\site\\web\\app\\themes\\example\\node_modules\\which\\which.js:89:16\n    at C:\\Users\\Kevin\\desktop\\wordpress dev\\example\\site\\web\\app\\themes\\example\\node_modules\\isexe\\index.js:42:5\n    at C:\\Users\\Kevin\\desktop\\wordpress dev\\example\\site\\web\\app\\themes\\example\\node_modules\\isexe\\windows.js:36:5\n    at FSReqWrap.oncomplete (fs.js:153:21)',
> gyp verb `which` failed   code: 'ENOENT' }
> gyp verb check python checking for Python executable "python" in the PATH
> gyp verb `which` succeeded python C:\Users\Kevin\AppData\Local\Programs\Python\Python37\python.EXE
> gyp ERR! configure error
> gyp ERR! stack Error: Command failed: C:\Users\Kevin\AppData\Local\Programs\Python\Python37\python.EXE -c import sys; print "%s.%s.%s" % sys.version_info[:3];
> gyp ERR! stack   File "<string>", line 1
> gyp ERR! stack     import sys; print "%s.%s.%s" % sys.version_info[:3];
> gyp ERR! stack                                ^
> gyp ERR! stack SyntaxError: invalid syntax
> gyp ERR! stack
> gyp ERR! stack     at ChildProcess.exithandler (child_process.js:294:12)
> gyp ERR! stack     at ChildProcess.emit (events.js:189:13)
> gyp ERR! stack     at maybeClose (internal/child_process.js:970:16)
> gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:259:5)
> gyp ERR! System Windows_NT 10.0.17134
> gyp ERR! command "C:\\Program Files\\nodejs\\node.exe" "C:\\Users\\Kevin\\desktop\\wordpress dev\\example\\site\\web\\app\\themes\\example\\node_modules\\node-gyp\\bin\\node-gyp.js" "rebuild" "--verbose" "--libsass_ext=" "--libsass_cflags=" "--libsass_ldflags=" "--libsass_library="
> gyp ERR! cwd C:\Users\Kevin\desktop\wordpress dev\example\site\web\app\themes\example\node_modules\node-sass
> gyp ERR! node -v v10.15.3
> 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":"win32","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!     C:\Users\Kevin\AppData\Roaming\npm-cache\_logs\2019-05-21T02_49_56_444Z-debug.log

I’m not sure how to approach this, so any direction on how to tackle this would be really appreciated.

Hey @kevintran4u - usually the first thing I’d check in a case like this is making sure I’m using a version of Node compatible with the project. Are you using v4.5 or so of Node?

PS - if they don’t want you to use Sage 9, they may at least be okay with 8.6.0, which uses newer versions of Node, Gulp, etc.

1 Like

Ah that worked out perfectly. I thought the latest version of node would suffice, but it turned out that was the issue. I took your advice and ran Sage 8.6 with npm 6.9 and it works like a charm. thank you!

1 Like

This topic was automatically closed after 42 days. New replies are no longer allowed.