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

⬆️ Update dependency @vitejs/plugin-react to v4 - autoclosed #126

Closed
wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Apr 20, 2023

Mend Renovate

This PR contains the following updates:

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

Release Notes

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

v4.2.1

Compare Source

Remove generic parameter on Plugin to avoid type error with Rollup 4/Vite 5 and skipLibCheck: false.

I expect very few people to currently use this feature, but if you are extending the React plugin via api object, you can get back the typing of the hook by importing ViteReactPluginApi:

import type { Plugin } from 'vite'
import type { ViteReactPluginApi } from '@​vitejs/plugin-react'

export const somePlugin: Plugin = {
  name: 'some-plugin',
  api: {
    reactBabel: (babelConfig) => {
      babelConfig.plugins.push('some-babel-plugin')
    },
  } satisfies ViteReactPluginApi,
}

v4.2.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.

v4.1.1

Compare Source

  • Enable retainLines to get correct line numbers for jsxDev (fix #​235)

v4.1.0

Compare Source

  • Add @types/babel__cores to dependencies (fix #​211)
  • Improve build perf when not using Babel plugins by lazy loading @babel/core #​212
  • Better invalidation message when an export is added & fix HMR for export of nullish values #​215
  • Include non-dev jsx runtime in optimizeDeps & support HMR for JS files using the non dev runtime #​224
  • The build output now contains a index.d.cts file so you don't get types errors when setting moduleResolution to node16 or nodenext in your tsconfig (we recommend using bundler which is more close to how Vite works)

v4.0.4

Compare Source

  • Fix #​198: Enable Babel if presets list is not empty

v4.0.3

Compare Source

  • Revert #​108: Remove 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.

v4.0.2

Compare Source

  • Fix fast-refresh for files that are transformed into jsx (#​188)

v4.0.1

Compare Source

v4.0.0

Compare Source

This major version include a revamp of options:

  • include/exclude now allow to completely override the files processed by the plugin (#​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:
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).

With these changes, only the file extensions is used for filtering processed files and the query param fallback is removed.

  • fastRefresh is removed (#​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)

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)
  • Wrap dynamic import to speedup analysis (#​143)

Other notable changes:

  • Silence "use client" warning (#​144, fix #​137)
  • Fast Refresh is applied on JS files using automatic runtime (#​122, fix #​83)
  • Vite 4.2 is required as a peer dependency (#​128)
  • Avoid key collision in React refresh registration (a74dfef, fix #​116)
  • Throw when refresh runtime is loaded twice (#​108, fix #​101)
  • Don't force optimization of jsx-runtime (#​132)

Configuration

📅 Schedule: Branch creation - "after 09:00 every weekday,before 23:00 every weekday,every weekday" in timezone Asia/Tokyo, 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 has been generated by Mend Renovate. View repository job log here.

@renovate renovate bot force-pushed the renovate/vitejs-plugin-react-4.x branch from 0ed80c4 to d66fd1e Compare June 19, 2023 23:49
@renovate renovate bot force-pushed the renovate/vitejs-plugin-react-4.x branch 2 times, most recently from 439747c to d9db78f Compare July 10, 2023 07:13
@renovate renovate bot force-pushed the renovate/vitejs-plugin-react-4.x branch from d9db78f to 7f4e791 Compare July 31, 2023 17:30
@renovate renovate bot force-pushed the renovate/vitejs-plugin-react-4.x branch from 7f4e791 to 2d853be Compare September 24, 2023 21:55
@renovate renovate bot force-pushed the renovate/vitejs-plugin-react-4.x branch from 2d853be to 53fca6a Compare November 2, 2023 09:51
@renovate renovate bot force-pushed the renovate/vitejs-plugin-react-4.x branch from 53fca6a to 05c5312 Compare November 16, 2023 14:02
@renovate renovate bot force-pushed the renovate/vitejs-plugin-react-4.x branch from 05c5312 to bddb036 Compare December 4, 2023 19:36
@renovate renovate bot force-pushed the renovate/vitejs-plugin-react-4.x branch from bddb036 to 30cdee6 Compare January 8, 2024 19:34
@renovate renovate bot force-pushed the renovate/vitejs-plugin-react-4.x branch from 30cdee6 to 718ba0e Compare January 17, 2024 21:54
@renovate renovate bot force-pushed the renovate/vitejs-plugin-react-4.x branch from 718ba0e to 914fbe1 Compare March 3, 2024 18:48
@renovate renovate bot force-pushed the renovate/vitejs-plugin-react-4.x branch from 914fbe1 to 9fc0994 Compare March 21, 2024 00:52
@renovate renovate bot changed the title ⬆️ Update dependency @vitejs/plugin-react to v4 ⬆️ Update dependency @vitejs/plugin-react to v4 - autoclosed Apr 22, 2024
@renovate renovate bot closed this Apr 22, 2024
@renovate renovate bot deleted the renovate/vitejs-plugin-react-4.x branch April 22, 2024 15:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants