DeprecationWarning: 'onAfterSetupMiddleware' option is deprecated
See original GitHub issueI got a warning when npm start. Please help me solve the problem.
(node:1681) [DEP_WEBPACK_DEV_SERVER_ON_AFTER_SETUP_MIDDLEWARE] DeprecationWarning: ‘onAfterSetupMiddleware’ option is deprecated. Please use the ‘setupMiddlewares’ option.
(Use node --trace-deprecation ...
to show where the warning was created)
(node:1681) [DEP_WEBPACK_DEV_SERVER_ON_BEFORE_SETUP_MIDDLEWARE] DeprecationWarning: ‘onBeforeSetupMiddleware’ option is deprecated. Please use the ‘setupMiddlewares’ option.
Issue Analytics
- State:
- Created 2 years ago
- Reactions:121
- Comments:75
Top Results From Across the Web
Cant load a react app after starting server - Stack Overflow
This is a deprecation warning, meaning that you need to start using the newly suggested way of configuring your middleware.
Read more >'onAfterSetupMiddleware' option is deprecated | bobbyhadz
To resolve the warning, update your configuration to use setupMiddlewares instead. dep webpack dev server on after setup middleware deprecationwarning. shell.
Read more >React Install Windows Question : r/reactjs - Reddit
(node:10720) [DEP_WEBPACK_DEV_SERVER_ON_AFTER_SETUP_MIDDLEWARE] DeprecationWarning: 'onAfterSetupMiddleware' option is deprecated.
Read more >Create-react-app broken? - Codecademy Forums
... DeprecationWarning: 'onAfterSetupMiddleware' option is deprecated. ... (Use node --trace-deprecation ... to show where the warning was ...
Read more >onBeforeSetupMiddleware is Deprecated 문제 해결방법 - velog
(node:2584) DEP_WEBPACK_DEV_SERVER_ON_AFTER_SETUP_MIDDLEWARE DeprecationWarning: 'onAfterSetupMiddleware' option is deprecated.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Would you all stop spamming? What is the purpose of you writing that you have the same issue? Will that fix the issue quicker? Subscribe to the issue and shut up
I have the same issue