Skip to content
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

Closed
edemaine opened this issue Aug 26, 2021 · 1 comment · Fixed by #3191
Closed

yarn start / webpack-cli fails #3189

edemaine opened this issue Aug 26, 2021 · 1 comment · Fixed by #3191

Comments

@edemaine
Copy link
Member

edemaine commented Aug 26, 2021

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 a running property anywhere. Any ideas for fixing? Updating webpack (#3182) didn't help.

[webpack-cli] Invalid configuration object. Object has been initialized using a
configuration object that does not match the API schema.
 - configuration has an unknown property 'running'. These properties are valid:
   object { bonjour?, client?, compress?, dev?, firewall?, headers?, historyApiFallback?, host?, hot?, http2?, https?, injectClient?, injectHot?, liveReload?, onAfterSetupMiddleware?, onBeforeSetupMiddleware?, onListening?, open?, openPage?, overlay?, port?, proxy?, public?, setupExitSignals?, static?, stdin?, transportMode?, useLocalIp? }

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.

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>
@KaTeX-bot
Copy link
Member

🎉 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
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants