Skip to content

React-dev-utils/webpackHotDevClient breaks when updating #8851

Closed
@darthzeran

Description

@darthzeran

#8254

Describe the bug

I updated my package.json like so:

"react": "^16.8.0", =>"^16.13.1",
"react-dom": "^16.8.0", => "^16.13.1",
"react-scripts": "2.1.8", =>"^3.4.1",

and then i ran yarn; yarn dev
and then I got the following error

Error: [BABEL] C:\project\node_modules\react-dev-utils\webpackHotDevClient.js: Cannot find module 'js-levenshtein' (While processing: "C:\\project\\node_modules\\babel-preset-react-app\\dependencies.js$0")   

so i yarn added the levenshtein modeule

then got the following error

Error: [BABEL] C:\project\node_modules\react-dev-utils\webpackHotDevClient.js: Invalid Option: corejs is not a valid top-level option.                                                                            Maybe you meant to use 'targets'? (While processing: "C:\\project\\node_modules\\babel-preset-react-app\\dependencies.js$0") 

I then did about 10 different github/stack overflow suggestions to remedy this error, but to no avail,
including mass yarn upgrades, installing individual packages, etc.

Did you try recovering your dependencies?

yes
yarn version 1.17.3

Which terms did you search for in User Guide?

hot dev, wepbackhotdevclient, corejs, invalid option

Environment

using Electron

Environment Info: current version of create-react-app: 3.4.1
running from C:\blank\AppData\Roaming\npm-cache_npx\18920\node_modules\create-react-app
System: OS: Windows 10 10.0.18362
CPU: (8) x64 Intel(R) Core(TM) i7-8565U CPU @ 1.80GHz
Binaries:
Node: 10.15.3 - C:\Program Files\nodejs\node.EXE
Yarn: 1.17.3 - C:\Program Files (x86)\Yarn\bin\yarn.CMD
npm: 6.4.1 - C:\Program Files\nodejs\npm.CMD
Browsers:
Edge: 44.18362.449.0
Internet Explorer: 11.0.18362.1
npmPackages:
react: ^16.13.1 => 16.13.1
react-dom: ^16.13.1 => 16.13.1
react-scripts: ^3.4.1 => 3.4.1
npmGlobalPackages:
create-react-app: Not Found

Steps to reproduce

Have an electron react project with a package .json similar to the intro,
change it to match the new versions added to package json
voila

Expected behavior

TO not crash when yarn dev'ing

Actual behavior

Errors shown above

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions