Errors: Data path ".builders['app-shell']" should have required property 'class'

data path "" should not have additional properties(es5browsersupport).
@angular-devkit/build-angular
schema validation failed with the following errors:
schema validation failed with the following errors data path .builders 'app-shell'
downgrade angular-devkit/build-angular
could not find the implementation for builder @angular-devkit/build-angular:dev-server
update @angular cli
angular devkit build angular 0.803 21 requires a peer of typescript 3.1 3.6 but none is installed

I am getting this error while running my application. Here are the details of my application.

Angular CLI: 7.3.3 
Node: 10.15.1 
Angular: 7.2.7 
@angular-devkit/architect -0.13.3 
@angular-devkit/build-angular- 0.800.1 
@angular-devkit/build-optimizer - 0.800.1 
@angular-devkit/build-webpack - 0.800.1 
@angular-devkit/core -7.3.3 
@angular-devkit/schematics -7.3.3 
@angular/cli -7.3.3 
@ngtools/webpack -8.0.1 
@schematics/angular -7.3.3 
@schematics/update 0.13.3 
rxjs 6.3.3 
typescript 3.2.4 
webpack 4.30.0

I have already tried cache clean.

In your package.json change the devkit builder.

"@angular-devkit/build-angular": "^0.800.1",

to

"@angular-devkit/build-angular": "^0.10.0",

it works for me. good luck.

Schema validation failed with the following errors: Data path , Try to update the package.json file so that "@angular-devkit/build-angular": "^​0.800.1" reads "@angular-devkit/build-angular": "^0.12.4". Errors typically fall into one the following categories: Data conversion errors, which occur if a conversion results in loss of significant digits, the loss of insignificant digits, and the truncation of strings. Data conversion errors also occur if the requested conversion is not supported.

Following worked for me

npm uninstall @angular-devkit/build-angular
npm install @angular-devkit/build-angular@0.13.0

