Closed zanatoshi closed 1 year ago
These steps failed to create a temp-workspace in your repo. I don't see why it would. it does the same thing where you run npx -y create-nx-workspace@latest temp-workspace --appName=identity-frontend --preset=react-monorepo --style=css --bundler=vite --packageManager=yarn --nxCloud
at workspace root. it should be same behaviour for private vs public repo.
If I run this command NX_VERBOSE_LOGGING=true npx -y create-nx-workspace@latest temp-workspace --appName=identity-frontend --preset=react-monorepo --style=css --bundler=vite --packageManager=yarn
, I have this result:
> NX Failed to create a workspace.
Error: error Command failed with exit code 1.
Stack: CreateNxWorkspaceError: error Command failed with exit code 1.
at /home/florian/.npm/_npx/505743838affa773/node_modules/create-nx-workspace/src/utils/child-process-utils.js:38:21
at ChildProcess.exithandler (node:child_process:427:5)
at ChildProcess.emit (node:events:513:28)
at maybeClose (node:internal/child_process:1091:16)
at ChildProcess._handle.onexit (node:internal/child_process:302:5)
If I try in an empty folder, it works.
Let me know if you need any other info.
@zanatoshi is there already a temp-workspace folder in your workspace? if so could you delete the folder and run the command again NX_VERBOSE_LOGGING=true npx -y create-nx-workspace@latest temp-workspace --appName=identity-frontend --preset=react-monorepo --style=css --bundler=vite --packageManager=yarn
?
if this does not work, could you paste the yarn-error.log
under temp-workspace?
I have the same issue here
https://github.com/yarnpkg/berry/issues/625 <- is the issue
is it an issue with yarn? when there is yarn.lock already in the workspace, there is some issue doing yarn install
for create-nx-workspace?
would delete yarn.lock
solve this issue then? when run nx init
it will override your package.json anyway.
So if I delete yarn.lock, then it use npm instead which go further than yarn but still failed because of missing npm lock file.
This issue has been automatically marked as stale because it hasn't had any recent activity. It will be closed in 14 days if no further activity occurs. If we missed this issue please reply to keep it active. Thanks for being a part of the Nx community! ๐
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 a CRA react app repository, migrating to an integrated NX repo with Vite is failing.
Expected Behavior
Expect to migrate the app to vite in a NX monorepo
GitHub Repo
No response
Steps to Reproduce
NX_VERBOSE_LOGGING=true npx nx@latest init --integrated --force --nxCloud
Nx Report
Failure Logs
Operating System
Additional Information
This is a private project, can't give a repository link. Could not reproduce in a public repository. Anyway I can debug this somehow ?
Also tried on macOS