-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Missing some required dependencies in very simple setup #720
Comments
Ok, I found what caused the issue. It was webpack configuration.
Missing .js is critical
|
Thanks megaboich. Exactly what I needed |
I'm experiencing this bug as well. This is my webpack.config.js file:
|
I had the same issue and I managed to resolve it, by reading the installation steps until the end :) and installing globally the mentioned packages from the terminal. Also a npm run clean was needed followed by npm install and then finally the npm start. |
Another potential cause of this problem is when the modules option does not contain the project's 'node_modules' folder. resolve: { if this piece of code "path.join(__dirname, 'node_modules')" is missing from the "modules" array or the path is incorrect you will get the same error. Please do not install the above mentioned packages (the ones listed in the terminal output) globally. Installing packages globally is almost never the solution to any problem. Global packages should almost always be avoided. The only global packages which are appropriate are packages used to initially create a project/package (ex: Yeoman, NPM, Bower), otherwise the package should be installed within the project/package, and referenced locally from "./node_modules/.bin". This is always better as you ensure other developers will not have conflicts between versions of global packages. Also, when the package's dependencies are installed with 'npm i', there is no need to do additional installation steps with global packages. Finally, many new Node.js developers on Mac/Linux run into issues with file system permissions and global packages. We do not want them using sudo to run code downloaded from the Internet. |
ERROR in multi (webpack)-dev-server/client?http://localhost:8080 webpack/hot/dev-server ./index.js help me |
Kinda sucks you have to resolve js extensions when your app contains no Javascript 🤷♂️ |
I had the same issue, just a little typo was giving me headaches. I wrote 'js' instead of '.js' Wrong Correct |
I am creating a typescript-webpack-react setup. Can someone explain to me why I need to manually resolve |
I got the same issue when using a symlink for |
@aamirkhan-91 webpack-dev-server injects some stuff into your site to implement the auto-reloading. This is in .js files. |
Hi, I used "npm install --save-dev babel-loader" and it worked for me. Give a try. |
Literally same issue! Thanks |
Thank you @athergeek ! |
Without this `webpack serve` fails. ref webpack/webpack-dev-server#720 (support ticket)
Had the same issue. Just realized I had the extensions listed as |
help me pls |
I have created very simple project as to show very simple setup of typescript, webpack and webpack-dev-server.
But unfortunately it doesn't work with minimal dependencies configured.
What is the current behavior?
I have errors when executing webpack-dev-server
If the current behavior is a bug, please provide the steps to reproduce.
Repository:
https://github.com/megaboich/sample-app-step1
What is the expected behavior?
Just work without errors
Please mention your webpack and Operating System version.
Windows 10
The text was updated successfully, but these errors were encountered: