Repository navigation
fix(deps): upgrade workspace React while preserving plugin compatibility - #39
Conversation
There was a problem hiding this comment.
Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.
An organization owner can choose the repository organization as the billing source for reviews requested by members with a paid Copilot license. Learn about Copilot code review billing.
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 0f217fb179
ℹ️ 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".
Upgrade the workspace and plugin template to React 19.2.8, including React DOM and React 19 types, while keeping the published third-parties plugin compatible with React 18 and React 19. Rspress stays at 2.0.22.
Keep
reactandreact-dompeer dependencies at^18.0.0 || ^19.0.0. Disable React Compiler for the plugin and remove both its compiler and runtime dependencies, so published components require neitherreact-compiler-runtimenorreact/compiler-runtime. Preserve the React 18 resource API fallback and use a patch changeset. Resource API tests now assert the behavior supported by the installed React version.Validation: