Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

error occurred in angular-cli8.3.5 #133

Closed
gtjyj opened this issue Sep 24, 2019 · 7 comments
Closed

error occurred in angular-cli8.3.5 #133

gtjyj opened this issue Sep 24, 2019 · 7 comments

Comments

@gtjyj
Copy link

gtjyj commented Sep 24, 2019

in angular-cli version 8.3.5, when i use option "ng build --prod", one error occured:

Schema validation failed with the following errors:
Data path ".budgets[1].type" should be equal to one of the allowed values.

when i change the angular.json from "builder": "ngx-build-plus:build" to "builder": "@angular-devkit/build-angular:browser" , all will be sucess.

after the error, i rollback the cli version from 8.3.5 to 8.0.2,all working expected

@gtjyj gtjyj changed the title erroroccurred in angular-cli8.3.5 error occurred in angular-cli8.3.5 Sep 24, 2019
@ringodotnl
Copy link

FYI no erorr using cli version 8.3.0.

@moefinley
Copy link

moefinley commented Oct 1, 2019

I get the error on version 8.3.5, 8.3.0 and 8.0.2

angular.json.txt

@moefinley
Copy link

@observant2
Copy link

To expand @moefinley's answer.
In angular.json remove:

{
"type": "anyComponentStyle",
"maximumWarning": "6kb",
"maximumError": "10kb"
}

@artu-ole
Copy link

This is not a resolved issue unless schema.json actually gets updated to reflect changes in angular_devkit/build_angular/src/browser/schema.json

@laurencefass
Copy link

removing

{ "type": "anyComponentStyle", "maximumWarning": "6kb", "maximumError": "10kb" }

allows a universal build to proceed. can anyone explain the issue in greater detail?

thanks

Maistho added a commit to Maistho/ngx-build-plus that referenced this issue Jan 21, 2020
@Maistho
Copy link

Maistho commented Jan 21, 2020

I opened #158 which should fix this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

8 participants