-2

I am pretty much noob at programming and specially terminal/command prompt stuff. So whenever I try to install something with npm this error occurs.

samiu@Seeam_Laptop MINGW64 ~
$ npm install
npm WARN deprecated source-map-url@0.4.1: See https://github.com/lydell/source-map-url#deprecated
npm WARN deprecated har-validator@5.1.5: this library is no longer supported
npm WARN deprecated urix@0.1.0: Please see https://github.com/lydell/urix#deprecated
npm WARN deprecated resolve-url@0.2.1: https://github.com/lydell/resolve-url#deprecated
npm WARN deprecated source-map-resolve@0.5.3: See https://github.com/lydell/source-map-resolve#deprecated
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.2: request has been deprecated, see https://github.com/request/request/issues/3142
npm WARN deprecated stable@0.1.8: Modern JS already guarantees Array#sort() is a stable sort, so this library is deprecated. See the compatibility table on MDN: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Array/sort#browser_compatibility
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 mkdirp@0.5.4: 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 debug@3.2.6: Debug versions >=3.2.0 <3.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 svgo@1.3.2: This SVGO version is no longer supported. Upgrade to v2.x.x.
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 popper.js@1.16.1: You can find the new Popper v2 at @popperjs/core, this package is dedicated to the legacy v1
npm ERR! code 1
npm ERR! path C:\Users\samiu\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\samiu\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\\samiu\\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@18.17.1 | 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\samiu\node_modules\which\which.js:13:12)
npm ERR! gyp verb `which` failed     at F (C:\Users\samiu\node_modules\which\which.js:68:19)
npm ERR! gyp verb `which` failed     at E (C:\Users\samiu\node_modules\which\which.js:80:29)
npm ERR! gyp verb `which` failed     at C:\Users\samiu\node_modules\which\which.js:89:16
npm ERR! gyp verb `which` failed     at C:\Users\samiu\node_modules\isexe\index.js:42:5
npm ERR! gyp verb `which` failed     at C:\Users\samiu\node_modules\isexe\windows.js:36:5
npm ERR! gyp verb `which` failed     at FSReqCallback.oncomplete (node:fs:210:21)
npm ERR! gyp verb `which` failed  python2 Error: not found: python2
npm ERR! gyp verb `which` failed     at getNotFoundError (C:\Users\samiu\node_modules\which\which.js:13:12)
npm ERR! gyp verb `which` failed     at F (C:\Users\samiu\node_modules\which\which.js:68:19)
npm ERR! gyp verb `which` failed     at E (C:\Users\samiu\node_modules\which\which.js:80:29)
npm ERR! gyp verb `which` failed     at C:\Users\samiu\node_modules\which\which.js:89:16
npm ERR! gyp verb `which` failed     at C:\Users\samiu\node_modules\isexe\index.js:42:5
npm ERR! gyp verb `which` failed     at C:\Users\samiu\node_modules\isexe\windows.js:36:5
npm ERR! gyp verb `which` failed     at FSReqCallback.oncomplete (node:fs:210: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` failed Error: not found: python
npm ERR! gyp verb `which` failed     at getNotFoundError (C:\Users\samiu\node_modules\which\which.js:13:12)
npm ERR! gyp verb `which` failed     at F (C:\Users\samiu\node_modules\which\which.js:68:19)
npm ERR! gyp verb `which` failed     at E (C:\Users\samiu\node_modules\which\which.js:80:29)
npm ERR! gyp verb `which` failed     at C:\Users\samiu\node_modules\which\which.js:89:16
npm ERR! gyp verb `which` failed     at C:\Users\samiu\node_modules\isexe\index.js:42:5
npm ERR! gyp verb `which` failed     at C:\Users\samiu\node_modules\isexe\windows.js:36:5
npm ERR! gyp verb `which` failed     at FSReqCallback.oncomplete (node:fs:210:21)
npm ERR! gyp verb `which` failed  python Error: not found: python
npm ERR! gyp verb `which` failed     at getNotFoundError (C:\Users\samiu\node_modules\which\which.js:13:12)
npm ERR! gyp verb `which` failed     at F (C:\Users\samiu\node_modules\which\which.js:68:19)
npm ERR! gyp verb `which` failed     at E (C:\Users\samiu\node_modules\which\which.js:80:29)
npm ERR! gyp verb `which` failed     at C:\Users\samiu\node_modules\which\which.js:89:16
npm ERR! gyp verb `which` failed     at C:\Users\samiu\node_modules\isexe\index.js:42:5
npm ERR! gyp verb `which` failed     at C:\Users\samiu\node_modules\isexe\windows.js:36:5
npm ERR! gyp verb `which` failed     at FSReqCallback.oncomplete (node:fs:210:21) {
npm ERR! gyp verb `which` failed   code: 'ENOENT'
npm ERR! gyp verb `which` failed }
npm ERR! gyp verb could not find "python". checking python launcher
npm ERR! gyp verb could not find "python". guessing location 
npm ERR! gyp verb ensuring that file exists: C:\Python27\python.exe
npm ERR! gyp ERR! configure error
npm ERR! gyp ERR! stack Error: Can't find Python executable "python", you can set the PYTHON env variable.
npm ERR! gyp ERR! stack     at PythonFinder.failNoPython (C:\Users\samiu\node_modules\node-gyp\lib\configure.js:484:19)
npm ERR! gyp ERR! stack     at PythonFinder.<anonymous> (C:\Users\samiu\node_modules\node-gyp\lib\configure.js:509:16)
npm ERR! gyp ERR! stack     at callback (C:\Users\samiu\node_modules\graceful-fs\polyfills.js:306:20)
npm ERR! gyp ERR! stack     at FSReqCallback.oncomplete (node:fs:210:21)
npm ERR! gyp ERR! System Windows_NT 10.0.22621
npm ERR! gyp ERR! command "C:\\Program Files\\nodejs\\node.exe" "C:\\Users\\samiu\\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\samiu\node_modules\node-sass
npm ERR! gyp ERR! node -v v18.17.1
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: C:\Users\samiu\AppData\Local\npm-cache\_logs\2023-08-25T14_52_58_855Z-debug-0.log

this is a case when i tried using npm install. but this occurs on anything i want to install with npm.

I've mainly tried deleting npm-modules folder, npm cache clear and changing node version after reading other stackoverflow posts but doing so nothing changed. All other suggestions/solutions end up with similar error code. chatGPT told me to install python and I did but that didn't fix it either.

Merwin
  • 9
  • 3
  • Well your error is quite obvious: "Can't find Python executable "python"". – 0stone0 Aug 25 '23 at 15:15
  • @0stone0 I installed python but its not working. can you tell me how to make python work with this – Merwin Aug 25 '23 at 15:38
  • Does this answer your question? [npm - "Can't find Python executable "python", you can set the PYTHON env variable."](https://stackoverflow.com/questions/34372618/npm-cant-find-python-executable-python-you-can-set-the-python-env-variabl) – 0stone0 Aug 25 '23 at 15:42

0 Answers0