qwik: [π] `pnpm create qwik@latest` asks to install dependencies but does not install them
Which component is affected?
Qwik Runtime
Describe the bug
Letβs create a Qwik App β¨ (v1.1.1) β β Where would you like to create your new project? (Use β.β or β./β for current directory) β ./qwik-app β β Creating new project in D:\Source\qwik-app β¦ π β β Select a starter β Basic App (QwikCity) β β Would you like to install pnpm dependencies? β Yes β β Initialize a new git repository? β Yes β β Created App π° β β Git initialized π² β β Failed to install dependencies π
Reproduction
https://stackblitz.com/edit/qwik-starter
Steps to reproduce
pnpm create qwik@latest
System Info
System:
OS: Windows 10 10.0.22621
CPU: (8) x64 Intel(R) Core(TM) i7-10510U CPU @ 1.80GHz
Memory: 1012.99 MB / 15.77 GB
Binaries:
Node: 20.1.0 - C:\Program Files\nodejs\node.EXE
Yarn: 3.5.1 - C:\Program Files\nodejs\yarn.CMD
npm: 9.6.4 - C:\Program Files\nodejs\npm.CMD
Browsers:
Edge: Spartan (44.22621.1702.0), Chromium (113.0.1774.35)
Internet Explorer: 11.0.22621.1
npmPackages:
@builder.io/qwik: ^1.1.1 => 1.1.1
@builder.io/qwik-city: ^1.1.1 => 1.1.1
undici: 5.22.0 => 5.22.0
vite: 4.3.5 => 4.3.5
Additional Information
No response
About this issue
- Original URL
- State: open
- Created a year ago
- Reactions: 1
- Comments: 22 (10 by maintainers)
Ok! This gives me an idea of whatβs going on!! We should be able to fix it in next release
Just to expand a bit from the previous comment - I tried
bun
,npm
andyarn
all coming up with the same issue.Sry to reopen this one @mhevery . I assume the problem on this issue is the background install which starts to download the npm packages as early as possible and moves them then into the final dir. the issue you linked is caused by the fact, that
yarn create qwik@latest
doesnβt exist. butyarn create qwik
works as expected π (https://qwik.builder.io/docs/getting-started/#create-an-app-using-the-cli)Yes, sorry I forgot to mention it:
Any Linux dev system running systemd (probably most) will fail with this because
tmpfs
is in RAM and you canβt perform a move from one device to another, since move/rename is supposed to be atomic.In the case of cross-device like this, the cli will need to copy and remove the original instead.
Same for scenarios like the one in this issue with the temp/store on a different drive from the project in Windows, etc.
Facing same issue with npm (v9.6.6) (OS: Archlinux)
Can you try again in 1.1.2? it should print the error message!