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

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@vitejs/plugin-react-swc	3.3.0 -> 3.8.1

---

Release Notes

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

v3.8.1

Compare Source

Remove WebContainers warning #​268

SWC is now supported in WebContainers 🎉

v3.8.0

Compare Source

Add useAtYourOwnRisk_mutateSwcOptions option

The future of Vite is with OXC, and from the beginning this was a design choice to not exposed too many specialties from SWC so that Vite React users can move to another transformer later.
Also debugging why some specific version of decorators with some other unstable/legacy feature doesn't work is not fun, so we won't provide support for it, hence the name useAtYourOwnRisk.

react({
  useAtYourOwnRisk_mutateSwcOptions(options) {
    options.jsc.parser.decorators = true;
    options.jsc.transform.decoratorVersion = "2022-03";
  },
});

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

• Support Vitest deps.experimentalOptimizer (#​115)

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: Enabled.

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

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

---

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

---

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

[changeset-bot]

⚠️ No Changeset found

Latest commit: 7e2a5a6

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[github-actions]

🚀 Snapshot Release (alpha)

The latest changes of this PR are available as alpha on npm (based on the declared changesets):

Package	Version	Info
@graphql-codegen/visitor-plugin-common	5.6.1-alpha-20250121060138-dce43ae8e6b4a83ce2927dd7bde4e1dcc26c8c9b	npm ↗︎ unpkg ↗︎
@graphql-codegen/typescript-document-nodes	4.0.13-alpha-20250121060138-dce43ae8e6b4a83ce2927dd7bde4e1dcc26c8c9b	npm ↗︎ unpkg ↗︎
@graphql-codegen/gql-tag-operations	4.0.13-alpha-20250121060138-dce43ae8e6b4a83ce2927dd7bde4e1dcc26c8c9b	npm ↗︎ unpkg ↗︎
@graphql-codegen/typescript-operations	4.4.1-alpha-20250121060138-dce43ae8e6b4a83ce2927dd7bde4e1dcc26c8c9b	npm ↗︎ unpkg ↗︎
@graphql-codegen/typescript-resolvers	4.4.2-alpha-20250121060138-dce43ae8e6b4a83ce2927dd7bde4e1dcc26c8c9b	npm ↗︎ unpkg ↗︎
@graphql-codegen/typed-document-node	5.0.13-alpha-20250121060138-dce43ae8e6b4a83ce2927dd7bde4e1dcc26c8c9b	npm ↗︎ unpkg ↗︎
@graphql-codegen/typescript	4.1.3-alpha-20250121060138-dce43ae8e6b4a83ce2927dd7bde4e1dcc26c8c9b	npm ↗︎ unpkg ↗︎
@graphql-codegen/client-preset	4.6.0-alpha-20250121060138-dce43ae8e6b4a83ce2927dd7bde4e1dcc26c8c9b	npm ↗︎ unpkg ↗︎
@graphql-codegen/graphql-modules-preset	4.0.13-alpha-20250121060138-dce43ae8e6b4a83ce2927dd7bde4e1dcc26c8c9b	npm ↗︎ unpkg ↗︎

[github-actions]

💻 Website Preview

The latest changes are available as preview in: https://pr-10098.graphql-code-generator.pages.dev