You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There might be a problem with the project dependency tree.
It is likely not a bug in Create React App, but something you need to fix locally.
The react-scripts package provided by Create React App requires a dependency:
"babel-jest": "^24.9.0"
Don't try to install it manually: your package manager does it automatically.
However, a different version of babel-jest was detected higher up in the tree:
\node_modules\babel-jest (version: 20.0.3)
Manually installing incompatible versions is known to cause hard-to-debug issues.
If you would prefer to ignore this check, add SKIP_PREFLIGHT_CHECK=true to an .env file in your project.
That will permanently disable this message but you might encounter other issues.
To fix the dependency tree, try following the steps below in the exact order:
1. Delete package-lock.json (not package.json!) and/or yarn.lock in your project folder.
2. Delete node_modules in your project folder.
3. Remove "babel-jest" from dependencies and/or devDependencies in the package.json file in your project folder.
4. Run npm install or yarn, depending on the package manager you use.
In most cases, this should be enough to fix the problem.
If this has not helped, there are a few other things you can try:
5. If you used npm, install yarn (http://yarnpkg.com/) and repeat the above steps with it instead.
This may help because npm has known issues with package hoisting which may get resolved in future versions.
6. Check if D:\_git_\os-viewer-ra\node_modules\babel-jest is outside your project directory.
For example, you might have accidentally installed something in your home folder.
7. Try running npm ls babel-jest in your project folder.
This will tell you which other package (apart from the expected react-scripts) installed babel-jest.
If nothing else helps, add SKIP_PREFLIGHT_CHECK=true to an .env file in your project.
That would permanently disable this preflight check in case you want to proceed anyway.
P.S. We know this message is long but please read the steps above :We hope you find them helpful!
All jests internal dependencies are specified with a ^ so for a fresh install without a lock file yarn will install jest-cli@24.8.0 for jest@24.7.1. If you put a resolution on jest-cli@24.7.1, it will still install jest-config@24.8.0.
You can put a resolution for babel-jest@24.7.1 which do work but generates warnings when running yarn as all 2.8.0 packages has the range ^2.8.0.
This issue should be solved when #7007 is released. But as of now, create-react-app tries to verify something that neither yarn nor jest is guaranteeing.
Thanks so much for the assistance, the solution is actually a lot simpler than what I thought I was meant to be trying. It's just forcing all packages to use the same version, simple. And much more simple than the examples I could see. All I had to do was:
1. yarn remove react-aad-msal
2. add
"resolutions": {
"jest": "23.6.0",
"babel-jest": "23.6.0"
},
to package.json
3. yarn install
4. yarn add react-aad-msal
and that's it!
検証用