I created a new project using Angular CLI 9.1.1 and VSCode is giving me the following warning in angular.json file:
Property AM is not allowed
AM is my project name
I want to resolve this warning, but don't know how.
-
3Even moderators closed the question, please add any further information you found Shruti, more people are on this issue.Josep Alacid– Josep Alacid2020-04-19 22:39:36 +00:00Commented Apr 19, 2020 at 22:39
-
2I'm seeing the same thing. If I change my project name to lower case, it appears to work. But my project name is an acronym, so upper case is correct. Is this a bug?DeborahK– DeborahK2020-04-28 15:11:57 +00:00Commented Apr 28, 2020 at 15:11
Add a comment
|
8 Answers
The schema is case sensitive. If you wish to fix:
Goto: ./node_modules/@angular/cli/lib/config/schema.json
At around line 27 you should find:
"projects": {
"type": "object",
"patternProperties": {
"^(?:@[a-z0-9-~][a-z0-9-._~]*\/)?[a-z0-9-~][a-z0-9-._~]*$": {
"$ref": "#/definitions/project"
}
},
Change the regex pattern to allow Uppercase project names:
"^(?:@[a-zA-Z0-9-~][a-zA-Z0-9-._~]*\/)?[a-zA-Z0-9-~][a-zA-Z0-9-._~]*$"
5 Comments
Fry Simpson
This solved the issue (after I closed and reopened VS Code). But, being the edited file under
node_modules, is it overwritten to the original each time I run npm install?
Yassir Khaldi
@FrySimpson To answer your question, running
npm install does not revert the modifications.Fry Simpson
@Yassir, thanks. In order to have modifications "remembered" I suppose i have to remember to keep the package-lock.json file if i manually delete node_modules in order to share my code with someone.
Grault
Note this requires a restart. I lost a bit of time for not thinking of that initially.
JerMah
How do you do this if the "node_modules" folder is normally not on git. Sure you could make an exception for this one file but...
The error was gone when change project name and all other occurrences for it in "angular.json" to lowercase letters. no need to create another project or any other stuff.
Comments
The packages installed for Angular 10 project have a change in project name structure.
The file named "schema.json" which come along the packages installed by Angular has a property name "projects" which has the schema structure defined for the project name.
It looks like this:
"projects": {
"type": "object",
"patternProperties": {
"^(?:@[a-z0-9-~][a-z0-9-._~]*\/)?[a-z0-9-~][a-z0-9-._~]*$": {
"$ref": "#/definitions/project"
}
}
It is configured for lower case project names. You simply have to change the regex so that your uppercase project names can be considered.
Change the code as below:
"projects": {
"type": "object",
"patternProperties": {
"^(?:@[a-zA-Z0-9-~][a-zA-Z0-9-._~]*\/)?[a-zA-Z0-9-~][a-zA-Z0-9-._~]*$": {
"$ref": "#/definitions/project"
}
}
The schema.json is located at below path:
./node_modules/@angular/cli/lib/config/schema.json
After the change in schema.json file, restart your Visual Code Editor.
Comments
It is working fine on stackblitz, sometimes VS code behaves strangely. Try closing VS code and opening again, that helps most of the times in these cases
working example https://stackblitz.com/edit/angular-dhtbbh
Comments
Checks if {} are in the correct position. In my case I did:
{ "configurations": { "production": { ... } }, **"stage": { ... }** }
The correct way was:
{ "configurations": { "production": { ... }, **"stage": { ... }** } }
Comments
There are 2 solutions which works for me 100% to overcome from the problem of "Property not allowed" in angular.json file.
Use the command in VS code cmd Ctrl+C choose option Y or
Restart the VS code after editing in angular.json file Hope it will helpful.
Comments
The error is resolved by creating another project but this time using the project name in lowercase letters.
1 Comment
ZeusT
This doesn't actually solve the issue, especially when you find the issue a long time after starting the project.