Angular CLI: Schema validation failed with the following errors: Data path "" must NOT have additional properties(xyz)
angular.json (or an option you passed to a builder) contains a property the schema does not allow — a typo, an option removed in a newer CLI, or the wrong builder.
Schema validation failed with the following errorsData path "" must NOT have additional propertiesData path "/budgets/0" must have required propertyUnknown option in angular.json Meaning
The message names the data path and the offending property. After upgrades, options like browserTarget, buildOptimizer, vendorChunk, aot or es5BrowserSupport were renamed or removed. Delete or rename the property, or run ng update to apply the migrations.
Common causes
- Option removed or renamed in the new Angular version (
browserTarget→buildTarget) - Typo in an option name
- Option belongs to another builder (for example esbuild vs webpack)
- Hand-edited angular.json copied from an older project
- Wrong type (string instead of boolean/array)
⚡ Quick fix
- Read the named property in the error and remove or rename it
- Run
ng update @angular/clito migrate configuration - Check the builder docs for valid options
Detailed fix by platform
Angular CLI
- Compare with a freshly generated project:
ng new tmp-appand diff its angular.json - Re-run migrations:
ng update @angular/cli @angular/core
Code examples
Renamed option
"serve": {
"builder": "@angular-devkit/build-angular:dev-server",
"configurations": {
"development": { "buildTarget": "my-app:build:development" } // was "browserTarget" before Angular 17
}
}How to diagnose
- Path — Which Data path and property are named?
- Version — Which CLI version?
- Builder — Which builder uses this option?
🔧 Still not fixed?
Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:
Similar errors
- Can't find stylesheet to import Angular (Sass): Error: Can't find stylesheet to import. @import 'variables';
- Cannot GET /route on refresh Angular (production): Cannot GET /dashboard — 404 when refreshing or opening a deep link
- Component is not resolved: templateUrl Angular tests: Component 'X' is not resolved: templateUrl: ./x.component.html — Did you run and wait for 'resolveComponentResources()'?
Most viewed in Angular
Other ways to find it
Where this error sits
Origin: On your device. Errors that are often confused with or caused by this one (click to open):
🧠 Still stuck? Analyze your error
Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.
💬 What worked for others
No tips yet — did something else fix this for you?
Share what worked for you
Tips are checked by an editor before they appear. Links are removed.
Report a correction or suggest an improvement
Last updated 15 Oct 2026