Instalacja projektu w JS

Question

Witam!

chciałbym poprosić o pomoc/wskazówki aby odpalić stary projekt napisany JS-iku na Windows10. (Nie jestem pewny, ale to może być AngularJS).

Katalog projektu wygląda w ten sposób:

W readme.md mam:

Jak próbuję zainstalować zależności ">npm install" to dostaję taki błąd:

npm ERR! Windows_NT 10.0.19045
npm ERR! argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "install"
npm ERR! node v6.9.4
npm ERR! npm  v3.10.10
npm ERR! code EPROTO
npm ERR! errno EPROTO
npm ERR! syscall write

npm ERR! write EPROTO 101057795:error:1408D07B:SSL routines:ssl3_get_key_exchange:bad signature:openssl\ssl\s3_clnt.c:2010:
npm ERR!
npm ERR!
npm ERR! If you need help, you may report this error at:
npm ERR!     <https://github.com/npm/npm/issues>

npm ERR! Please include the following file with any support request:
npm ERR!     C:\Projects\blabla-56fb3cfa20b3\npm-debug.log

[Pytanie]

Skąd może wynikać ten błąd podczas próby instalowania zależności?

Z góry dzięki za pomoc!

Answer 1

Node 6 i npm 3 to totalne antyki, mające z dobre 5-6 lat (jak nie więcej). Sam błąd wygląda, jakby npm próbowało łączyć się z rejestrem pakietów npm przy pomocy SSL3 – które już dawno zostało wyłączone jako przestarzały sposób zabezpieczania połączenia.

Proponowałbym zaktualizować npm-a:

npm i -g npm

i wówczas sprawdzić, czy działa.

Comments

Hmm... Tak myślałem że mogę mieć problem z wersją Node'a, więc zainstalowałem sobie NVM do zarządzania wersjami.

Teraz pobiłem Node'a do...

PS C:\WINDOWS\system32> npm -v
9.5.0
PS C:\WINDOWS\system32> node -v
v18.15.0

Teraz próbując zainstalować projekt mam:

