Angular-cli: Error: Can't resolve 'webpack-dev-server/client?http://0.0.0.0:0' [1.7]

Created on 16 Feb 2018  Â·  7Comments  Â·  Source: angular/angular-cli

Versions

Angular CLI: 1.7.0
Node: 8.9.4
OS: linux x64
Angular: 5.2.5
... animations, common, compiler, compiler-cli, core, forms
... http, language-service, platform-browser
... platform-browser-dynamic, router

@angular/cdk: 5.2.1
@angular/cli: 1.7.0
@angular/flex-layout: 2.0.0-beta.12
@angular/material: 5.2.1
@angular-devkit/build-optimizer: 0.3.1
@angular-devkit/core: 0.3.1
@angular-devkit/schematics: 0.3.1
@ngtools/json-schema: 1.2.0
@schematics/angular: 0.3.1
@schematics/package-update: 0.3.1
typescript: 2.4.2
webpack-node-externals: 1.6.0
webpack: 3.10.0

Repro steps

Havn't got a repro sorry :/

Observed behavior

ERROR in multi webpack-dev-server/client?http://0.0.0.0:0 ./path/to/main.ts
Module not found: Error: Can't resolve 'webpack-dev-server/client?http://0.0.0.0:0' in '/home/f.wiles/Documents/projectname'

Mention any other details that might be useful (optional)

This is a medium sized project using yarn as the package manager

$ npm ls webpack-dev-server
[email protected] /home/f.wiles/Documents/project-name
└─┬ @angular/[email protected]
     └── [email protected]

I've also tried deleting both yarn.lock and node_modules but the same error is observed

low regression bufix

Most helpful comment

Just upgraded everything in an app that worked on previous versions, and got the same error. Easy to repro, just run ng new test-app and ng serve. Work-around: install @angular/[email protected] and hope 1.7.1 has better luck. :)

All 7 comments

Just upgraded everything in an app that worked on previous versions, and got the same error. Easy to repro, just run ng new test-app and ng serve. Work-around: install @angular/[email protected] and hope 1.7.1 has better luck. :)

Exactly the same issue however I am using npm 5 (not yarn per the original report). Downgrading from 1.7.0 to @angular/[email protected] worked for me. I'm not sure what other information beyond the original report will be relevant but happy to provide more if prompted.

I had the same issue and it got resolved after i manually re-run npm install @angular/[email protected].

@alrazex 's solution worked for me as well:

manually re-run npm install @angular/[email protected]

I had the same issue after upgrading to CLI 1.7.0
Did as @alrazex did with re-run npm install @angular/[email protected]
And that works for me.
thanks

@hansl this issue is reproducible with @angular/[email protected] in IE
Should this really be closed ?

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_This action has been performed automatically by a bot._

Was this page helpful?
0 / 5 - 0 ratings

Related issues

jmurphzyo picture jmurphzyo  Â·  3Comments

gotschmarcel picture gotschmarcel  Â·  3Comments

daBishMan picture daBishMan  Â·  3Comments

NCC1701M picture NCC1701M  Â·  3Comments

hareeshav picture hareeshav  Â·  3Comments