Skip to content

chore: upgrade to Docusaurus 3.7 #11262

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.

Sign up for GitHub

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
+1,408 −442
Open

chore: upgrade to Docusaurus 3.7 #11262

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 7 additions & 7 deletions packages/website/package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -28,12 +28,12 @@
},
"dependencies": {
"@babel/runtime": "^7.24.4",
"@docusaurus/core": "^3.2.1",
"@docusaurus/plugin-client-redirects": "^3.2.1",
"@docusaurus/plugin-pwa": "^3.2.1",
"@docusaurus/preset-classic": "^3.2.1",
"@docusaurus/remark-plugin-npm2yarn": "^3.2.1",
"@docusaurus/theme-common": "^3.2.1",
"@docusaurus/core": "~3.7.0",
"@docusaurus/plugin-client-redirects": "~3.7.0",
"@docusaurus/plugin-pwa": "~3.7.0",
"@docusaurus/preset-classic": "~3.7.0",
"@docusaurus/remark-plugin-npm2yarn": "~3.7.0",
"@docusaurus/theme-common": "~3.7.0",
"@typescript-eslint/parser": "workspace:*",
"@typescript-eslint/website-eslint": "workspace:*",
"@uiw/react-shields": "2.0.1",
Expand All @@ -55,7 +55,7 @@
"typescript": "*"
},
"devDependencies": {
"@docusaurus/module-type-aliases": "^3.2.1",
"@docusaurus/module-type-aliases": "~3.7.0",
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Almost everywhere else uses ^. I think the two existing ~s might have been unintentional. Is there a reason to go with ~ here?

If it doesn't make a strong difference, I'd think we'd rather stick with ^ for consistency.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The reason was because larger changes are needed to adopt 3.8. Ideally we'd just upgrade to 3.8, but I was having trouble with that given that I'm not a React developer. I don't know if those changes would be hard for someone familiar with Docusaurus and React, but they might be a bit beyond me.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah gotcha, so this is to make sure we don't accidentally bump to a 3.8 of something then? In that case if it makes it easier to not accidentally bump, that seems reasonable to me.

"@types/mdast": "^4.0.3",
"@types/react": "*",
"@types/unist": "^3.0.2",
Expand Down
Loading