jpedroschmitz / gatsby-starter-ts

TypeScript starter for Gatsby. No plugins and styling. Exactly the necessary to start. Ready for Gatsby 5 🔥
https://typescript.gatsbyjs.io
MIT License
304 stars 27 forks source link

chore(deps): update dependency @vitejs/plugin-react to v4 #854

Closed renovate[bot] closed 1 year ago

renovate[bot] commented 1 year ago

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@vitejs/plugin-react (source) 3.1.0 -> 4.0.0 age adoption passing confidence

Release Notes

vitejs/vite-plugin-react ### [`v4.0.0`](https://togithub.com/vitejs/vite-plugin-react/blob/HEAD/packages/plugin-react/CHANGELOG.md#​400-2023-04-20) [Compare Source](https://togithub.com/vitejs/vite-plugin-react/compare/cda8145b8dc5a7211c0e3f8a253b4cac9c2c3d42...f87d23e91fa48b8a8488dd8bee5277070f5fc3c2) This major version include a revamp of options: - `include`/`exclude` now allow to completely override the files processed by the plugin ([#​122](https://togithub.com/vitejs/vite-plugin-react/pull/122)). This is more in line with other Rollup/Vite plugins and simplify the setup of enabling Fast Refresh for `.mdx` files. This can be done like this: ```js export default defineConfig({ plugins: [ { enforce: 'pre', ...mdx() }, react({ include: /\.(mdx|js|jsx|ts|tsx)$/ }), ], }) ``` These changes also allow to apply Babel plugins on files outside Vite root (expect in node_modules), which improve support for monorepo (fix [#​16](https://togithub.com/vitejs/vite-plugin-react/issues/16)). With these changes, only the file extensions is used for filtering processed files and the query param fallback is removed. - `fastRefresh` is removed ([#​122](https://togithub.com/vitejs/vite-plugin-react/pull/122)). This should be correctly activated by plugin without configuration. - `jsxPure` is removed. This is a niche use case that was just passing down the boolean to esbuild.jsxSideEffects. ([#​129](https://togithub.com/vitejs/vite-plugin-react/pull/129)) The support for React auto import whe using classic runtime is removed. This was prone to errors and added complexity for no good reason given the very wide support of automatic runtime nowadays. This migration path should be as simple as removing the runtime option from the config. This release goes in hand with the upcoming Vite 4.3 release focusing on performances: - Cache plugin load ([#​141](https://togithub.com/vitejs/vite-plugin-react/issues/141)) - Wrap dynamic import to speedup analysis ([#​143](https://togithub.com/vitejs/vite-plugin-react/issues/143)) Other notable changes: - Silence "use client" warning ([#​144](https://togithub.com/vitejs/vite-plugin-react/pull/144), fix [#​137](https://togithub.com/vitejs/vite-plugin-react/issues/137)) - Fast Refresh is applied on JS files using automatic runtime ([#​122](https://togithub.com/vitejs/vite-plugin-react/pull/122), fix [#​83](https://togithub.com/vitejs/vite-plugin-react/issues/83)) - Vite 4.2 is required as a peer dependency ([#​128](https://togithub.com/vitejs/vite-plugin-react/pull/128)) - Avoid key collision in React refresh registration ([a74dfef](https://togithub.com/vitejs/vite-plugin-react/commit/a74dfef), fix [#​116](https://togithub.com/vitejs/vite-plugin-react/issues/116)) - Throw when refresh runtime is loaded twice ([#​108](https://togithub.com/vitejs/vite-plugin-react/pull/108), fix [#​101](https://togithub.com/vitejs/vite-plugin-react/issues/101)) - Don't force optimization of jsx-runtime ([#​132](https://togithub.com/vitejs/vite-plugin-react/pull/132))

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.



This PR has been generated by Mend Renovate. View repository job log here.

renovate[bot] commented 1 year ago

⚠ Artifact update problem

Renovate 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
undefined