-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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
Creating an angular workspace with appName='app' breaks angular.json #1844
Comments
Thanks for raising this issue, @IgorAufricht! I think you and I must have found this problem at the same time. This seems to occur with any application with a name that is contained within the word "application". The same bug will also cause problems for anyone trying to add a library with a name like "lib". Thanks for tracking down the relevant bit of code! |
Currently when trying to create an app named 'app' or a lib named 'lib', the schematics inject the 'projectType' as 'apps/application' or lib as 'libs/library', breaking the Angular build. fix nrwl#1844
Currently when trying to create an app named 'app' or a lib named 'lib', the schematics inject the 'projectType' as 'apps/application' or lib as 'libs/library', breaking the Angular build. fix nrwl#1844
Currently when trying to create an app named 'app' or a lib named 'lib', the schematics inject the 'projectType' as 'apps/application' or lib as 'libs/library', breaking the Angular build. fix #1844
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. |
Expected Behavior
I should be able to create a workspace with an angular app named "app".
Current Behavior
The workspace gets created, but the
angular.json
file gets incorrectly modified.Steps to Reproduce
npx create-nx-workspace@8.5.0 nxrepo --preset=angular --cli=angular
ng build
This will fail with:
This is because the
angular.json
file now contains the following:Other
For what it's worth, I tracked it to the replaceAppNameWithPath function.
The text was updated successfully, but these errors were encountered: