The GULP assembly does not start, it gives errors when npm i in window 10, while everything works in the linux subsystem. How to fix the problem?

Question

Node.js

The GULP assembly does not start in windows 10, it gives errors when npm i, while everything works fine in the linux subsystem.
Please tell me how to solve this problem. Below is the error log and package.json file

npm ERR! code 1
npm ERR! path D:\WorkSpace\___template-windows\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 D:\WorkSpace\___template-windows\node_modules\node-gyp\bin\node-gyp.js rebuild --verbose --libsass_ext= --libsass_cflags= --libsass_ldflags = --libsass_lib
rary=
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 'D:\\WorkSpace\\___template-windows\\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 [email protected]
npm ERR! gypinfo using [email protected] | win32 | x64
npm ERR! gyp verb command rebuild []
npm ERR! gyp verb command clean []
npm ERR!
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 (D:\WorkSpace\___template-windows\node_modules\which\which.js:13:12)
npm ERR! gyp verb `which` failed at F (D:\WorkSpace\___template-windows\node_modules\which\which.js:68:19)
npm ERR! gyp verb `which` failed at E (D:\WorkSpace\___template-windows\node_modules\which\which.js:80:29)
npm ERR! gyp verb `which` failed at D:\WorkSpace\___template-windows\node_modules\which\which.js:89:16
npm ERR! gyp verb `which` failed at D:\WorkSpace\___template-windows\node_modules\isexe\index.js:42:5
npm ERR! gyp verb `which` failed at D:\WorkSpace\___template-windows\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 (D:\WorkSpace\___template-windows\node_modules\which\which.js:13:12)
npm ERR! gyp verb `which` failed at F (D:\WorkSpace\___template-windows\node_modules\which\which.js:68:19)
npm ERR! gyp verb `which` failed at E (D:\WorkSpace\___template-windows\node_modules\which\which.js:80:29)
npm ERR! gyp verb `which` failed at D:\WorkSpace\___template-windows\node_modules\which\which.js:89:16
npm ERR! gyp verb `which` failed at D:\WorkSpace\___template-windows\node_modules\isexe\index.js:42:5
npm ERR! gyp verb `which` failed at D:\WorkSpace\___template-windows\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 "", line 1
npm ERR! gyp ERR! stack import sys; print "%s.%s.%s" % sys.version_info[:3];
npm ERR! gyp ERR! 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:397:12)
npm ERR! gyp ERR! stack at ChildProcess.emit (node:events:390:28)
npm ERR! gyp ERR! stack at maybeClose (node:internal/child_process:1064:16)
npm ERR! gyp ERR! stack at Process.ChildProcess._handle.onexit (node:internal/child_process:301:5)
npm ERR! gyp ERR! System Windows_NT 10.0.17763
npm ERR! gyp ERR! command "C:\\Program Files\\nodejs\\node.exe" "D:\\WorkSpace\\___template-windows\\node_modules\\node-gyp\\bin\\node-gyp.js" "rebuild" "--verbose" "--libsass_ext=" "--libsass_cflags=" "--l
ibsass_ldflags=" "--libsass_library="
npm ERR! gyp ERR! cwd D:\WorkSpace\___template-windows\node_modules\node-sass
npm ERR! gyp ERR! node -v v16.13.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:
npm ERR! C:\Users\rg\AppData\Local\npm-cache\_logs\2022-02-17T09_49_46_616Z-debug-0.log

Here is the package.json
{
"name":
"description": "Start HTML Template",
"main": "index.js",
"scripts": {
"test": "echo \"Error: no test specified\" && exit 1"
},
"author": "Admin",
"license": "ISC",
"devDependencies": {
"@babel/core": "^7.12.3",
"@babel/preset-env": "^7.12.1",
"babel- plugin-module-resolver": "^4.0.0",
"bootstrap": "^4.5.3",
"browser-sync": "^2.26.13",
"del": "^6.0.0",
" gulp": "^4.0.2",
"gulp-autoprefixer": "^7.0.1",
"gulp-babel": "^8.0.0",
"gulp-clean-css": "^4.3.0",
"gulp-concat": "^2.6 .1",
"gulp-imagemin": "^7.1.0",
"gulp-less": "^4.0.1",
"gulp-newer": "^1.4.0",
"gulp-rsync": "0.0.9",
"gulp-sass": "^4.1.0",
"gulp-stylus": "^2.7.0" ,
"gulp-uglify": "^3.0.2"
}
}

Answer 1

The error is 100% related to the Sass handler.
In short, the problem is in node-sass npm and the current version of node.js that is installed in the environment. There was such a package - node-sass, lived and made good money, and then suddenly its support stopped and it switched to deprecated status. Now, instead of node-sass, all new projects use dart-sass (sass package in npm) when setting up. To fix the error, I advise you to update the dependencies and, if possible, move to sass (or you can try installing the dependencies through yarn - it may be fixed and you won’t need to change anything).
* Another option is to change the node version to 16.13.2 via nvm, since the latest version of node-sass seems to be able to work with it.