fix(webpackDevServer): fix deprecation warning

[zhaomengfan]

update webpack-dev-server + fix deprecation warning (#11860)

[facebook-github-bot]

Hi @zhaomengfan!

Thank you for your pull request and welcome to our community.

Action Required

In order to merge any pull request (code, docs, etc.), we require contributors to sign our Contributor License Agreement, and we don't seem to have one on file for you.

Process

In order for us to review and merge your suggested changes, please sign at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need to sign the corporate CLA.

Once the CLA is signed, our tooling will perform checks and validations. Afterwards, the pull request will be tagged with CLA signed. The tagging process may take up to 1 hour after signing. Please give it that time before contacting us about it.

If you have received this in error or have any questions, please contact us at [email protected]. Thanks!

[facebook-github-bot]

Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Meta Open Source project. Thanks!

[yann-combarnous]

@raix , could this be added to 5.0.1, by any chance? It would reduce CRA verbosity on startup.

[wcedmisten-reify]

@zhaomengfan Recommend upgrading webpack-dev-server to 4.7.3 to include a recent security patch

[ramdaniAli]

Will this deprecation be fixed in a future release?

[brookjordan]

Would love to see this implemented to reduce developer confusion.

[Meligy]

Is there a workaround until this PR is merged?

Or else, is there anything that can help with it? I assume external user review / approval will not count.

[icey-franken]

bump

[sbaggott]

This is actually breaking our app locally. With react-scripts 5.0.1, when we run npm start, despite it just being a warning it stops the dev server with the deprecation warning. Is there any way to fix this while we wait for 5.0.2?

[pat-ryb]

It work. The warning it's gone.

It really does the trick.

[dirkesquire]

At the moment my app won't start up using [email protected]. I see a lot of failing tests in the requested Review? How do we get this reviewed/fixed/merged in?

[Meligy]

Is this planned for 5.0.2?

[ithrforu]

bump.

[akhileshgoud2504]

The issue got fixed with the changes in the below link https://github.com/facebook/create-react-app/pull/11862/files/2dff88610f9ad215349424d1769b88e0a0d2fa1d Thank you..!

[micktdj]

Is this still planned for 5.0.2 patch ?

[MikeMcC399]

• Is there anybody sponsoring or working on this PR? It fails 7 out of 9 tests.

• The issue https://github.com/facebook/create-react-app/issues/11860 is still open.

[BalaM314]

I can't see the failure reason anymore as Azure dropped the run results, does anyone know why the tests are failing?

[MikeMcC399]

@BalaM314

The whole PR is now stale, so either the original submitter @zhaomengfan would need to rebase or somebody else would need to be active. Considering that the last commit to the master branch was in September 2022 it seems that the repository is no longer being actively maintained.

• Edit: See also issue https://github.com/facebook/create-react-app/issues/13393

[Abel13]

how can I use this branch on my code?

[morremeyer]

@nathanwiles Your school project's recommendation is outdated. Take a look at e.g. vite. create-react-app is unmaintained.

[misraelson]

IMO CRA should be maintained. Lots and lots of production apps still use CRA. This isn't breaking my app, but I do see a warning pop up for a split second before the local server runs. It's wild that this PR is still open, how can we merge it in? @zhaomengfan please merge this

[jaypatel22222]

Hi Guys, Will this be fixed in any new releases?

[MikeMcC399]

@jaypatel22222

Hi Guys, Will this be fixed in any new releases?

• You should probably read https://github.com/facebook/create-react-app/issues/13393 for background information. It sounds highly unlikely that there will be any new release.