-
-
Notifications
You must be signed in to change notification settings - Fork 8.5k
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
Resolve peer dependency warnings #6613
Comments
It seems odd to me that I need to provide |
Oh, As for the client redirect plugin, I'm afraid not many people use it so they haven't complained😆 Will fix that as well As for |
Sweet, thank you! |
I'm not sure about the business with |
Tests seem good. Here're the latest results from E2E tests:
At this point... You would need to use package extensions for the rest. As for |
Thanks! I guess we could open issues with CRA and |
algolia/docsearch#1272 I wonder how soon the CRA one can be merged though, traffic in that repo is insane |
@Josh-Cena I tried updating to latest canary now. Getting a new one, otherwise looks good 👍
|
Oh, that was a minor regression unnoticed. Thanks for reporting @SimenB |
Have you read the Contributing Guidelines on issues?
Prerequisites
npm run clear
oryarn clear
command.rm -rf node_modules yarn.lock package-lock.json
and re-installing packages.Description
Jest is currently on a slightly old version of docusaurus (jestjs/jest#12138), and when running
yarn install
, we get a bunch of peer dependency warnings.I tried to upgrade to rc.15, and there are even more warnings now 🙈
Steps to reproduce
yarn
Expected behavior
Only a single peer dependency warning from
jscodeshift
Actual behavior
10+ peer warnings from docusaurus
Your environment
0.0.0-4269
and2.0.0-beta.15
Reproducible demo
No response
Self-service
The text was updated successfully, but these errors were encountered: