release: @rsbuild/plugin-react v2.1.0#7945
Conversation
📝 WalkthroughWalkthroughThe 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches📝 Generate docstrings
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: f2924c3f5a
ℹ️ 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".
| { | ||
| "name": "@rsbuild/plugin-react", | ||
| "version": "2.0.1", | ||
| "version": "2.1.0", |
There was a problem hiding this comment.
Require core 2.1 for the 2.1 release
When consumers keep @rsbuild/core on a 2.0.x release (the peer range still permits it, and the React templates still allow ^2.0.14), installing this newly published @rsbuild/plugin-react@2.1.0 makes the generated declarations reference Rspack.SwcLoaderTransformConfig['reactCompiler']; @rsbuild/core 2.0.x uses Rspack types where that key does not exist, so TypeScript with skipLibCheck: false fails before user code is checked even if reactCompiler is never used. Please either require/bump core to >=2.1.0 for this release or make the exported type compatible with core 2.0.x.
Useful? React with 👍 / 👎.
Summary
Release
@rsbuild/plugin-reactas2.1.0for the newreactCompileroption.Related Links