-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
Failed to create a workspace #28235
Comments
Hi @escwxyz , got any solution? I'm getting one similar issues while creating a workspace using yarn.
And my error log looks like this
|
Stuck in the step of creating workspace, also. Any idea? DescriptionWhen attempting to initialize a new Nx workspace using the command Steps to Reproduce
Error Message
Environment
Attempted Solutions
Expected BehaviorSuccessfully create an Nx workspace without encountering redirect errors. Actual BehaviorWorkspace creation fails with a "Maximum number of redirects exceeded" error. |
@wangyinyuan Have you tried creating without the E2E test runners? Try skipping that E2E test suite and see if it is working.
|
@nvinay-litmus7 Quite sad. I tried setting E2E to
|
@wangyinyuan I just tried creating a new workspace. Sending you the steps below which actually worked for me. I'm using an M-series mac. Also using yarn as the package manager to create this, because npm is always throwing me an error while creating. But whenever I select an E2E option this approach will fail but if I skip and chose none it is working fine. Steps:
|
@nvinay-litmus7 Thanks for the reminder, I didn't specify a pm and used npm by default, but after I specified yarn as the pm and disabled E2E, it still didn't work, so I tried skipping the CI again and it finally worked. Here is my successful case:
|
I took a look if I could reproduce, and using A workaround at the moment is to use another package manager if possible, while I investigate this issue. |
@ndcunningham With npm also if we are opting for E2E it is getting failed. Please find the details below:
|
This issue has been closed for more than 30 days. If this issue is still occuring, please open a new issue with more recent context. |
## Current Behavior On Windows, when packageManager=pnpm, `create-nx-workspace` fails due to an issue with `child_process.spawn`. Using `spawn`, the `@nx/workspace:preset` generator is executed twice when `packageManager=pnpm`, causing the overall create-nx-workspace flow to fail, even though most things have been set up correctly to that point. Using `fork` has shown success. ## Expected Behavior Running `create-nx-workspace --packageManager=pnpm` should work on Windows ## Fixes Fixes #20222 Fixes #27270 Fixes #22917 Fixes #22312 Fixes #28710 Fixes #28289 Fixes #28235 Fixes #22383 Fixes #21742 Fixes #20270
Current Behavior
Failed to create a brand new workspace
Expected Behavior
The CLI shall create a new workspace as expected.
GitHub Repo
No response
Steps to Reproduce
npx create-nx-workspace@latest project-name --verbose
Nx Report
The project is not even created, so the `nx report` is not available at this time.
Failure Logs
The text was updated successfully, but these errors were encountered: