Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Quick Install Failed #3354

Open
LimesWeb opened this issue Feb 9, 2025 · 7 comments
Open

Quick Install Failed #3354

LimesWeb opened this issue Feb 9, 2025 · 7 comments

Comments

@LimesWeb
Copy link

LimesWeb commented Feb 9, 2025

Hi, im trying to setup a Testproject with Vendure but the Quickinstallation seems to fail for me. Im on the Typescript Version 5.3.3. as suggested.

The Logs are in the Attached Txt File.

2025-02-09T10_50_48_793Z-debug-0.log

Here a snipit:

3405 info run better-sqlite3@9.6.0 install { code: 1, signal: null }
3406 warn cleanup Failed to remove some directories [
3406 warn cleanup [
3406 warn cleanup '\\?\C:\Users\Gabriel\Documents\OneDrive\Projekte\WebsiteTest\my-shop\node_modules\@apollo',
3406 warn cleanup [Error: EPERM: operation not permitted, rmdir 'C:\Users\Gabriel\Documents\OneDrive\Projekte\WebsiteTest\my-shop\node_modules@apollo\server\dist\esm'] {
3406 warn cleanup errno: -4048,
3406 warn cleanup code: 'EPERM',
3406 warn cleanup syscall: 'rmdir',
3406 warn cleanup path: 'C:\Users\Gabriel\Documents\OneDrive\Projekte\WebsiteTest\my-shop\node_modules\@apollo\server\dist\esm'
3406 warn cleanup }
3406 warn cleanup ]
3406 warn cleanup ]
3407 verbose stack Error: command failed
3407 verbose stack at promiseSpawn (C:\ProgramData\nvm\v22.11.0\node_modules\npm\node_modules@npmcli\promise-spawn\lib\index.js:22:22)
3407 verbose stack at spawnWithShell (C:\ProgramData\nvm\v22.11.0\node_modules\npm\node_modules@npmcli\promise-spawn\lib\index.js:124:10)
3407 verbose stack at promiseSpawn (C:\ProgramData\nvm\v22.11.0\node_modules\npm\node_modules@npmcli\promise-spawn\lib\index.js:12:12)
3407 verbose stack at runScriptPkg (C:\ProgramData\nvm\v22.11.0\node_modules\npm\node_modules@npmcli\run-script\lib\run-script-pkg.js:77:13)
3407 verbose stack at runScript (C:\ProgramData\nvm\v22.11.0\node_modules\npm\node_modules@npmcli\run-script\lib\run-script.js:9:12)
3407 verbose stack at C:\ProgramData\nvm\v22.11.0\node_modules\npm\node_modules@npmcli\arborist\lib\arborist\rebuild.js:329:17
3407 verbose stack at run (C:\ProgramData\nvm\v22.11.0\node_modules\npm\node_modules\promise-call-limit\dist\commonjs\index.js:67:22)
3407 verbose stack at C:\ProgramData\nvm\v22.11.0\node_modules\npm\node_modules\promise-call-limit\dist\commonjs\index.js:84:9
3407 verbose stack at new Promise ()
3407 verbose stack at callLimit (C:\ProgramData\nvm\v22.11.0\node_modules\npm\node_modules\promise-call-limit\dist\commonjs\index.js:35:69)
3408 verbose pkgid better-sqlite3@9.6.0
3409 error code 1
3410 error path C:\Users\Gabriel\Documents\OneDrive\Projekte\WebsiteTest\my-shop\node_modules\better-sqlite3
3411 error command failed
3412 error command C:\WINDOWS\system32\cmd.exe /d /s /c prebuild-install || node-gyp rebuild --release
3413 error prebuild-install info begin Prebuild-install version 7.1.3
3413 error prebuild-install info looking for local prebuild @ prebuilds\better-sqlite3-v9.6.0-node-v127-win32-x64.tar.gz
3413 error prebuild-install info looking for cached prebuild @ C:\Users\Gabriel\AppData\Local\npm-cache_prebuilds\c7460d-better-sqlite3-v9.6.0-node-v127-win32-x64.tar.gz
3413 error prebuild-install http request GET https://github.com/WiseLibs/better-sqlite3/releases/download/v9.6.0/better-sqlite3-v9.6.0-node-v127-win32-x64.tar.gz
3413 error prebuild-install http 404 https://github.com/WiseLibs/better-sqlite3/releases/download/v9.6.0/better-sqlite3-v9.6.0-node-v127-win32-x64.tar.gz
3413 error prebuild-install warn install No prebuilt binaries found (target=22.11.0 runtime=node arch=x64 libc= platform=win32)
3413 error gyp info it worked if it ends with ok
3413 error gyp verb cli [
3413 error gyp verb cli 'C:\Program Files\nodejs\node.exe',
3413 error gyp verb cli 'C:\ProgramData\nvm\v22.11.0\node_modules\npm\node_modules\node-gyp\bin\node-gyp.js',
3413 error gyp verb cli 'rebuild',
3413 error gyp verb cli '--release'
3413 error gyp verb cli ]
3413 error gyp info using node-gyp@10.2.0
3413 error gyp info using node@22.11.0 | win32 | x64
3413 error gyp verb clean removing "build" directory
3413 error gyp verb find Python Python is not set from command line or npm configuration
3413 error gyp verb find Python Python is not set from environment variable PYTHON
3413 error gyp verb find Python checking if the py launcher can be used to find Python 3
3413 error gyp verb find Python - executing "py.exe" to get Python 3 executable path
3413 error gyp verb find Python - executable path is "C:\Users\Gabriel\AppData\Local\Programs\Python\Python312\python.exe"
3413 error gyp verb find Python - executing "C:\Users\Gabriel\AppData\Local\Programs\Python\Python312\python.exe" to get version
3413 error gyp verb find Python - version is "3.12.0"
3413 error gyp info find Python using Python version 3.12.0 found at "C:\Users\Gabriel\AppData\Local\Programs\Python\Python312\python.exe"
3413 error gyp verb get node dir no --target version specified, falling back to host node version: 22.11.0
3413 error gyp verb install input version string "22.11.0"
3413 error gyp verb install installing version: 22.11.0
3413 error gyp verb install --ensure was passed, so won't reinstall if already installed
3413 error gyp verb install version is already installed, need to check "installVersion"
3413 error gyp verb got "installVersion" 11
3413 error gyp verb needs "installVersion" 11
3413 error gyp verb install version is good
3413 error gyp verb on Windows; need to check node.lib
3413 error gyp verb get node dir target node version installed: 22.11.0
3413 error gyp verb build dir attempting to create "build" dir: C:\Users\Gabriel\Documents\OneDrive\Projekte\WebsiteTest\my-shop\node_modules\better-sqlite3\build
3413 error gyp verb build dir "build" dir needed to be created? Yes
3413 error gyp verb find VS msvs_version not set from command line or npm config
3413 error gyp verb find VS VCINSTALLDIR not set, not running in VS Command Prompt
3413 error gyp verb find VS could not use PowerShell to find Visual Studio 2017 or newer, try re-running with '--loglevel silly' for more details.
3413 error gyp verb find VS
3413 error gyp verb find VS Failure details: undefined
3413 error gyp verb find VS checking VS2022 (17.12.35506.116) found at:
3413 error gyp verb find VS "C:\Program Files\Microsoft Visual Studio\2022\Community"
3413 error gyp verb find VS - found "Visual Studio C++ core features"
3413 error gyp verb find VS - missing any VC++ toolset
3413 error gyp verb find VS could not find a version of Visual Studio 2017 or newer to use
3413 error gyp verb find VS not looking for VS2017 as it is only supported up to Node.js 21
3413 error gyp verb find VS not looking for VS2017 as it is only supported up to Node.js 21
3413 error gyp verb find VS not looking for VS2017 as it is only supported up to Node.js 21
3413 error gyp verb find VS not looking for VS2015 as it is only supported up to Node.js 18
3413 error gyp verb find VS not looking for VS2013 as it is only supported up to Node.js 8
3413 error gyp ERR! find VS
3413 error gyp ERR! find VS msvs_version not set from command line or npm config
3413 error gyp ERR! find VS VCINSTALLDIR not set, not running in VS Command Prompt
3413 error gyp ERR! find VS could not use PowerShell to find Visual Studio 2017 or newer, try re-running with '--loglevel silly' for more details.
3413 error gyp ERR! find VS
3413 error gyp ERR! find VS Failure details: undefined
3413 error gyp ERR! find VS checking VS2022 (17.12.35506.116) found at:
3413 error gyp ERR! find VS "C:\Program Files\Microsoft Visual Studio\2022\Community"
3413 error gyp ERR! find VS - found "Visual Studio C++ core features"
3413 error gyp ERR! find VS - missing any VC++ toolset
3413 error gyp ERR! find VS could not find a version of Visual Studio 2017 or newer to use
3413 error gyp ERR! find VS not looking for VS2017 as it is only supported up to Node.js 21
3413 error gyp ERR! find VS not looking for VS2017 as it is only supported up to Node.js 21
3413 error gyp ERR! find VS not looking for VS2017 as it is only supported up to Node.js 21
3413 error gyp ERR! find VS not looking for VS2015 as it is only supported up to Node.js 18
3413 error gyp ERR! find VS not looking for VS2013 as it is only supported up to Node.js 8
3413 error gyp ERR! find VS
3413 error gyp ERR! find VS **************************************************************
3413 error gyp ERR! find VS You need to install the latest version of Visual Studio
3413 error gyp ERR! find VS including the "Desktop development with C++" workload.
3413 error gyp ERR! find VS For more information consult the documentation at:
3413 error gyp ERR! find VS https://github.com/nodejs/node-gyp#on-windows
3413 error gyp ERR! find VS **************************************************************
3413 error gyp ERR! find VS
3413 error gyp ERR! configure error
3413 error gyp ERR! stack Error: Could not find any Visual Studio installation to use
3413 error gyp ERR! stack at VisualStudioFinder.fail (C:\ProgramData\nvm\v22.11.0\node_modules\npm\node_modules\node-gyp\lib\find-visualstudio.js:118:11)
3413 error gyp ERR! stack at VisualStudioFinder.findVisualStudio (C:\ProgramData\nvm\v22.11.0\node_modules\npm\node_modules\node-gyp\lib\find-visualstudio.js:74:17)
3413 error gyp ERR! stack at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
3413 error gyp ERR! stack at async createBuildDir (C:\ProgramData\nvm\v22.11.0\node_modules\npm\node_modules\node-gyp\lib\configure.js:112:18)
3413 error gyp ERR! stack at async run (C:\ProgramData\nvm\v22.11.0\node_modules\npm\node_modules\node-gyp\bin\node-gyp.js:81:18)
3413 error gyp ERR! System Windows_NT 10.0.22621
3413 error gyp ERR! command "C:\Program Files\nodejs\node.exe" "C:\ProgramData\nvm\v22.11.0\node_modules\npm\node_modules\node-gyp\bin\node-gyp.js" "rebuild" "--release"
3413 error gyp ERR! cwd C:\Users\Gabriel\Documents\OneDrive\Projekte\WebsiteTest\my-shop\node_modules\better-sqlite3
3413 error gyp ERR! node -v v22.11.0
3413 error gyp ERR! node-gyp -v v10.2.0
3413 error gyp ERR! not ok
3414 silly unfinished npm timer reify 1739098249484
3415 silly unfinished npm timer reify:build 1739098278204
3416 silly unfinished npm timer build 1739098278204
3417 silly unfinished npm timer build:deps 1739098278205
3418 silly unfinished npm timer build:run:install 1739098278437
3419 silly unfinished npm timer build:run:install:node_modules/better-sqlite3 1739098278477
3420 verbose cwd C:\Users\Gabriel\Documents\OneDrive\Projekte\WebsiteTest\my-shop
3421 verbose os Windows_NT 10.0.22621
3422 verbose node v22.11.0
3423 verbose npm v10.9.0
3424 verbose exit 1
3425 verbose code 1
3426 error A complete log of this run can be found in: C:\Users\Gabriel\AppData\Local\npm-cache_logs\2025-02-09T10_50_48_793Z-debug-0.log

@michaelbromley
Copy link
Member

Hi, I'm wondering if this has anything to do with attempting to npm install onto OneDrive. Can you try it on a non-OneDrive location and see if that resolves it?

@LimesWeb
Copy link
Author

Thanks for the quick reply!
I tried it, but still get the same error. Is there anything else I could try?

@michaelbromley
Copy link
Member

Sorry, not sure what to suggest but when I googled, there seem to be a lot of results that might contain useful info. I am also using Windows 11 by the way. I haven't run into this.

@LimesWeb
Copy link
Author

Unfortunately, I still haven't found a solution. The suggested solutions I have found have not worked.

@LimesWeb
Copy link
Author

I don't understand that. I have now tried to install it on a new windows, on a new linux fedora and tried for hours to fix the problem with gyp, but it still doesn't work.
If I only have to have typescript and nodejs (higher than 18) installed, then I don't know what to do if it doesn't work on 3 systems at the same time

@dlhck
Copy link
Collaborator

dlhck commented Feb 20, 2025

@LimesWeb my recommendation: Use WSL2 on Windows.

@michaelbromley
Copy link
Member

What's the log output when it fails on Linux?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants