angular-cli: ng build/serve fails with "Error: No errors" message
OS?
Ubuntu 16.10
Versions.
__ _ _ __ __ _ _ _ | | __ _ _ __ ___ | |(_)
/ _` || '_ \ / _` || | | || | / _` || '__|_____ / __|| || |
| (_| || | | || (_| || |_| || || (_| || | |_____|| (__ | || |
\__,_||_| |_| \__, | \__,_||_| \__,_||_| \___||_||_|
|___/
angular-cli: 1.0.0-beta.26
node: 7.4.0
os: linux x64
@angular/common: 2.4.5
@angular/compiler: 2.4.5
@angular/core: 2.4.5
@angular/forms: 2.4.5
@angular/http: 2.4.5
@angular/platform-browser: 2.4.5
@angular/platform-browser-dynamic: 2.4.5
@angular/router: 3.4.5
@angular/compiler-cli: 2.4.5
Repro steps.
New app created using =>
ng new PROJECT
The log given by the failure.
ng serve
No errors
Error: No errors
at validate (/home/carlos/empresa.com.br/PROJECT/node_modules/extract-text-webpack-plugin/schema/validator.js:10:9)
at Function.ExtractTextPlugin.extract (/home/carlos/empresa.com.br/PROJECT/node_modules/extract-text-webpack-plugin/index.js:188:3)
at /home/carlos/empresa.com.br/PROJECT/node_modules/angular-cli/models/webpack-build-styles.js:79:83
at Array.map (native)
at Object.getWebpackStylesConfig (/home/carlos/empresa.com.br/PROJECT/node_modules/angular-cli/models/webpack-build-styles.js:76:43)
at new NgCliWebpackConfig (/home/carlos/empresa.com.br/PROJECT/node_modules/angular-cli/models/webpack-config.js:44:51)
at Class.run (/home/carlos/empresa.com.br/PROJECT/node_modules/angular-cli/tasks/serve-webpack.js:23:22)
at /home/carlos/empresa.com.br/PROJECT/node_modules/angular-cli/commands/serve.run.js:37:22
at process._tickCallback (internal/process/next_tick.js:103:7)
This is just a new ubuntu and a new node npm and angular-cli install
`carlos@carlos-Z97M-D3H:~/empresa.com.br/PROJECT(master○) » npm start 1 ↵
project@0.0.0 start /home/carlos/empresa.com.br/PROJECT ng serve
No errors
Error: No errors
at validate (/home/carlos/empresa.com.br/PROJECT/node_modules/extract-text-webpack-plugin/schema/validator.js:10:9)
at Function.ExtractTextPlugin.extract (/home/carlos/empresa.com.br/PROJECT/node_modules/extract-text-webpack-plugin/index.js:188:3)
at /home/carlos/empresa.com.br/PROJECT/node_modules/angular-cli/models/webpack-build-styles.js:79:83
at Array.map (native)
at Object.getWebpackStylesConfig (/home/carlos/empresa.com.br/PROJECT/node_modules/angular-cli/models/webpack-build-styles.js:76:43)
at new NgCliWebpackConfig (/home/carlos/empresa.com.br/PROJECT/node_modules/angular-cli/models/webpack-config.js:44:51)
at Class.run (/home/carlos/empresa.com.br/PROJECT/node_modules/angular-cli/tasks/serve-webpack.js:23:22)
at /home/carlos/empresa.com.br/PROJECT/node_modules/angular-cli/commands/serve.run.js:37:22
at process._tickCallback (internal/process/next_tick.js:103:7)
npm ERR! Linux 4.8.0-34-generic
npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "start"
npm ERR! node v7.4.0
npm ERR! npm v4.0.5
npm ERR! code ELIFECYCLE
npm ERR! project@0.0.0 start: `ng serve`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the project@0.0.0 start script 'ng serve'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the project package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! ng serve
npm ERR! You can get information on how to open an issue for this project with:
npm ERR! npm bugs project
npm ERR! Or if that isn't available, you can get their info via:
npm ERR! npm owner ls project
npm ERR! There is likely additional logging output above.
npm ERR! Please include the following file with any support request:
npm ERR! /home/carlos/empresa/PROJECT/npm-debug.log
`
About this issue
- Original URL
- State: closed
- Created 7 years ago
- Reactions: 7
- Comments: 44 (6 by maintainers)
I can confirm that the problem does not occur anymore after installing the plugin at version 2.0.0-rc.0 (npm install extract-text-webpack-plugin@2.0.0-rc.0 --save-dev)
Same issue here since half an hour or so:
This was driving me nuts… can we PLEASE pin versions and stop using bleeding edge chaos unless some library explicitly asks for it? (e.g. like java/maven is doing it since forever)?! 😡
This problem arises from a recent update in a external dependency and it’s not fixable without a CLI release right now.
The workaround by @drakenfly is the only option right now:
I’m going to leave this open since a lot of people are going to be searching for it. Will also change the title to something more obvious.
What version of
extract-text-webpack-plugin
are you running? I see that they released a new version just an hour ago:2.0.0-rc.1
which is also giving me the above error. I’ll try with the previous version.@duard
npm ls extract-text-webpack-plugin
in your project.Guys this is insane, use fucking yarn, and pin your shit!
npm install extract-text-webpack-plugin@2.0.0-rc.0 --save-dev
did not work for me.If I remove the
node_modules
folder and then re-installnpm install
, it installs2.0.0-rc.1
, even though it is saved inpackage.json
:any suggestion?
Thanks
@Drakenfly Thanks. That did the trick.
npm install extract-text-webpack-plugin@2.0.0-rc.0 --save-dev
@Lopierdis