question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

installation error

See original GitHub issue

PS C:\Users\xxx\source\Angular\ngx-admin> npm install npm WARN old lockfile npm WARN old lockfile The package-lock.json file was created with an old version of npm, npm WARN old lockfile so supplemental metadata must be fetched from the registry. npm WARN old lockfile npm WARN old lockfile This is a one-time fix-up, please be patient… npm WARN old lockfile npm WARN EBADENGINE Unsupported engine { npm WARN EBADENGINE package: ‘@angular-devkit/architect@0.1201.0’, npm WARN EBADENGINE required: { npm WARN EBADENGINE node: ‘^12.14.1 || >=14.0.0’, npm WARN EBADENGINE npm: ‘^6.11.0 || ^7.5.6’, npm WARN EBADENGINE yarn: ‘>= 1.13.0’ npm WARN EBADENGINE }, npm WARN EBADENGINE current: { node: ‘v16.15.0’, npm: ‘8.5.5’ } npm WARN EBADENGINE } npm WARN EBADENGINE Unsupported engine { npm WARN EBADENGINE package: ‘@angular-devkit/build-angular@12.1.0’, npm WARN EBADENGINE required: { npm WARN EBADENGINE node: ‘^12.14.1 || >=14.0.0’, npm WARN EBADENGINE npm: ‘^6.11.0 || ^7.5.6’, npm WARN EBADENGINE yarn: ‘>= 1.13.0’ npm WARN EBADENGINE }, npm WARN EBADENGINE current: { node: ‘v16.15.0’, npm: ‘8.5.5’ } npm WARN EBADENGINE } npm WARN EBADENGINE Unsupported engine { npm WARN EBADENGINE package: ‘@angular-devkit/build-optimizer@0.1201.0’, npm WARN EBADENGINE required: { npm WARN EBADENGINE node: ‘^12.14.1 || >=14.0.0’, npm WARN EBADENGINE npm: ‘^6.11.0 || ^7.5.6’, npm WARN EBADENGINE yarn: ‘>= 1.13.0’ npm WARN EBADENGINE }, npm WARN EBADENGINE current: { node: ‘v16.15.0’, npm: ‘8.5.5’ } npm WARN EBADENGINE } npm WARN EBADENGINE Unsupported engine { npm WARN EBADENGINE package: ‘@angular-devkit/build-webpack@0.1201.0’, npm WARN EBADENGINE required: { npm WARN EBADENGINE node: ‘^12.14.1 || >=14.0.0’, npm WARN EBADENGINE npm: ‘^6.11.0 || ^7.5.6’, npm WARN EBADENGINE yarn: ‘>= 1.13.0’ npm WARN EBADENGINE }, npm WARN EBADENGINE current: { node: ‘v16.15.0’, npm: ‘8.5.5’ } npm WARN EBADENGINE } npm WARN EBADENGINE Unsupported engine { npm WARN EBADENGINE package: ‘@angular-devkit/core@12.1.0’, npm WARN EBADENGINE required: { npm WARN EBADENGINE node: ‘^12.14.1 || >=14.0.0’, npm WARN EBADENGINE npm: ‘^6.11.0 || ^7.5.6’, npm WARN EBADENGINE yarn: ‘>= 1.13.0’ npm WARN EBADENGINE }, npm WARN EBADENGINE current: { node: ‘v16.15.0’, npm: ‘8.5.5’ } npm WARN EBADENGINE } npm WARN EBADENGINE Unsupported engine { npm WARN EBADENGINE package: ‘@angular-devkit/schematics@12.1.0’, npm WARN EBADENGINE required: { npm WARN EBADENGINE node: ‘^12.14.1 || >=14.0.0’, npm WARN EBADENGINE npm: ‘^6.11.0 || ^7.5.6’, npm WARN EBADENGINE yarn: ‘>= 1.13.0’ npm WARN EBADENGINE }, npm WARN EBADENGINE current: { node: ‘v16.15.0’, npm: ‘8.5.5’ } npm WARN EBADENGINE } npm WARN EBADENGINE Unsupported engine { npm WARN EBADENGINE package: ‘@angular/cli@12.1.0’, npm WARN EBADENGINE required: { npm WARN EBADENGINE node: ‘^12.14.1 || >=14.0.0’, npm WARN EBADENGINE npm: ‘^6.11.0 || ^7.5.6’, npm WARN EBADENGINE yarn: ‘>= 1.13.0’ npm WARN EBADENGINE }, npm WARN EBADENGINE current: { node: ‘v16.15.0’, npm: ‘8.5.5’ } npm WARN EBADENGINE } npm WARN EBADENGINE Unsupported engine { npm WARN EBADENGINE package: ‘@ngtools/webpack@12.1.0’, npm WARN EBADENGINE required: { npm WARN EBADENGINE node: ‘^12.14.1 || >=14.0.0’, npm WARN EBADENGINE npm: ‘^6.11.0 || ^7.5.6’, npm WARN EBADENGINE yarn: ‘>= 1.13.0’ npm WARN EBADENGINE }, npm WARN EBADENGINE current: { node: ‘v16.15.0’, npm: ‘8.5.5’ } npm WARN EBADENGINE } npm WARN EBADENGINE Unsupported engine { npm WARN EBADENGINE package: ‘@schematics/angular@12.1.0’, npm WARN EBADENGINE required: { npm WARN EBADENGINE node: ‘^12.14.1 || >=14.0.0’, npm WARN EBADENGINE npm: ‘^6.11.0 || ^7.5.6’, npm WARN EBADENGINE yarn: ‘>= 1.13.0’ npm WARN EBADENGINE }, npm WARN EBADENGINE current: { node: ‘v16.15.0’, npm: ‘8.5.5’ } npm WARN EBADENGINE } npm WARN EBADENGINE Unsupported engine { npm WARN EBADENGINE package: ‘karma-cli@1.0.1’, npm WARN EBADENGINE required: { node: ‘0.10 || 0.12 || 4 || 5 || 6’ }, npm WARN EBADENGINE current: { node: ‘v16.15.0’, npm: ‘8.5.5’ } npm WARN EBADENGINE } npm WARN deprecated ini@1.3.5: Please update to ini >=1.3.6 to avoid a prototype pollution issue npm WARN deprecated domelementtype@1.3.0: update to domelementtype@1.3.1 npm WARN deprecated source-map-url@0.4.1: See https://github.com/lydell/source-map-url#deprecated npm WARN deprecated flatten@1.0.2: flatten is deprecated in favor of utility frameworks such as lodash. npm WARN deprecated source-map-resolve@0.6.0: See https://github.com/lydell/source-map-resolve#deprecated npm WARN deprecated urix@0.1.0: Please see https://github.com/lydell/urix#deprecated npm WARN deprecated har-validator@5.1.5: this library is no longer supported npm WARN deprecated har-validator@5.1.3: this library is no longer supported npm WARN deprecated har-validator@5.1.3: this library is no longer supported npm WARN deprecated browserslist@1.7.7: Browserslist 2 could fail on reading Browserslist >3.0 config used in other tools. npm WARN deprecated browserslist@1.7.7: Browserslist 2 could fail on reading Browserslist >3.0 config used in other tools. npm WARN deprecated browserslist@1.7.7: Browserslist 2 could fail on reading Browserslist >3.0 config used in other tools. npm WARN deprecated chokidar@1.7.0: Chokidar 2 will break on node v14+. Upgrade to chokidar 3 with 15x less dependencies. npm WARN deprecated chokidar@2.1.8: Chokidar 2 does not receive security updates since 2019. Upgrade to chokidar 3 with 15x fewer dependencies npm WARN deprecated source-map-resolve@0.5.3: See https://github.com/lydell/source-map-resolve#deprecated npm WARN deprecated source-map-resolve@0.5.3: See https://github.com/lydell/source-map-resolve#deprecated npm WARN deprecated resolve-url@0.2.1: https://github.com/lydell/resolve-url#deprecated npm WARN deprecated circular-json@0.3.3: CircularJSON is in maintenance only, flatted is its successor. npm WARN deprecated debug@4.1.1: Debug versions >=3.2.0 ❤️.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797) npm WARN deprecated debug@3.2.6: Debug versions >=3.2.0 ❤️.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797) npm WARN deprecated gulp-util@3.0.8: gulp-util is deprecated - replace it, following the guidelines at https://medium.com/gulpjs/gulp-util-ca3b1f9f9ac5 npm WARN deprecated querystring@0.2.0: The querystring API is considered Legacy. new code should use the URLSearchParams API instead. npm WARN deprecated uuid@2.0.3: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details. npm WARN deprecated node-uuid@1.4.8: Use uuid module instead npm WARN deprecated uuid@3.4.0: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details. npm WARN deprecated uuid@3.4.0: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details. npm WARN deprecated request@2.88.0: request has been deprecated, see https://github.com/request/request/issues/3142 npm WARN deprecated request@2.88.0: request has been deprecated, see https://github.com/request/request/issues/3142 npm WARN deprecated request@2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142 npm WARN deprecated uuid@3.3.2: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details. npm WARN deprecated uuid@3.3.2: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details. npm WARN deprecated mkdirp@0.5.1: Legacy versions of mkdirp are no longer supported. Please update to mkdirp 1.x. (Note that the API surface has changed to use Promises in 1.x.) npm WARN deprecated coffee-script@1.12.7: CoffeeScript on NPM has moved to “coffeescript” (no hyphen) npm WARN deprecated viz.js@1.8.0: no longer supported npm WARN deprecated tar@2.2.2: This version of tar is no longer supported, and will not receive security updates. Please upgrade asap. npm WARN deprecated @types/googlemaps@3.43.3: Types for the Google Maps browser API have moved to @types/google.maps. Note: these types are not for the googlemaps npm package, which is a Node API. npm WARN deprecated tslint@6.1.3: TSLint has been deprecated in favor of ESLint. Please see https://github.com/palantir/tslint/issues/4534 for more information. npm WARN deprecated core-js@2.5.1: core-js@❤️.4 is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Please, upgrade your dependencies to the actual version of core-js. npm WARN deprecated ckeditor@4.7.3: We have renamed the @ckeditor package. New versions are available under the @ckeditor4 name. npm ERR! code 1 npm ERR! path C:\Users\xxx\source\Angular\ngx-admin\node_modules\node-sass npm ERR! command failed npm ERR! command C:\Windows\system32\cmd.exe /d /s /c node scripts/build.js npm ERR! Building: C:\Program Files\nodejs\node.exe C:\Users\xxx\source\Angular\ngx-admin\node_modules\node-gyp\bin\node-gyp.js rebuild --verbose --libsass_ext= --libsass_cflags= --libsass_ldflags= --libsass_library= npm ERR! gyp info it worked if it ends with ok npm ERR! gyp verb cli [ npm ERR! gyp verb cli ‘C:\Program Files\nodejs\node.exe’, npm ERR! gyp verb cli ‘C:\Users\xxx\source\Angular\ngx-admin\node_modules\node-gyp\bin\node-gyp.js’, npm ERR! gyp verb cli ‘rebuild’, npm ERR! gyp verb cli ‘–verbose’, npm ERR! gyp verb cli ‘–libsass_ext=’, npm ERR! gyp verb cli ‘–libsass_cflags=’, npm ERR! gyp verb cli ‘–libsass_ldflags=’, npm ERR! gyp verb cli ‘–libsass_library=’ npm ERR! gyp verb cli ] npm ERR! gyp info using node-gyp@3.8.0 npm ERR! gyp info using node@16.15.0 | win32 | x64 npm ERR! gyp verb command rebuild [] npm ERR! gyp verb command clean [] npm ERR! gyp verb clean removing “build” directory npm ERR! gyp verb command configure [] npm ERR! gyp verb check python checking for Python executable “python2” in the PATH npm ERR! gyp verb which failed Error: not found: python2 npm ERR! gyp verb which failed at getNotFoundError (C:\Users\xxx\source\Angular\ngx-admin\node_modules\which\which.js:13:12) npm ERR! gyp verb which failed at F (C:\Users\xxx\source\Angular\ngx-admin\node_modules\which\which.js:68:19) npm ERR! gyp verb which failed at E (C:\Users\xxx\source\Angular\ngx-admin\node_modules\which\which.js:80:29) npm ERR! gyp verb which failed at C:\Users\xxx\source\Angular\ngx-admin\node_modules\which\which.js:89:16 npm ERR! gyp verb which failed at C:\Users\xxx\source\Angular\ngx-admin\node_modules\isexe\index.js:42:5 npm ERR! gyp verb which failed at C:\Users\xxx\source\Angular\ngx-admin\node_modules\isexe\windows.js:36:5 npm ERR! gyp verb which failed at FSReqCallback.oncomplete (node:fs:198:21) npm ERR! gyp verb which failed python2 Error: not found: python2 npm ERR! gyp verb which failed at getNotFoundError (C:\Users\xxx\source\Angular\ngx-admin\node_modules\which\which.js:13:12) npm ERR! gyp verb which failed at F (C:\Users\xxx\source\Angular\ngx-admin\node_modules\which\which.js:68:19) npm ERR! gyp verb which failed at E (C:\Users\xxx\source\Angular\ngx-admin\node_modules\which\which.js:80:29) npm ERR! gyp verb which failed at C:\Users\xxx\source\Angular\ngx-admin\node_modules\which\which.js:89:16 npm ERR! gyp verb which failed at C:\Users\xxx\source\Angular\ngx-admin\node_modules\isexe\index.js:42:5 npm ERR! gyp verb which failed at C:\Users\xxx\source\Angular\ngx-admin\node_modules\isexe\windows.js:36:5 npm ERR! gyp verb which failed at FSReqCallback.oncomplete (node:fs:198:21) { npm ERR! gyp verb which failed code: ‘ENOENT’ npm ERR! gyp verb which failed } npm ERR! gyp verb check python checking for Python executable “python” in the PATH npm ERR! gyp verb which succeeded python C:\Python310\python.EXE npm ERR! gyp ERR! configure error npm ERR! gyp ERR! stack Error: Command failed: C:\Python310\python.EXE -c import sys; print “%s.%s.%s” % sys.version_info[:3]; npm ERR! gyp ERR! stack File “<string>”, line 1 npm ERR! gyp ERR! stack import sys; print “%s.%s.%s” % sys.version_info[:3]; npm ERR! gyp ERR! stack ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ npm ERR! gyp ERR! stack SyntaxError: Missing parentheses in call to ‘print’. Did you mean print(…)? npm ERR! gyp ERR! stack npm ERR! gyp ERR! stack at ChildProcess.exithandler (node:child_process:398:12) npm ERR! gyp ERR! stack at ChildProcess.emit (node:events:527:28) npm ERR! gyp ERR! stack at maybeClose (node:internal/child_process:1092:16) npm ERR! gyp ERR! stack at Socket.<anonymous> (node:internal/child_process:451:11) npm ERR! gyp ERR! stack at Socket.emit (node:events:527:28) npm ERR! gyp ERR! stack at Pipe.<anonymous> (node:net:709:12) npm ERR! gyp ERR! System Windows_NT 10.0.19044 npm ERR! gyp ERR! command “C:\Program Files\nodejs\node.exe” “C:\Users\xxx\source\Angular\ngx-admin\node_modules\node-gyp\bin\node-gyp.js” “rebuild” “–verbose” “–libsass_ext=” “–libsass_cflags=” “–libsass_ldflags=” “–libsass_library=” npm ERR! gyp ERR! cwd C:\Users\xxx\source\Angular\ngx-admin\node_modules\node-sass npm ERR! gyp ERR! node -v v16.15.0 npm ERR! gyp ERR! node-gyp -v v3.8.0 npm ERR! gyp ERR! not ok npm ERR! Build failed with error code: 1