npm notice Beginning October 4, 2021, all connections to the npm registry - including for package installation - must use TLS 1.2 or higher. You are currently using plaintext http to connect. Please visit the GitHub blog for more information: https://github.blog/2021-08-23-npm-registry-deprecating-tls-1-0-tls-1-1/
npm notice Beginning October 4, 2021, all connections to the npm registry - including for package installation - must use TLS 1.2 or higher. You are currently using plaintext http to connect. Please visit the GitHub blog for more information: https://github.blog/2021-08-23-npm-registry-deprecating-tls-1-0-tls-1-1/
npm WARN deprecated natives@1.1.6: This module relies on Node.js's internals and will break at some point. Do not use it, and update to graceful-fs@4.x.
npm WARN deprecated source-map-url@0.4.1: See https://github.com/lydell/source-map-url#deprecated
npm WARN deprecated csurf@1.11.0: Please use another csrf package
npm WARN deprecated minimatch@2.0.10: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
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 cryptiles@2.0.5: 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 mailcomposer@4.0.1: This project is unmaintained
npm WARN deprecated graceful-fs@1.2.3: please upgrade to graceful-fs 4 for compatibility with current and future versions of Node.js
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 boom@2.10.1: 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 nodemailer@2.7.2: All versions below 4.0.1 of Nodemailer are deprecated. See https://nodemailer.com/status/
npm WARN deprecated formidable@1.2.6: Please upgrade to latest, formidable@v2 or formidable@v3! Check these notes: https://bit.ly/2ZEqIau
npm WARN deprecated xmldom@0.1.31: Deprecated due to CVE-2021-21366 resolved in 0.5.0
npm WARN deprecated socks@1.1.9: If using 2.x branch, please upgrade to at least 2.1.6 to avoid a serious bug with socket data flow and an import issue introduced in 2.1.0
npm WARN deprecated minimatch@0.2.14: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm WARN deprecated sntp@1.0.9: 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 buildmail@4.0.1: This project is unmaintained
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 hoek@2.16.3: 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 request@2.81.0: request has been deprecated, see https://github.com/request/request/issues/3142
npm WARN deprecated messageformat@2.3.0: Package renamed as '@messageformat/core', see messageformat.github.io for more details. 'messageformat@4' will eventually provide a polyfill for Intl.MessageFormat, once it's been defined by Unicode & ECMA.
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 har-validator@4.2.1: this library is no longer supported
npm WARN deprecated hawk@3.1.3: 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 bson@1.0.9: Fixed a critical issue with BSON serialization documented in CVE-2019-2391, see https://bit.ly/2KcpXdo for more details
npm WARN deprecated mongodb@2.2.16: Please upgrade to 2.2.19 or higher
npm WARN deprecated ejs@1.0.0: Critical security bugs fixed in 2.5.5
npm WARN deprecated ejs@2.4.2: Critical security bugs fixed in 2.5.5
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 cleanup Failed to remove some directories [
npm WARN cleanup   [
npm WARN cleanup     'C:\\Projects\\blabla-56fb3cfa20b3\\node_modules',
npm WARN cleanup     [Error: EPERM: operation not permitted, rmdir 'C:\Projects\blabla-56fb3cfa20b3\node_modules\ejs-mate\node_modules\ejs\test\fixtures'] {
npm WARN cleanup       errno: -4048,
npm WARN cleanup       code: 'EPERM',
npm WARN cleanup       syscall: 'rmdir',
npm WARN cleanup       path: 'C:\\Projects\\blabla-56fb3cfa20b3\\node_modules\\ejs-mate\\node_modules\\ejs\\test\\fixtures'
npm WARN cleanup     }
npm WARN cleanup   ],
npm WARN cleanup   [
npm WARN cleanup     'C:\\Projects\\blabla-56fb3cfa20b3\\node_modules\\glob-watcher\\node_modules\\globule',
npm WARN cleanup     [Error: EPERM: operation not permitted, rmdir 'C:\Projects\blabla-56fb3cfa20b3\node_modules\glob-watcher\node_modules\globule\test\fixtures'] {
npm WARN cleanup       errno: -4048,
npm WARN cleanup       code: 'EPERM',
npm WARN cleanup       syscall: 'rmdir',
npm WARN cleanup       path: 'C:\\Projects\\blabla-56fb3cfa20b3\\node_modules\\glob-watcher\\node_modules\\globule\\test\\fixtures'
npm WARN cleanup     }
npm WARN cleanup   ],
npm WARN cleanup   [
npm WARN cleanup     'C:\\Projects\\blabla-56fb3cfa20b3\\node_modules\\glob-watcher\\node_modules',
npm WARN cleanup     [Error: EPERM: operation not permitted, rmdir 'C:\Projects\blabla-56fb3cfa20b3\node_modules\glob-watcher\node_modules\globule\test'] {
npm WARN cleanup       errno: -4048,
npm WARN cleanup       code: 'EPERM',
npm WARN cleanup       syscall: 'rmdir',
npm WARN cleanup       path: 'C:\\Projects\\blabla-56fb3cfa20b3\\node_modules\\glob-watcher\\node_modules\\globule\\test'
npm WARN cleanup     }
npm WARN cleanup   ]
npm WARN cleanup ]
npm ERR! code 1
npm ERR! path C:\Projects\blabla-56fb3cfa20b3\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:\Projects\blabla-56fb3cfa20b3\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:\\Projects\\blabla-56fb3cfa20b3\\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.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:\Projects\blabla-56fb3cfa20b3\node_modules\which\which.js:13:12)
npm ERR! gyp verb `which` failed     at F (C:\Projects\blabla-56fb3cfa20b3\node_modules\which\which.js:68:19)
npm ERR! gyp verb `which` failed     at E (C:\Projects\blabla-56fb3cfa20b3\node_modules\which\which.js:80:29)
npm ERR! gyp verb `which` failed     at C:\Projects\blabla-56fb3cfa20b3\node_modules\which\which.js:89:16
npm ERR! gyp verb `which` failed     at C:\Projects\blabla-56fb3cfa20b3\node_modules\isexe\index.js:42:5
npm ERR! gyp verb `which` failed     at C:\Projects\blabla-56fb3cfa20b3\node_modules\isexe\windows.js:36:5
npm ERR! gyp verb `which` failed     at FSReqCallback.oncomplete (node:fs:208:21)
npm ERR! gyp verb `which` failed  python2 Error: not found: python2
npm ERR! gyp verb `which` failed     at getNotFoundError (C:\Projects\blabla-56fb3cfa20b3\node_modules\which\which.js:13:12)
npm ERR! gyp verb `which` failed     at F (C:\Projects\blabla-56fb3cfa20b3\node_modules\which\which.js:68:19)
npm ERR! gyp verb `which` failed     at E (C:\Projects\blabla-56fb3cfa20b3\node_modules\which\which.js:80:29)
npm ERR! gyp verb `which` failed     at C:\Projects\blabla-56fb3cfa20b3\node_modules\which\which.js:89:16
npm ERR! gyp verb `which` failed     at C:\Projects\blabla-56fb3cfa20b3\node_modules\isexe\index.js:42:5
npm ERR! gyp verb `which` failed     at C:\Projects\blabla-56fb3cfa20b3\node_modules\isexe\windows.js:36:5
npm ERR! gyp verb `which` failed     at FSReqCallback.oncomplete (node:fs:208: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:\Users\konra\AppData\Local\Programs\Python\Python310\python.EXE
npm ERR! gyp ERR! configure error
npm ERR! gyp ERR! stack Error: Command failed: C:\Users\konra\AppData\Local\Programs\Python\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:419:12)
npm ERR! gyp ERR! stack     at ChildProcess.emit (node:events:513:28)
npm ERR! gyp ERR! stack     at maybeClose (node:internal/child_process:1091:16)
npm ERR! gyp ERR! stack     at ChildProcess._handle.onexit (node:internal/child_process:302:5)
npm ERR! gyp ERR! System Windows_NT 10.0.19045
npm ERR! gyp ERR! command "C:\\Program Files\\nodejs\\node.exe" "C:\\Projects\\blabla-56fb3cfa20b3\\node_modules\\node-gyp\\bin\\node-gyp.js" "rebuild" "--verbose" "--libsass_ext=" "--libsass_cflags=" "--libsass_ldflags=" "--libsass_library="
npm ERR! gyp ERR! cwd C:\Projects\blabla-56fb3cfa20b3\node_modules\node-sass
npm ERR! gyp ERR! node -v v18.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\konra\AppData\Local\npm-cache\_logs\2023-03-09T23_43_46_455Z-debug-0.log

Czyli dalej sypie...

---

Okeey, chyba brakuje mi Pythona2 na kompie. Spróbuję jutro zainstalować i sprawdzę czy pójdzie.

---

Ja bym jeszcze spróbował z nowym npm-em, ale na tym Node 6. Bo widzę, że sypło budowanie natywnego pakietu dla Node – czyli coś, co zmienia się między wersjami.

---

Chyba nie da rady podbić npm-a z tej niskiej wersji.

PS C:\WINDOWS\system32> npm -v
3.10.10
PS C:\WINDOWS\system32> npm i -g npm
npm ERR! Windows_NT 10.0.19045
npm ERR! argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "i" "-g" "npm"
npm ERR! node v6.9.4
npm ERR! npm  v3.10.10
npm ERR! code EPROTO
npm ERR! errno EPROTO
npm ERR! syscall write

npm ERR! write EPROTO 101057795:error:1408D07B:SSL routines:ssl3_get_key_exchange:bad signature:openssl\ssl\s3_clnt.c:2010:
npm ERR!
npm ERR!
npm ERR! If you need help, you may report this error at:
npm ERR!     <https://github.com/npm/npm/issues>

npm ERR! Please include the following file with any support request:
npm ERR!     C:\WINDOWS\system32\npm-debug.log

 

---

To chyba faktycznie zostaje próba z tym Pythonem, względnie bezpośredni download npm-a (chociaż ten skrypt pewnie nie zadziała pod Windowsem bez WSL-a lub git basha).

---

Zainstalowałem pythona2.7 i przeszedłem przez instrukcję instalację gulp.js na oficjalnej stronie https://gulpjs.com/docs/en/getting-started/quick-start. Gulp służy chyba do budowania frontów, więc może być potrzebny. Teraz mam wersje...

PS C:\Projects\blabla-56fb3cfa20b3> node --version
v8.11.1
PS C:\Projects\blabla-56fb3cfa20b3> npm --version        
5.6.0
PS C:\Projects\blabla-56fb3cfa20b3> npx --version
9.7.1
PS C:\Projects\blabla-56fb3cfa20b3> gulp --version
CLI version: 2.3.0
Local version: 3.9.1

