Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

webpack-dev-server Windows 10 consistent error

See original GitHub issue

I’m not able to run a webpack-dev-server on the same repo my colleagues are using seamlessly.

I’m the only one using Windows 10. Others use either mac or Ubuntu.

My conf an the error I’m getting is:

PS D:\GitHub\frontagregador> npm -v
3.10.9
PS D:\GitHub\frontagregador> node -v
v7.1.0
PS D:\GitHub\frontagregador> npm run dev

> test-front-end-agregador@1.0.0 dev D:\GitHub\frontagregador
> webpack-dev-server --content-base src --inline --hot

 http://localhost:8080/
webpack result is served from /
content is served from D:\GitHub\frontagregador\src
404s will fallback to /index.html

npm ERR! Windows_NT 10.0.14393
npm ERR! argv "D:\\nodejs\\node.exe" "D:\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "run" "dev"
npm ERR! node v7.1.0
npm ERR! npm  v3.10.9
npm ERR! code ELIFECYCLE
npm ERR! test-front-end-agregador@1.0.0 dev: `webpack-dev-server --content-base src --inline --hot`
npm ERR! Exit status 3221226505
npm ERR!
npm ERR! Failed at the test-front-end-agregador@1.0.0 dev script 'webpack-dev-server --content-base src --inline --hot'.
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 test-front-end-agregador package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     webpack-dev-server --content-base src --inline --hot
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs test-front-end-agregador
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls test-front-end-agregador
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     D:\GitHub\frontagregador\npm-debug.log

Issue Analytics

State:
Created 7 years ago
Comments:6 (3 by maintainers)

Top GitHub Comments

1reaction

SpaceK33zcommented, Nov 23, 2016

Okay, I’m going to close this for now since we have many other issues with the watch functionality and node v7 anyway.

0reactions

juanmagomezmayoralcommented, Nov 23, 2016

ok, sorry, didn’t undertand you. I’ve run it on v6 node and it works (lots of non-related errors like ERROR in ./src/layouts/footer/styles.scss Module not found: Error: Cannot resolve ‘file’ or ‘directory’ ./…/…/…/node_modules/css-loader/index.js in D:\GitHub\frontagregador/src\layouts\footer @ ./src/layouts/footer/styles.scss 4:14-199 but the webserver is up)

It seems to be an issue related to node v7 then…

thanks J

Top Results From Across the Web

"npm start" error with webpack-dev-server - node.js

Try running npm install . Looks like the module isn't installed. – lux. Jan 10, 2017 at 21:06.

How I solved and debugged my Webpack issue through ...

When webpack bundles your source code, it can become difficult to track down errors and warnings to their original location.

Error: No hook for resolver normal in object ResolverFactory

Hello. I am encountering this reoccurring error message when attempting to run and compile the template map via the "ArcGIS JS API CLI ......

MiniCssExtractPlugin

This plugin extracts CSS into separate files. It creates a CSS file per JS file which contains CSS. It supports On-Demand-Loading of CSS...

options has an unknown property 'before'. these ...

Seems overlay doesn't work with latest webpack-dev-server v4.1.0. Error: ... Operating System: windows 10; Node Version: 14.5.0; NPM Version: 6.14.8 ...