npm ERR! A complete log of this run can be found in: npm ERR! C:\Users\xxx\AppData\Local\npm-cache_logs\2022-05-07T16_35_25_637Z-debug-0.log PS C:\Users\xxx\source\Angular\ngx-admin>

Issue Analytics

  • State:open
  • Created a year ago
  • Comments:14

github_iconTop GitHub Comments

2reactions
adampwrightcommented, May 8, 2022

Same problem

1reaction
Prefix1802commented, May 10, 2022

Hi,

Can you try this?

Download and install python 2.7 and then

npm config set python C:\Python27\python.exe

The problem is that node-sass needs python 2

“npm ERR! gyp verb which failed python2 Error: not found: python2”

Read more comments on GitHub >

github_iconTop Results From Across the Web

How to troubleshoot Windows Installer errors - Microsoft Support
Describes how to troubleshoot problems that occur when you install, uninstall, or upgrade a program on a Windows-based computer by using Windows Installer....
Read more >
How to Fix Microsoft Windows 10 Installation Error Codes
This document covers the list of Windows 10 installation error codes with its corresponding Cause and Resolution. Learn how to Fix!
Read more >
If an error occurred while updating or installing macOS
The message might say that an error occurred while downloading, preparing, or installing, or that the installer is damaged or could not be ......
Read more >
Fix problems installing Chrome - Google Chrome Help
If you get an error message when you try to download and install Google Chrome, try these fixes. Fix most installation errors Make...
Read more >
"Install failed - Error 1603. Fatal error during installation ...
The window "Install failed - Error 1603, fatal error during installation" pops up when installing Autodesk products 2020 or above versions.
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found