npm start throw Data path ".builders['app-shell']" should have , Error: Schema validation failed with the following errors: Data path ".builders['app​-shell']" should have required property 'class'. Node, npm: `v10. Schema validation failed with the following errors: [ng] Data path "" should NOT have additional properties(es5BrowserSupport). [ERROR] ng has unexpectedly closed (exit code 1).

Everyone here is focusing on downgrading @angular-devkit/build-angular to @angular 7.x versions for compatibility, but what they should be doing is to upgrade @angular/cli to angular 8 versions.

The problem is that the system cli is still stuck at an old version and isn't automatically updated by ng update (because it is outside the angular controlled project), so it is being left at an incompatible version when trying to access the angular libraries.

Downgrading @angular-devkit/build-angular just causes more incompatibilities.

npm i --global @angular/cli@latest

will fix the problem without breaking things elsewhere.

Data path ".builders['app-shell']" should have required property , Data path ".builders['app-shell']" should have required property 'class'. Error: Schema validation failed with the following errors: Data path  SSIS error outputs are a secondary path through which the data flow can send rows that do not conform to data type, length, or transformation standards defined by the ETL developer. That’s a lengthy way to say that it’s where you can send your junk data.

Everyone is focusing on downgrading @angular-devkit/build-angular version to X, or upgrading @angular/cli version to Y or latest.

However, Please do not blindly suggest an X or Y or latest as answers. (Though usually, downgrading devkit should be better because upgrading CLI is a breaking change)

The correct version to choose, always depends on your Angular (angular-cli) version.

Angular CLI v8.3.19 -> 0.803.19
Angular CLI v8.3.17 -> 0.803.17
Angular CLI v7.3.8 -> 0.13.8
Angular CLI v6-lts -> 0.8.9

For other specific versions, visit: https://github.com/angular/angular-cli/tags. Find your CLI version, and in some tags, they do mention the corresponding versions for @angular-devkit/** packages.

Note: If you want to upgrade your CLI version, you should first consider upgrading to latest of your major version, do not simply jump to the next major version.

Schema validation failed ".builders['app-shell']" should have , on “ionic serve” Schema validation failed with the following errors: Data path “.​builders['app-shell']” should have required property 'class'. [ERROR] ng has  So I'm given a data dump with the two colums, all the peeps in the company and the second column who they report to. When I ran the Path Function the system kept telling me there were a ton of errors. I figured out that some of the data had to be cleaned up (mispelling of names) so I did that and it solved about 90% of the issues.

Your @angular-devkit is incompatible with @angular/cli version, so just install older one like this for example:

npm install @angular-devkit/build-angular@0.13.8 @angular-devkit/build-ng-packagr@0.13.8

Data path "" should not have additional properties(es5browsersupport), If you have faced or are facing the below error while running your Schema validation failed with the following errors: Data path should NOT  Data error (cyclic redundancy check) In this error message, path\filename.pst correspond to the location and the file name of your Personal Folders (.pst) file--for example, C:\mypst.pst. You may not be able to view some of the downloaded messages.

Pro OpenSolaris: A New Open Source OS for Linux Developers and , surface errors, DMA and cache memory errors, data path errors, and even device driver bugs. This process also enables active “self-healing” of disk data. Check for Interface Errors SFR - Check ASA Interfaces FTD (non-SSP and FPR-2100) - Check for Interface Errors FTD (SSP) - Navigating the Data Path to Look for Interface Errors Data to Provide to Cisco Technical Assistance Center (TAC) Next Step: Troubleshoot the Firepower DAQ Layer Introduction

Diagnosing SAS Data Path Failures on Servers Using MegaRAID , Important Operating Note On Oracle x86 servers using MegaRAID disk controllers, Serial Attached SCSI (SAS) data path errors can occur. To triage and isolate  Error: Windows cannot access the specified device, path, or file. You may not have the appropriate permission to access the item

Data Path builder app-shell should have required property class , Schema validation failed with the following errors: Data path ".builders['app-shell']​" should have required property 'class'. Error: Schema  Error code: 0x80070035. The network path was no found. The exact reason why “ The network path was not found” Error Code 0x80070035 emerges is not clear, but it has been noticed that the NetBIOS [3] over TCP/IP service is not enabled on most of the affected machines. Luckily, our team is here to help you.

Comments
  • Here is the detail of my application. Angular CLI: 7.3.3 Node: 10.15.1 Angular: 7.2.7 @angular-devkit/architect -0.13.3 @angular-devkit/build-angular- 0.800.1 @angular-devkit/build-optimizer - 0.800.1 @angular-devkit/build-webpack - 0.800.1 @angular-devkit/core -7.3.3 @angular-devkit/schematics -7.3.3 @angular/cli -7.3.3 @ngtools/webpack -8.0.1 @schematics/angular -7.3.3 @schematics/update 0.13.3 rxjs 6.3.3 typescript 3.2.4 webpack 4.30.0
  • This issue is generally because of incompatible packages. Have you recently updated package.json?
  • Finally i found the solution. 1)Firstly eliminate all changes in package.json file by giving simple command git checkout package.json. 2)Then after make change in package.json in @angular-devkit/build-angular- ~0.800.1(Add tail instead of cap) 3)Then run command rm -rf node_modules/ 4)Then clean catch by giving command npm clean cache -f 5)And at last run command npm install. This works for me.
  • Above, npm clean cache -f is wrong, should be npm cache clean --force .
  • What I found is that I had set nvm to use the wrong version of node, needed to set that properly using nvm use 12.14.01 (in my case)
  • Tried this...But still not working.
  • Made it to @angular-devkit/build-angular": "0.13.4" and it worked.
  • Perfect. Worked with "0.13.4", and running npm build afterwards
  • the 0.13.4 worked for me, however make sure you remove the node_modules folder first, delete the package-lock.json and then run npm install. seems to fix everything.
  • This solution works but it's wrong, you should instead upgrade the angular and angular cli version. Check @ovangle answer below
  • this one worked for me :)