We encountered an error message stating: "Schema validation failed with the following errors: Data path "" should NOT have additional properties(project)" , error occurs when there are extra or unexpected properties in the data being validated against a schema. In this case, it seems that the validation process is failing due to additional properties associated with the "project" data.

we need to ensure that the data being validated adheres strictly to the schema requirements. We should review the schema definition and compare it with the data being validated to identify any inconsistencies or extra properties.

Additionally, it's essential to ensure that the schema validation process is correctly configured and that it accurately reflects the expected structure of the data.

Once we've identified the extra properties causing the validation failure, we can either remove them from the data or update the schema definition to accommodate them if they are necessary for our application's requirements.


We encountered an issue while updating Ionic to the newest version, where we had to remove "es5BrowserSupport": true from angular.json in our Angular application.

It seems that having "es5BrowserSupport": true was causing problems, specifically with npm start not working as expected.

After removing "es5BrowserSupport": true from angular.json, npm start started working again without any issues.

may be compatibility issues between the es5BrowserSupport configuration and the latest version of angular. By removing this configuration, we were able to resolve the problem and continue development smoothly.


To resolve this issue, we first tried removing the "extractCss": true entry from the angular.json file. However, if this didn't work, then follow below of steps as outlined below:

  1. npm update: First, we ran the npm update command to ensure that all our npm packages were up to date.
  2. ng update: Next, we ran the ng update command to update Angular itself and any Angular-related packages.
  3. npm update --all --force: Finally, if there were still mismatching packages, we ran npm update --all --force to forcefully update all packages to resolve any conflicts.

it ensure that our Angular application and its dependencies are up to date and in sync, to resolving any compatibility issues that may arise due to outdated or mismatched packages.


We encountered an issue in our Angular project and found a solution that worked for us,we uninstalled the @angular-devkit/build-angular package using the npm uninstall command:

            npm uninstall @angular-devkit/build-angular

After uninstalling, we installed a specific version of the @angular-devkit/build-angular package using the npm install command:

            npm install @angular-devkit/[email protected]

This trick successfully resolved the issue we were facing in our Angular project.It's important to note that this solution may not be applicable to every situation, and the specific version of the package may vary depending on the project's and compatibility with other dependencies.