Project extension with invalid name found in Angular with NX
Asked Answered
R

5

9

I am using Angular with nx and when I try to nx serve todos I get this error:

Project extension with invalid name found

And my project name is: todos.

I followed this https://nx.dev/angular-tutorial/01-create-application to create todos app with Angular 14.0.5 and I get the above error.

Does someone have any idea regarding this error?

Rase answered 16/7, 2022 at 12:4 Comment(2)
If you are using vscode, you can try out the nx dashboard extension. There is a commands section where you can choose to serve whichever app you want in the workspace.Callender
What is the effective name of your angular app ? Todos or myapp ?Indices
R
10

There is a git issue (see this) regarding to this problem. It's something that started to appear in Angular CLI v14.0.6.

Based on the git issue they are currently working on that to solve the problem but the most important thing is that: it doesn't really cause any issues apart from the noisy logs.

Rase answered 24/7, 2022 at 4:0 Comment(0)
F
1

I was facing the same issue with angular nx and I looked for solution and found a git issue describing the same problem and there it was written that "When starting the Angular app with nx run portal:serve:development the project compiles successfully, though there is some noisy logging. This is a known issue with Nx with the newest version of Angular. It is said to be harmless.

nrwl/nx#11138

As the known issue is harmless I think there is no need to worry about this issue.

I am attaching the git page link below: https://github.com/ZenSoftware/zen/issues/21

Fatma answered 17/7, 2022 at 12:40 Comment(0)
M
1

When I have ran this command npm run affected:test --code-coverage I got below warning :

Project 'user-journey' contains extension with invalid name (tags).

For fixing this warning, I have removed below line from nx.json / angular.json

"defaultProject": "web-shell",

Key defaultProject has been deprecated.

Please refer this link : https://github.com/angular/angular-cli/issues/11111

Moon answered 5/10, 2023 at 11:26 Comment(0)
A
0

I got this too. The problem in my case was that I positioned a property in the project.json on a wrong position. I had the lint target outside the targets on the root level. When positioning it correctly inside the targets object then there was no message anymore.

Articulation answered 24/5, 2024 at 14:43 Comment(0)
B
0

Got this error when my project configuration was off. Make sure all the commands (build,server,test) are within "target" object in project.json/ angular.json.

Bureau answered 27/6, 2024 at 14:5 Comment(0)

© 2022 - 2025 — McMap. All rights reserved.