Skip to content
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

fix(deps): update dependency @vitejs/plugin-react-swc to v3.7.2 #16

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Oct 30, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@vitejs/plugin-react-swc 3.3.0 -> 3.7.2 age adoption passing confidence

Release Notes

vitejs/vite-plugin-react-swc (@​vitejs/plugin-react-swc)

v3.7.2

Compare Source

Add Vite 6 to peerDependencies range #​207

Thanks @​RobinTail

Revert throw when refresh runtime is loaded twice #​237

Revert the throw when refresh runtime is loaded twice to enable usage in micro frontend apps. This was added to help fix setup usage, and this is not worth an annoying warning for others or a config parameter.

This revert was done in the Babel plugin last year and I didn't port it back.

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

  • Add devTarget option (fixes #​141)
  • Disable Fast Refresh based on config.server.hmr === false instead of process.env.TEST
  • Warn when plugin is in WebContainers (see #​118)
  • Better invalidation message when an export is added & fix HMR for export of nullish values (#​143)

v3.3.2

Compare Source

v3.3.1

Compare Source

  • Add 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)
  • Throw an error when the MDX plugin is after this one (#​100). This is an expected breaking change added in 3.2.0 and this should people that were using both plugins before this version to migrate.

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot changed the title fix(deps): update dependency @vitejs/plugin-react-swc to v3.7.1 fix(deps): update dependency @vitejs/plugin-react-swc to v3.7.2 Nov 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants