Data path "" should NOT have additional properties(customWebpackConfig).
See original GitHub issueAfter installation ng serve -o reflects
Schema validation failed with the following errors:
Data path "" should NOT have additional properties(customWebpackConfig).
Issue Analytics
- State:
- Created 3 years ago
- Comments:9
Top Results From Across the Web
Schema validation fails: Data path "" should NOT have ...
ng serve Schema validation failed with the following errors: Data path "" should NOT have additional properties(customWebpackConfig).`.
Read more >angular - Data path '''' should NOT have additional properties ...
In my case a simple npm i which re/installs all dependencies, solved the issue. – Semo. Aug 19, 2021 at 11:52.
Read more >Hi Jacob, thanks for sharing ! I could make it work for Angular ...
I got an error `Schema validation failed with the following errors: Data path "" should NOT have additional properties(customWebpackConfig).
Read more >Data path "" should NOT have additional properties ...
Data path "" should NOT have additional properties(customWebpackConfig). ... Then get error: Schema validation failed with the following errors:
Read more >angular/angular-cli - Gitter
hi guys need some help upgraded to angular v6 . while using angular 2 in tslint ... errors: Data path "" should NOT...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@AlexanderOpran I got confused a bit with a PR 😃 Although PR that I created not relevant for you anymore. I’ll put it here as an example: https://github.com/AlexanderOpran/angular-tailwind-debug/pull/1
Error “Data path “” should NOT have additional properties(customWebpackConfig).” was due to
customWebpackConfig
inserve
config: https://github.com/AlexanderOpran/angular-tailwind-debug/pull/1/files#diff-2d2675bb4687601a5c7ccf707455132f90f3516a33716185687e5c41df59ac7dL176-L180and using
@angular-builders/custom-webpack@10
instead ofv11
https://github.com/AlexanderOpran/angular-tailwind-debug/pull/1/files#diff-7ae45ad102eab3b6d7e7896acd08c427a9b25b346470d7bc6507b6481575d519L27-L28webpack.config.js
was outdated.@nartc I reproduced this issue while working on PR. removing customWebpackConfig from serve solved it for me. So I think the issue can be closed (maybe we should make some FAQ on the readme page?)
@vltansky I see. You have any action item to close this issue?