-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
yarn start / webpack-cli fails #3189
Labels
Comments
edemaine
added a commit
that referenced
this issue
Aug 26, 2021
edemaine
added a commit
that referenced
this issue
Aug 26, 2021
ylemkimon
added a commit
that referenced
this issue
Aug 27, 2021
* chore(deps): update webpack, webpack-cli, webpack-dev-server Fixes #3189 * injectClient -> client * Switch WebpackDevServer constructor order * Switch from listen to start * Fix missing argument to catch * chore: dedupe lockfile * chore: update to Yarn 3.0.1 * ci: run yarn install on semantic release * ci: use setup-node cache * chore: update lockfile Co-authored-by: Ylemkimon <y@ylem.kim>
🎉 This issue has been resolved in version 0.13.14 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I'm getting the following error message when trying to
yarn start
. I don't seem to be able to figure out where there's arunning
property anywhere. Any ideas for fixing? Updating webpack (#3182) didn't help.I've reproduced the error on Windows and Linux, and using Yarn or NPM/
npx
. On the other hand,yarn build
works fine, so it's specific to the dev server.The text was updated successfully, but these errors were encountered: