-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
[Update] Upgrade docusaurus version #7244
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you, I can't remember why we used exact versions in the past. But this seems reasonable
"@docusaurus/preset-classic": "3.6.0", | ||
"@docusaurus/theme-search-algolia": "3.6.0", | ||
"@docusaurus/preset-classic": "^3.6.0", | ||
"@docusaurus/theme-search-algolia": "^3.6.0", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
looks correct
im assuming npm upgrade docusaurus
was ran at packages/lexical-website path?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes!
for testing, u can view the generated lexical website at the vercel preview link commented by vercel bot i checked it looks fine |
Description
This pull request is to update the docusaurus version
currently, inside lexical-website, the docusaurus/plugin-client-redirects has a different version(3.7.0) so the
docusaurus build
would fail.Test plan
Before
when run
docusaurus build
Error: Invalid name=docusaurus-plugin-client-redirects version number=3.7.0.
All official @docusaurus/* packages should have the exact same version as @docusaurus/core (number=3.6.0).
After
able to run
docusaurus build