-
Notifications
You must be signed in to change notification settings - Fork 12k
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
Error: An old project has been detected, which needs to be updated to Angular CLI 6. #10145
Comments
The project structure is actually right! We had a different multi-project structure that we reverted back to the current one. The key difference is in the We're looking at adding the multi-project first structure as an options in the future for new projects. The error is not right though. I think we're incorrectly picking up a |
Does it recursively look up the tree until it finds the file, or is there another logic to it? |
It recursively goes up, looking for either |
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
Versions
Repro steps
Observed behavior
Creates project but spits out the errors below. and then creates the old project structure.
Desired behavior
Should create new v.6 project structure and not complain about the empty folder being an old project.
Mention any other details that might be useful (optional)
I tried removing all globally installed yarn packages, as to mitigate if any of them where braking cli, but still same problem.
The ng new command was run from a totally empty newly created folder, so it can't be anything to do with that.
The text was updated successfully, but these errors were encountered: