Sourced from react's releases.
19.2.7 (June 1st, 2026)
React Server Components
- Fixed missing
FormDataentries in Server Actions which regressed in 19.2.6 (#36566 by@unstubbable)19.2.6 (May 6th, 2026)
React Server Components
- Type hardening and performance improvements (#36425 by
@eps1lonand@unstubbable)19.2.5 (April 8th, 2026)
React Server Components
- Add more cycle protections (#36236 by
@eps1lonand@unstubbable)
Sourced from react's changelog.
19.2.7 (June 1, 2026)
React Server Components
- Fixed missing
FormDataentries in Server Actions which regressed in 19.2.6 (@unstubbable#36566)19.2.6 (May 6, 2026)
React Server Components
- Type hardening and performance improvements (
@eps1lon,@unstubbable#36425)19.2.5 (March 18, 2026)
React Server Components
- Add more cycle protections (
@eps1lon,@unstubbable#36236)
6117d7c
Version 19.2.7 (#36591)eaf3e95
Version 19.2.623f4f9f
19.2.5This version was pushed to npm by GitHub Actions, a new releaser for react since your current version.
Sourced from react-dom's releases.
19.2.7 (June 1st, 2026)
React Server Components
- Fixed missing
FormDataentries in Server Actions which regressed in 19.2.6 (#36566 by@unstubbable)19.2.6 (May 6th, 2026)
React Server Components
- Type hardening and performance improvements (#36425 by
@eps1lonand@unstubbable)19.2.5 (April 8th, 2026)
React Server Components
- Add more cycle protections (#36236 by
@eps1lonand@unstubbable)
Sourced from react-dom's changelog.
19.2.7 (June 1, 2026)
React Server Components
- Fixed missing
FormDataentries in Server Actions which regressed in 19.2.6 (@unstubbable#36566)19.2.6 (May 6, 2026)
React Server Components
- Type hardening and performance improvements (
@eps1lon,@unstubbable#36425)19.2.5 (March 18, 2026)
React Server Components
- Add more cycle protections (
@eps1lon,@unstubbable#36236)
6117d7c
Version 19.2.7 (#36591)eaf3e95
Version 19.2.623f4f9f
19.2.5This version was pushed to npm by GitHub Actions, a new releaser for react-dom since your current version.
Sourced from react-i18next's changelog.
17.0.8
- fix(types):
<Trans i18nKey={$ => ...}>now typechecks underenableSelector: 'strict'. TheTranscomponent's conditional type was gated on_EnableSelector extends true | 'optimize', excluding'strict'and falling back to the legacy string-key signature. Runtime was already correct (it callskeyFromSelector(i18nKey)whenevertypeof i18nKey === 'function'); this is a type-only fix that widens the conditional to include'strict'. Thanks@Faithfinder(#1921)
Sourced from react-icons's releases.
v5.7.0
What's Changed
- update packages by
@kamijin-fantain react-icons/react-icons#1153Full Changelog: https://github.com/react-icons/react-icons/compare/v5.6.0...v5.7.0
87470d5
v5.7.0e1cb061
fix ci publishbffaab7
Revert "v5.7.0"2cde989
v5.7.0dac95cc
update npm in ci workflow21fcd04
Revert "v5.7.0"3a05518
v5.7.0c8b5050
fix github pages deploy2f78ae4
Update CI actions, Pages deploy, and staged npm publishing11f5a06
update packages (#1153)This version was pushed to npm by GitHub Actions, a new releaser for react-icons since your current version.
Sourced from @vitejs/plugin-react's releases.
plugin-react@6.0.3
No release notes provided.
plugin-react@6.0.2
Allow all options in reactCompilerPreset (#1189)
This is a type only change. Only
compilationModeandtargetoptions were available forreactCompilerPreset.plugin-react@6.0.1
Expand
@rolldown/plugin-babelpeer dep range (#1146)Expanded
@rolldown/plugin-babelpeer dep range to include^0.2.0.plugin-react@6.0.0
Remove Babel Related Features (#1123)
Vite 8+ can handle React Refresh Transform by Oxc and doesn't need Babel for it. With that, there are no transform applied that requires Babel. To reduce the installation size of this plugin, babel is no longer a dependency of this plugin and the related features are removed.
If you are using Babel, you can use
@rolldown/plugin-babeltogether with this plugin:import { defineConfig } from 'vite' import react from '@vitejs/plugin-react' +import babel from '@rolldown/plugin-babel'export default defineConfig({ plugins: [
react({babel: {plugins: ['@babel/plugin-proposal-throw-expressions'],},}),
react(),babel({plugins: ['@babel/plugin-proposal-throw-expressions'],}),For React compiler users, you can use
reactCompilerPresetfor easier setup with preconfigured filter to improve build performance:import { defineConfig } from 'vite' -import react from '@vitejs/plugin-react' +import react, { reactCompilerPreset } from '@vitejs/plugin-react' +import babel from '@rolldown/plugin-babel'export default defineConfig({ plugins: [ </tr></table>
... (truncated)
Sourced from @vitejs/plugin-react's changelog.
6.0.3 (2026-06-23)
6.0.2 (2026-05-14)
Allow all options in reactCompilerPreset (#1189)
This is a type only change. Only
compilationModeandtargetoptions were available forreactCompilerPreset.6.0.1 (2026-03-13)
Expand
@rolldown/plugin-babelpeer dep range (#1146)Expanded
@rolldown/plugin-babelpeer dep range to include^0.2.0.6.0.0 (2026-03-12)
6.0.0-beta.0 (2026-03-03)
Remove Babel Related Features (#1123)
Vite 8+ can handle React Refresh Transform by Oxc and doesn't need Babel for it. With that, there are no transform applied that requires Babel. To reduce the installation size of this plugin, babel is no longer a dependency of this plugin and the related features are removed.
If you are using Babel, you can use
@rolldown/plugin-babeltogether with this plugin:import { defineConfig } from 'vite' import react from '@vitejs/plugin-react' +import babel from '@rolldown/plugin-babel'export default defineConfig({ plugins: [
react({babel: {plugins: ['@babel/plugin-proposal-throw-expressions'],},}),
react(),babel({plugins: ['@babel/plugin-proposal-throw-expressions'],}),For React compiler users, you can use
reactCompilerPresetfor easier setup with preconfigured filter to improve build performance:import { defineConfig } from 'vite' -import react from '@vitejs/plugin-react' +import react, { reactCompilerPreset } from '@vitejs/plugin-react' </tr></table>
... (truncated)
640fd35
release: plugin-react@6.0.3889efb0
fix(deps): update all non-major dependencies (#1249)6c57dd4
fix(plugin-react): use '/' base in bundledDev preamble to fix non-root
base p...3cc33a7
fix(deps): update react-related dependencies (#1245)c0f7c7f
docs: mention the Biome rule in the "Consistent components
exports" section (...cd80f0f
fix(deps): update all non-major dependencies (#1241)e38acca
fix(deps): update all non-major dependencies (#1227)9a9bb26
perf(react): improve react compiler preset so that slightly more modules
are ...6535b55
release: plugin-react@6.0.2bf0e43b
feat(react): whitelist debugging-options (#1189)00818e9
v0.5.3 [publish]202fc4a
Fix PascalCase class exported via export { Name }
incorrectly treated as Re...Sourced from i18next-cli's changelog.
1.65.0
- fix(extract): respect
fallbackNS— keys already translated in a fallback namespace are no longer duplicated into the requesting namespace's file (#272).
- Such keys are now attributed to the fallback namespace instead, so
removeUnusedKeysno longer prunes them from the fallback file (previously a key likecancelliving only in the fallback namespace was deleted there and re-created in every namespace that used it).- A key that already has a non-empty value in the requesting namespace's own file is treated as an intentional per-namespace override and keeps being extracted there, mirroring the i18next runtime lookup order (requested namespace first, then the fallback chain). Empty-string placeholders left behind by previous extract runs are cleaned up.
- Keys not found in any fallback namespace are still added to the requesting namespace, like the i18next
saveMissingbehavior.- feat(extract):
fallbackNSnow also accepts an array of namespaces (looked up in order, like the i18next runtime option) — supported byextract,status, and the TypeScript types generator.1.64.2
- fix(status): scope the pass/fail result to the requested locale (#271).
status <locale>now exits based on that locale only, instead of always evaluating every secondary language. Previously, running e.g.status en-AUon a fully-translated primary could print "🎉 All keys present" and still exit1because an unrelated secondary (e.g. an emptyde-DE) was incomplete — a summary that contradicted the exit code.- When the requested locale is the primary, the check still fails only on absent keys (empty placeholders are tolerated); for a secondary it fails on any untranslated/absent key. The global view (
statuswith no locale) is unchanged.- The failure message now names the locale when scoped (
Error: Incomplete translations detected for "de-DE".) so the reason is no longer hidden.1.64.1
- fix(status): align plural reporting with the i18next runtime (#270).
- Plural categories that
Intl.PluralRulesonly selects for out-of-range values (e.g. French_many, which fires only for counts ≥ 1,000,000) are now treated as optional: a missing or empty variant is shown as a soft "optional plural form" note instead of a hard "missing key" error, so it no longer fails the check. Categories reachable by typical counts (including decimals, e.g. Polish/Russianother) remain required.- With
disablePlurals: true, a key used withcountis now considered satisfied when either its plural variants (_one/_other) or the bare key exist — mirroring the runtime'skey + suffix → keyresolution chain —
... (truncated)
9497126
1.65.0cebfb66
fix(extract): respect fallbackNS and stop duplicating keys into
namespace fil...4af3b5b
1.64.259e5c15
fix(status): scope pass/fail to the requested locale #27158e96ac
1.64.190fb64d
fix(status): align plural reporting with the i18next runtime #2704f32c05
1.64.09ab66af
feat(extract): support trailing wildcards in functions (e.g.
'tProps.*')3f40d0b
1.63.1eac231d
fix(init): pin @inlang/plugin-i18next@6.2.1 (restores Sherlock
annotations)