-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
Move library results in module already exists #4600
Comments
I think this one is loosely related, in the sense that the |
That was my assumption as well. if the rootDir starts with the same thing there seems to be some issues. |
Indeed. I've been using this to get around it, but it's not ideal.
|
Ya same, usually just tack a |
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. |
Please don't close this. |
^ |
@yharaskrik @beeman this was solved in #6507 and it was released in the latest version. I'm closing this one, if you still think this is an issue, please feel free to reopen it or create a new issue. |
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
With directory structure:
When I try and run
yarn nx g move --project builder-feature-browser builder/feature/browser
(ie. one level deeper) so I have the resulting dir structureDoes not work. See logs below.
Expected Behavior
Move should work as nothing is conflicting (it is being moved to an entirely different folder)
Steps to Reproduce
https://github.com/yharaskrik/nx-move-project-module-already-exists
Clone and run
yarn nx g move --project builder-feature-browser builder/feature/browser
Failure Logs
Environment
The text was updated successfully, but these errors were encountered: