-
-
Notifications
You must be signed in to change notification settings - Fork 2
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
chore(deps): update dependency @vitejs/plugin-react-swc to ^3.7.1 #188
base: master
Are you sure you want to change the base?
Conversation
Run & review this pull request in StackBlitz Codeflow. |
|
size-limit report 📦
|
4935187
to
dd368f6
Compare
dd368f6
to
20e831d
Compare
20e831d
to
ac35d12
Compare
⚠ Artifact update problemRenovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is. ♻ Renovate will retry this branch, including artifacts, only when one of the following happens:
The artifact failure details are included below: File name: pnpm-lock.yaml
|
ac35d12
to
6821973
Compare
6821973
to
28911d5
Compare
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
28911d5
to
24bd3e1
Compare
|
24bd3e1
to
ddc179e
Compare
ddc179e
to
892e325
Compare
This PR contains the following updates:
^3.3.0
->^3.7.1
Release Notes
vitejs/vite-plugin-react-swc (@vitejs/plugin-react-swc)
v3.7.1
Compare Source
Ignore directive sourcemap error #231
v3.7.0
Compare Source
Support HMR for class components
This is a long overdue and should fix some issues people had with HMR when migrating from CRA.
v3.6.0
Compare Source
Add parserConfig option
This will unlock to use the plugin in some use cases where the original source code is not in TS. Using this option to keep using JSX inside
.js
files is highly discouraged and can be removed in any future version.v3.5.0
Compare Source
Update peer dependency range to target Vite 5
There were no breaking change that impacted this plugin, so any combination of React plugins and Vite core version will work.
Align jsx runtime for optimized dependencies
This will only affect people using internal libraries that contains untranspiled JSX. This change aligns the optimizer with the source code and avoid issues when the published source don't have
React
in the scope.Reminder: While being partially supported in Vite, publishing TS & JSX outside of internal libraries is highly discouraged.
v3.4.1
Compare Source
Add support for
.mts
(fixes #161)Using CJS in source code will not work in Vite (and will never be supported), so this is better to only use
.ts
.But to better align with Vite core defaults,
.mts
extension will now be processed like.ts
. This maybe reverted in a future major.v3.4.0
Compare Source
devTarget
option (fixes #141)config.server.hmr === false
instead ofprocess.env.TEST
v3.3.2
Compare Source
v3.3.1
Compare Source
type: module
to package.json (#101). Because the library already publish.cjs
&.mjs
files, the only change is for typing when using the node16 module resolution (fixes #95)3.2.0
and this should people that were using both plugins before this version to migrate.Configuration
📅 Schedule: Branch creation - "before 4am on the first day of the month" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.