Jak próbuję wywołać komendę gulp, to dostaję...

PS C:\Projects\blabla-56fb3cfa20b3> gulp
{ Error: Cannot find module 'gulp-less'
    at Function.Module._resolveFilename (module.js:547:15)
    at Function.Module._load (module.js:474:25)
    at Module.require (module.js:596:17)
    at require (internal/module.js:11:18)
    at Object.<anonymous> (C:\Projects\blabla-56fb3cfa20b3\gulpfile.js:4:12)
    at Module._compile (module.js:652:30)
    at Object.Module._extensions..js (module.js:663:10)
    at Module.load (module.js:565:32)
    at tryModuleLoad (module.js:505:12)
    at Function.Module._load (module.js:497:3) code: 'MODULE_NOT_FOUND' }

jak próbuję wywołać npm install to dostaję...

> node-sass@3.13.1 postinstall C:\Projects\blabla-56fb3cfa20b3\node_modules\node-sass
> node scripts/build.js

Building: C:\Program Files\nodejs\node.exe C:\Projects\blabla-56fb3cfa20b3\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:\\Projects\\blabla-56fb3cfa20b3\\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 node-gyp@3.8.0
gyp info using node@8.11.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 "python2" in the PATH
gyp verb `which` failed Error: not found: python2
gyp verb `which` failed     at getNotFoundError (C:\Projects\blabla-56fb3cfa20b3\node_modules\which\which.js:13:12)
gyp verb `which` failed     at F (C:\Projects\blabla-56fb3cfa20b3\node_modules\which\which.js:68:19)
gyp verb `which` failed     at E (C:\Projects\blabla-56fb3cfa20b3\node_modules\which\which.js:80:29)
gyp verb `which` failed     at C:\Projects\blabla-56fb3cfa20b3\node_modules\which\which.js:89:16
gyp verb `which` failed     at C:\Projects\blabla-56fb3cfa20b3\node_modules\isexe\index.js:42:5
gyp verb `which` failed     at C:\Projects\blabla-56fb3cfa20b3\node_modules\isexe\windows.js:36:5
gyp verb `which` failed     at FSReqWrap.oncomplete (fs.js:152:21)
gyp verb `which` failed  python2 { Error: not found: python2
gyp verb `which` failed     at getNotFoundError (C:\Projects\blabla-56fb3cfa20b3\node_modules\which\which.js:13:12)
gyp verb `which` failed     at F (C:\Projects\blabla-56fb3cfa20b3\node_modules\which\which.js:68:19)
gyp verb `which` failed     at E (C:\Projects\blabla-56fb3cfa20b3\node_modules\which\which.js:80:29)
gyp verb `which` failed     at C:\Projects\blabla-56fb3cfa20b3\node_modules\which\which.js:89:16
gyp verb `which` failed     at C:\Projects\blabla-56fb3cfa20b3\node_modules\isexe\index.js:42:5
gyp verb `which` failed     at C:\Projects\blabla-56fb3cfa20b3\node_modules\isexe\windows.js:36:5
gyp verb `which` failed     at FSReqWrap.oncomplete (fs.js:152:21)
gyp verb `which` failed   stack: 'Error: not found: python2\n    at getNotFoundError (C:\\Projects\\blabla-56fb3cfa20b3\\node_modules\\which\\which.js:13:12)\n    at F (C:\\Projects\\blabla-56fb3cfa20b3\\node_modules\\which\\which.js:68:19)\n    at E (C:\\Projects\\blabla-56fb3cfa20b3\\node_modules\\which\\which.js:80:29)\n    at C:\\Projects\\blabla-56fb3cfa20b3\\node_modules\\which\\which.js:89:16\n    at C:\\Projects\\blabla-56fb3cfa20b3\\node_modules\\isexe\\index.js:42:5\n    at C:\\Projects\\blabla-56fb3cfa20b3\\node_modules\\isexe\\windows.js:36:5\n    at FSReqWrap.oncomplete (fs.js:152: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:\Python27\python.EXE
gyp verb check python version `C:\Python27\python.EXE -c "import sys; print "2.7.2
gyp verb check python version .%s.%s" % sys.version_info[:3];"` returned: %j
gyp verb get node dir no --target version specified, falling back to host node version: 8.11.1
gyp verb command install [ '8.11.1' ]
gyp verb install input version string "8.11.1"
gyp verb install installing version: 8.11.1
gyp verb install --ensure was passed, so won't reinstall if already installed
gyp verb install version is already installed, need to check "installVersion"
gyp verb got "installVersion" 9
gyp verb needs "installVersion" 9
gyp verb install version is good
gyp verb get node dir target node version installed: 8.11.1
gyp verb build dir attempting to create "build" dir: C:\Projects\blabla-56fb3cfa20b3\node_modules\node-sass\build
gyp verb build dir "build" dir needed to be created? C:\Projects\blabla-56fb3cfa20b3\node_modules\node-sass\build
gyp verb find vs2017 Found installation at: C:\Program Files\Microsoft Visual Studio\2022\Community
gyp verb find vs2017   - Missing Visual Studio C++ core features (Microsoft.VisualStudio.VC.MSBuild.Base)
gyp verb find vs2017   - Missing VC++ 2017 v141 toolset (x86,x64) (Microsoft.VisualStudio.Component.VC.Tools.x86.x64)
gyp verb find vs2017   - Missing a Windows SDK (Microsoft.VisualStudio.Component.Windows10SDK.* or Microsoft.VisualStudio.Component.Windows81SDK)
gyp verb find vs2017   - Some required components are missing, not using this installation
gyp verb Not using VS2017: No usable installation of VS2017 found
gyp verb build/config.gypi creating config file
gyp verb build/config.gypi writing out config file: C:\Projects\blabla-56fb3cfa20b3\node_modules\node-sass\build\config.gypi
gyp verb config.gypi checking for gypi file: C:\Projects\blabla-56fb3cfa20b3\node_modules\node-sass\config.gypi
gyp verb common.gypi checking for gypi file: C:\Projects\blabla-56fb3cfa20b3\node_modules\node-sass\common.gypi
gyp verb gyp gyp format was not specified; forcing "msvs"
gyp info spawn C:\Python27\python.EXE
gyp info spawn args [ 'C:\\Projects\\blabla-56fb3cfa20b3\\node_modules\\node-gyp\\gyp\\gyp_main.py',
gyp info spawn args   'binding.gyp',
gyp info spawn args   '-f',
gyp info spawn args   'msvs',
gyp info spawn args   '-G',
gyp info spawn args   'msvs_version=auto',
gyp info spawn args   '-I',
gyp info spawn args   'C:\\Projects\\blabla-56fb3cfa20b3\\node_modules\\node-sass\\build\\config.gypi',
gyp info spawn args   '-I',
gyp info spawn args   'C:\\Projects\\blabla-56fb3cfa20b3\\node_modules\\node-gyp\\addon.gypi',
gyp info spawn args   '-I',
gyp info spawn args   'C:\\Users\\konra\\.node-gyp\\8.11.1\\include\\node\\common.gypi',
gyp info spawn args   '-Dlibrary=shared_library',
gyp info spawn args   '-Dvisibility=default',
gyp info spawn args   '-Dnode_root_dir=C:\\Users\\konra\\.node-gyp\\8.11.1',
gyp info spawn args   '-Dnode_gyp_dir=C:\\Projects\\blabla-56fb3cfa20b3\\node_modules\\node-gyp',
gyp info spawn args   '-Dnode_lib_file=C:\\Users\\konra\\.node-gyp\\8.11.1\\<(target_arch)\\node.lib',
gyp info spawn args   '-Dmodule_root_dir=C:\\Projects\\blabla-56fb3cfa20b3\\node_modules\\node-sass',
gyp info spawn args   '-Dnode_engine=v8',
gyp info spawn args   '--depth=.',
gyp info spawn args   '--no-parallel',
gyp info spawn args   '--generator-output',
gyp info spawn args   'C:\\Projects\\blabla-56fb3cfa20b3\\node_modules\\node-sass\\build',
gyp info spawn args   '-Goutput_dir=.' ]
gyp verb command build []
gyp verb build type Release
gyp verb architecture x64
gyp verb node dev dir C:\Users\konra\.node-gyp\8.11.1
gyp verb found first Solution file build/binding.sln
gyp verb could not find "msbuild.exe" in PATH - finding location in registry
gyp info spawn C:\Windows\Microsoft.NET\Framework\v4.0.30319\msbuild.exe
gyp info spawn args [ 'build/binding.sln',
gyp info spawn args   '/nologo',
gyp info spawn args   '/p:Configuration=Release;Platform=x64' ]
Projekty w tym rozwiązaniu są tworzone po kolei. Abu umożliwić tworzenie równoległe, dodaj przełącznik "/m".
Kompilacja rozpoczęła się 25.03.2023 01:22:10.
Projekt "C:\Projects\blabla-56fb3cfa20b3\node_modules\node-sass\build\binding.sln" w węźle 1 (domyślne elementy docelowe).
ValidateSolutionConfiguration:
  Tworzenie konfiguracji rozwiązania "Release|x64".
MSBUILD : error MSB3428: Nie można załadować składnika Visual C++ "VCBuild.exe". Aby rozwiązać ten problem:1) zainstaluj zesta
w .NET Framework 2.0 SDK, 2) zainstaluj program Microsoft Visual Studio 2005 lub 3) dodaj lokalizację składnika do ścieżki sys
temowej, jeżeli jest zainstalowana w jakiejś lokalizacji.  [C:\Projects\blabla-56fb3cfa20b3\node_modules\node-sass\build\bindi
ng.sln]
Kompilowanie projektu "C:\Projects\blabla-56fb3cfa20b3\node_modules\node-sass\build\binding.sln" wykonane (domyślne elementy d
ocelowe) - NIEPOWODZENIE.


Kompilacja NIE POWIODŁA SIĘ.

"C:\Projects\blabla-56fb3cfa20b3\node_modules\node-sass\build\binding.sln" (domyślny element docelowy) (1)->
(element docelowy _src_\libsass) ->
  MSBUILD : error MSB3428: Nie można załadować składnika Visual C++ "VCBuild.exe". Aby rozwiązać ten problem:1) zainstaluj zes
taw .NET Framework 2.0 SDK, 2) zainstaluj program Microsoft Visual Studio 2005 lub 3) dodaj lokalizację składnika do ścieżki s
ystemowej, jeżeli jest zainstalowana w jakiejś lokalizacji.  [C:\Projects\blabla-56fb3cfa20b3\node_modules\node-sass\build\bin
ding.sln]

    Ostrzeżenia: 0
    Liczba błędów: 1

Czas, który upłynął: 00:00:00.19
gyp ERR! build error
gyp ERR! stack Error: `C:\Windows\Microsoft.NET\Framework\v4.0.30319\msbuild.exe` failed with exit code: 1
gyp ERR! stack     at ChildProcess.onExit (C:\Projects\blabla-56fb3cfa20b3\node_modules\node-gyp\lib\build.js:262:23)
gyp ERR! stack     at emitTwo (events.js:126:13)
gyp ERR! stack     at ChildProcess.emit (events.js:214:7)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:198:12)
gyp ERR! System Windows_NT 10.0.19045
gyp ERR! command "C:\\Program Files\\nodejs\\node.exe" "C:\\Projects\\blabla-56fb3cfa20b3\\node_modules\\node-gyp\\bin\\node-gyp.js" "rebuild" "--verbose" "--libsass_ext=" "--libsass_cflags=" "--libsass_ldflags=" "--libsass_library="
gyp ERR! cwd C:\Projects\blabla-56fb3cfa20b3\node_modules\node-sass
gyp ERR! node -v v8.11.1
gyp ERR! node-gyp -v v3.8.0
gyp ERR! not ok
Build failed with error code: 1
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! node-sass@3.13.1 postinstall: `node scripts/build.js`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the node-sass@3.13.1 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\konra\AppData\Roaming\npm-cache\_logs\2023-03-25T00_22_11_196Z-debug.log

to chyba coś z node-sass, ale nie wiem jak to naprawić

---

Z błędu wynika, że nie masz zainstalowanego środowiska .NET:

MSBUILD : error MSB3428: Nie można załadować składnika Visual C++ "VCBuild.exe". Aby rozwiązać ten problem:1) zainstaluj zestaw .NET Framework 2.0 SDK, 2) zainstaluj program Microsoft Visual Studio 2005 lub 3) dodaj lokalizację składnika do ścieżki systemowej, jeżeli jest zainstalowana w jakiejś lokalizacji.  [C:\Projects\blabla-56fb3cfa20b3\node_modules\node-sass\build\binding.sln]