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

[🐞]CLI - temp .create folder not always being removed (see scenarios in description) #7351

Open
Shane-Donlon opened this issue Feb 20, 2025 · 0 comments
Labels
STATUS-1: needs triage New issue which needs to be triaged TYPE: bug Something isn't working

Comments

@Shane-Donlon
Copy link
Contributor

Which component is affected?

Starters / CLI

Describe the bug

Hey there,
Just to officially log this for tracking.

So when running npm create qwik@latest the temp .create-qwik folder not always being removed.

Example A)
Only an issue on Windows but see the something went wrong response.

 Let's create a  Qwik App  ✨ (v1.12.0)
│
◇  Where would you like to create your new project? (Use '.' or './' for current directory)
│  ./testing-qwik-cli
│
●  Creating new project in {location of stuff}  ... 🐇
│
◇  Select a starter
│  Empty App (Qwik City + Qwik)
│
◇  Would you like to install npm dependencies?
│  No
│
◇  Initialize a new git repository?
│  No
│
▲  Something went wrong
◇  App Created 🐰

screenshot showing the folder not being deleted

Example B)
This is an issue on Linux & Windows.

Not a big issue, but just to have it documented somewhere.

┌  Let's create a  Qwik App  ✨ (v1.12.0)
│
◇  Where would you like to create your new project? (Use '.' or './' for current
directory)
│  ./qwik-app
│
●  Creating new project in  {directory Name} ... 🐇
│
■  Select a starter
│  Empty App (Qwik City + Qwik)
│
└  Operation cancelled.

Screenshot of the create folder modified time and current time (.create-qwik-12a6diouw46 foldername)
.create-qwik folder with time of modification and current time

Reproduction

CLI issue locally

Steps to reproduce

npm create qwik@latest and see responses above.

System Info

Dual boot system with Windows and Linux, but was always an issue on Windows. 

System:
    OS: Linux 6.8 Linux Mint 22.1 (Xia)
    CPU: (16) x64 AMD Ryzen 9 6900HX with Radeon Graphics
    Memory: 25.77 GB / 28.13 GB
    Container: Yes
    Shell: 5.2.21 - /bin/bash
  Binaries:
    Node: 22.14.0 - ~/.nvm/versions/node/v22.14.0/bin/node
    npm: 11.1.0 - ~/.nvm/versions/node/v22.14.0/bin/npm
    pnpm: 10.4.1 - ~/.nvm/versions/node/v22.14.0/bin/pnpm
  Browsers:
    Chrome: 133.0.6943.98

Laptop that also had the issue
System:
    OS: Windows 11 10.0.22631
    CPU: (8) x64 Intel(R) Core(TM) i5-1035G1 CPU @ 1.00GHz
    Memory: 439.29 MB / 7.74 GB
  Binaries:
    Node: 22.11.0 - C:\Program Files\nodejs\node.EXE
    Yarn: 1.22.21 - ~\AppData\Roaming\npm\yarn.CMD
    npm: 10.9.0 - C:\Program Files\nodejs\npm.CMD
    pnpm: 9.14.2 - ~\AppData\Roaming\npm\pnpm.CMD
    bun: 1.1.38 - ~\AppData\Roaming\npm\bun.CMD
  Browsers:
    Edge: Chromium (127.0.2651.74)

Additional Information

No response

@Shane-Donlon Shane-Donlon added STATUS-1: needs triage New issue which needs to be triaged TYPE: bug Something isn't working labels Feb 20, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
STATUS-1: needs triage New issue which needs to be triaged TYPE: bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant