Open helgardferreira opened 8 months ago
If I downgrade to v15.9.2 then I am able to create a nx workspace. The @latest
, @previous
, and @canary
versions are all not functioning.
Update: after successfully running npx create-nx-workspace@15.9.2
I noticed the CLI mentioned the following:
Directory is already under version control. Skipping initialization of git.
Context: I have git setup for neovim and tmux that rests at ~/
that ignores (via .gitignore) everything except for my neovim and tmux configuration.
After some experimenting I was able to get npx create-nx-workspace@latest
to work if I create a folder (in my intended directory) and first git init
before running nps create-nx-workspace@latest
.
My theory is there is something wrong with the CLI's logic when certain commands are executed within a directory that is nested within a git repo with certain .gitignore
rules.
same as this issue https://github.com/nrwl/nx/issues/20270
Current Behavior
Currently if I run
npx create-nx-workspace
with or without a preset, whether the setup is package-based or integrated, etc. The CLI hangs indefinitely onCreating your workspace
.Expected Behavior
The expected behaviour is for the
create-nx-workspace
to work on any mainstream operating system.GitHub Repo
No response
Steps to Reproduce
npx create-nx-workspace
on MacOS aarm64 SonomaNx Report
Failure Logs
No response
Package Manager Version
npm 9.8.0
Operating System
Additional Information
CLI Output: