# Angular CLI: Schema validation failed with the following errors: Data path "" must NOT have additional properties(xyz)

**Code:** `Schema validation failed with the following errors` · **Category:** Angular · **Seen on:** Angular, Angular CLI

`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.

## 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

1. Read the named property in the error and remove or rename it
2. Run `ng update @angular/cli` to migrate configuration
3. Check the builder docs for valid options

## Detailed fix by platform

### Angular CLI

1. Compare with a freshly generated project: `ng new tmp-app` and diff its angular.json
2. Re-run migrations: `ng update @angular/cli @angular/core`

## Code examples

### Renamed option

```json
"serve": {
  "builder": "@angular-devkit/build-angular:dev-server",
  "configurations": {
    "development": { "buildTarget": "my-app:build:development" }   // was "browserTarget" before Angular 17
  }
}
```

## How to diagnose

1. **Path** — Which Data path and property are named?
2. **Version** — Which CLI version?
3. **Builder** — Which builder uses this option?

---
Source: [WhatIsMyError](https://whatismyerror.com/errors/angular/angular-json-schema-validation-failed)