chore: update dependencies, Docusaurus v3.10 and fix config - #282
chore: update dependencies, Docusaurus v3.10 and fix config#282dave1010 wants to merge 1 commit into
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 8638db7c0d
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| "@docusaurus/module-type-aliases": "~3.10.2", | ||
| "@docusaurus/tsconfig": "~3.10.2", | ||
| "@docusaurus/types": "~3.10.2", | ||
| "@testing-library/jest-dom": "^7.0.0", |
There was a problem hiding this comment.
Keep jest-dom compatible with the CI Node version
On every push, .github/workflows/tests.yml runs the test suite with Node 18, but the lockfile for this upgraded dependency declares node >=22, and jest.setup.js imports it unconditionally before the tests run. This leaves the repository's required test job executing an unsupported dependency/runtime combination; either retain the Node-18-compatible jest-dom release or update the workflow to Node 22 or newer.
Useful? React with 👍 / 👎.
Motivation
Description
package.json(notably Docusaurus packages to ~3.10.2, React to ^19.2.8,@testing-library/jest-domto ^7.0.0, Babel/Jest updates, swc/swc-related and many transitive upgrades) and regeneratedpackage-lock.json.future.experimental_fastertofuture.fasterindocusaurus.config.tsto match the newer API.tsconfig.jsoncompiler options so test/library types resolve correctly (tweakedbaseUrl/types).Testing
npm test -- --runInBandand all test suites passed (5suites,45tests).npm run typecheckand TypeScript checks completed successfully after the tsconfig fixes.DISABLE_FASTER_BUILD=true npm run build(webpack fallback) andnpm run build(faster build path after config fix), and both produced successful builds.Codex Task