Bump the npm group across 1 directory with 23 updates

[dependabot]

Bumps the npm group with 23 updates in the / directory:

Package	From	To
@ant-design/icons	5.5.1	5.5.2
@dnd-kit/core	6.1.0	6.3.1
@dnd-kit/sortable	8.0.0	10.0.0
@types/node	22.9.0	22.10.7
@types/w3c-web-serial	1.0.6	1.0.7
@vitejs/plugin-react	4.3.1	4.3.4
antd	5.22.0	5.23.2
i18next	23.16.5	24.2.1
i18next-browser-languagedetector	8.0.0	8.0.2
i18next-http-backend	2.6.2	3.0.1
react	18.3.1	19.0.0
@types/react	18.3.12	19.0.7
react-dom	18.3.1	19.0.0
@types/react-dom	18.3.1	19.0.3
react-i18next	15.1.1	15.4.0
react-syntax-highlighter	15.5.0	15.6.1
react-router-dom	6.28.0	7.1.3
styled-components	6.1.13	6.1.14
vite	5.4.11	6.0.10
vite-tsconfig-paths	5.1.2	5.1.4
yup	1.4.0	1.6.1
@babel/plugin-transform-private-property-in-object	7.24.7	7.25.9
concurrently	8.2.2	9.1.2

Updates @ant-design/icons from 5.5.1 to 5.5.2

Commits

• See full diff in compare view

Updates @dnd-kit/core from 6.1.0 to 6.3.1

Release notes

Sourced from @​dnd-kit/core's releases.

@​dnd-kit/core@​6.3.1

Patch Changes

• #1555 62f632a Thanks @​clauderic! - Added Tab to the list of default key codes that end a drag and drop operation. Can be customized by passing in a custom list of keyCodes to the KeyboardSensor options.

@​dnd-kit/core@​6.3.0

Minor Changes

• #1539 0c6a28d Thanks @​irobot! - Make it possible to add visual cues when using activation constraints.

  Context

  Activation constraints are used when we want to prevent accidental dragging or when pointer press can mean more than "start dragging".

  A typical use case is a button that needs to respond to both "click" and "drag" gestures. Clicks can be distinguished from drags based on how long the pointer was held pressed.

  The problem

  A control that responds differently to a pointer press based on duration or distance can be confusing to use -- the user has to guess how long to keep holding or how far to keep dragging until their intent is acknowledged.

  Implementing such cues is currently possible by attaching extra event listeners so that we know when a drag is pending. Furthermore, the listener needs to have access to the same constraints that were applied to the sensor initiating the drag. This can be made to work in simple cases, but it becomes error-prone and difficult to maintain in complex scenarios.

  Solution

  This changeset proposes the addition of two new events: onDragPending and onDragAbort.

  onDragPending

  A drag is considered to be pending when the pointer has been pressed and there are activation constraints that need to be satisfied before a drag can start.

  This event is initially fired on pointer press. At this time offset (see below) will be undefined.

  It will subsequently be fired every time the pointer is moved. This is to enable visual cues for distance-based activation.

  The event's payload contains all the information necessary for providing visual feedback:

  export interface DragPendingEvent {

... (truncated)

Changelog

Sourced from @​dnd-kit/core's changelog.

6.3.1

Patch Changes

• #1555 62f632a Thanks @​clauderic! - Added Tab to the list of default key codes that end a drag and drop operation. Can be customized by passing in a custom list of keyCodes to the KeyboardSensor options.

6.3.0

Minor Changes

• #1539 0c6a28d Thanks @​irobot! - Make it possible to add visual cues when using activation constraints.

  Context

  Activation constraints are used when we want to prevent accidental dragging or when pointer press can mean more than "start dragging".

  A typical use case is a button that needs to respond to both "click" and "drag" gestures. Clicks can be distinguished from drags based on how long the pointer was held pressed.

  The problem

  A control that responds differently to a pointer press based on duration or distance can be confusing to use -- the user has to guess how long to keep holding or how far to keep dragging until their intent is acknowledged.

  Implementing such cues is currently possible by attaching extra event listeners so that we know when a drag is pending. Furthermore, the listener needs to have access to the same constraints that were applied to the sensor initiating the drag. This can be made to work in simple cases, but it becomes error-prone and difficult to maintain in complex scenarios.

  Solution

  This changeset proposes the addition of two new events: onDragPending and onDragAbort.

  onDragPending

  A drag is considered to be pending when the pointer has been pressed and there are activation constraints that need to be satisfied before a drag can start.

  This event is initially fired on pointer press. At this time offset (see below) will be undefined.

  It will subsequently be fired every time the pointer is moved. This is to enable visual cues for distance-based activation.

  The event's payload contains all the information necessary for providing visual feedback:

... (truncated)

Commits

• 97c1609 Version Packages
• 62f632a End keyboard drag operation when pressing tab
• 060c982 Version Packages
• 9175566 Merge branch 'master' into feature/constraint-cues
• 2eedcc3 Version Packages
• 835ae76 Lint
• 3c4f627 Merge pull request #1543 from clauderic/patch-1
• baad391 Merge pull request #1542 from clauderic/fix-zero-id
• b7f46bb Merge pull request #1541 from clauderic/handle-cancel-events
• 2eb636f Merge pull request #1435 from knaveenkumar3576/user/knaveenkumar3576/improved...
• Additional commits viewable in compare view

Updates @dnd-kit/sortable from 8.0.0 to 10.0.0

Release notes

Sourced from @​dnd-kit/sortable's releases.

@​dnd-kit/sortable@​10.0.0

Patch Changes

• Updated dependencies [0c6a28d]:
  • @​dnd-kit/core@​6.3.0

@​dnd-kit/sortable@​9.0.0

Patch Changes

• #1542 f629ec6 Thanks @​clauderic! - Fix bug with draggable and sortable elements with an id equal to 0.

• Updated dependencies [00ec286, 995dc23, f629ec6, 99643f6, 6bbe39b, 545a41c, bcaf7c4]:

  • @​dnd-kit/core@​6.2.0

Changelog

Sourced from @​dnd-kit/sortable's changelog.

10.0.0

Patch Changes

• Updated dependencies [0c6a28d]:
  • @​dnd-kit/core@​6.3.0

9.0.0

Patch Changes

• #1542 f629ec6 Thanks @​clauderic! - Fix bug with draggable and sortable elements with an id equal to 0.

• Updated dependencies [00ec286, 995dc23, f629ec6, 99643f6, 6bbe39b, 545a41c, bcaf7c4]:

  • @​dnd-kit/core@​6.2.0

Commits

• 060c982 Version Packages
• 2eedcc3 Version Packages
• f629ec6 Fix for when id is equal to 0
• See full diff in compare view

Updates @types/node from 22.9.0 to 22.10.7

Commits

• See full diff in compare view

Updates @types/w3c-web-serial from 1.0.6 to 1.0.7

Commits

• See full diff in compare view

Updates @vitejs/plugin-react from 4.3.1 to 4.3.4

Release notes

Sourced from @​vitejs/plugin-react's releases.

v4.3.4

Add Vite 6 to peerDependencies range

Vite 6 is highly backward compatible, not much to add!

Force Babel to output spec compliant import attributes #386

The default was an old spec (with type: "json"). We now enforce spec compliant (with { type: "json" })

v4.3.3

React Compiler runtimeModule option removed

React Compiler was updated to accept a target option and runtimeModule was removed. vite-plugin-react will still detect runtimeModule for backwards compatibility.

When using a custom runtimeModule or target !== '19', the plugin will not try to pre-optimize react/compiler-runtime dependency.

The react-compiler-runtime is now available on npm can be used instead of the local shim for people using the compiler with React < 19.

Here is the configuration to use the compiler with React 18 and correct source maps in development:

npm install babel-plugin-react-compiler react-compiler-runtime @babel/plugin-transform-react-jsx-development

export default defineConfig(({ command }) => {
  const babelPlugins = [['babel-plugin-react-compiler', { target: '18' }]]
  if (command === 'serve') {
    babelPlugins.push(['@babel/plugin-transform-react-jsx-development', {}])
  }
return {
plugins: [react({ babel: { plugins: babelPlugins } })],
}
})

v4.3.2

Ignore directive sourcemap error #369

Changelog

Sourced from @​vitejs/plugin-react's changelog.

4.3.4 (2024-11-26)

Add Vite 6 to peerDependencies range

Vite 6 is highly backward compatible, not much to add!

Force Babel to output spec compliant import attributes #386

The default was an old spec (with type: "json"). We now enforce spec compliant (with { type: "json" })

4.3.3 (2024-10-19)

React Compiler runtimeModule option removed

React Compiler was updated to accept a target option and runtimeModule was removed. vite-plugin-react will still detect runtimeModule for backwards compatibility.

When using a custom runtimeModule or target !== '19', the plugin will not try to pre-optimize react/compiler-runtime dependency.

The react-compiler-runtime is now available on npm can be used instead of the local shim for people using the compiler with React < 19.

Here is the configuration to use the compiler with React 18 and correct source maps in development:

npm install babel-plugin-react-compiler react-compiler-runtime @babel/plugin-transform-react-jsx-development

export default defineConfig(({ command }) => {
  const babelPlugins = [['babel-plugin-react-compiler', { target: '18' }]]
  if (command === 'serve') {
    babelPlugins.push(['@babel/plugin-transform-react-jsx-development', {}])
  }
return {
plugins: [react({ babel: { plugins: babelPlugins } })],
}
})

4.3.2 (2024-09-29)

Ignore directive sourcemap error #369

Commits

• 2e368a6 release: plugin-react@4.3.4
• bde1ad6 feat: add Vite 6 to peerDependencies range (#390)
• 45a727c fix(deps): update all non-major dependencies (#373)
• 5d2b6c6 fix: force non-legacy import attributes babel output (#386)
• b61592a release: plugin-react@4.3.3
• e8a923f fix: add react-dom in optimizeOps to handle CJS script. (#375)
• 7a7e339 feat: support new React Compiler target option (#374)
• 63b2e38 release: plugin-react@4.3.2
• fdf6ce4 fix(deps): update all non-major dependencies (#273)
• 4544e97 feat: update refresh utils for React Router 7 support (#363)
• Additional commits viewable in compare view

Updates antd from 5.22.0 to 5.23.2

Release notes

Sourced from antd's releases.

5.23.2

• 🐞 Fix Space.Compact throwing Should not use more than one & in a selector warning. #52489
• 💄 Fix the Layout switching sidebar button style was lost. #52477
• 💄 Fix the scroll bar height is not 0 when the first row of the virtual scroll Table is collapsed. #52447 @​LeeSSHH
• 💄 Fix the last item in Descriptions did not correctly fill the remaining space. #52410 @​anyuxuan
• 💄 Fix extra margin for the last item in Radio. #52433
• 💄 Fix the Input/Mentions clear button padding was incorrect. #52407 @​ustcfury
• 💄 Fix rounded corners of addonAfter in Input compact mode. #52490 @​DDDDD12138
• 💄 Fix Menu.Item links were still clickable and lacked disabled styles when in disabled state. #52402 @​aojunhao123
• TypeScript
  • 🤖 MISC: Optimize PurePanel to use React.ComponentType type. #52480
  • 🤖 Fix missing token type for Skeleton and Rate. #52406 @​coding-ice

---

• 🐞 修复 Space.Compact 抛出 Should not use more than one & in a selector 警告信息的问题。#52489
• 💄 修复 Layout 切换侧边栏按钮样式丢失的问题。#52477
• 💄 修复 Table 收起虚拟滚动表格第一行时滚动条高度不为 0 的问题。#52447 @​LeeSSHH
• 💄 修复 Descriptions 最后一项未正确填充满剩余空间的问题。#52410 @​anyuxuan
• 💄 修复 Radio.Group 最后一项多余 margin 的问题。#52433
• 💄 修复 Input/Mentions 清除按钮 padding 不正确的问题。#52407 @​ustcfury
• 💄 修复 Input 紧凑模式中 addonAfter 的圆角问题。#52490 @​DDDDD12138
• 💄 修复 Menu.Item 在禁用状态下链接仍可点击且缺少禁用样式的问题。#52402 @​aojunhao123
• TypeScript
  • 🤖 MISC: 优化 PurePanel 使用 React.ComponentType 类型。#52480
  • 🤖 修复 Skeleton 和 Rate 缺失的 token 类型。#52406 @​coding-ice

5.23.1

• 🆕 Add Tree leaf node className for differentiate node type. #52274 @​EmilyyyLiu
• 🐞 Fix DatePicker switch buttons is not hidden when superPrevIcon/superNextIcon/prevIcon/nextIcon is null. #52327 @​afc163
• 🐞 Fix Select throws error not a valid selector in Jest tests. #51844 @​renovate
• 🐞 Fix Layout.Sider under ConfigProvider directly, the theme not working. #52302 @​zombieJ
• 🐞 Fix Splitter lost previous state when re-expanding. #52222 @​jjlstruggle
• 🐞 Fix Table unexpected row selections when set checkStrictly to false in tree mode. #52338 @​LeeSSHH
• Button
  • 🐞 Fix Button alignment and icon centering by adjusting the icon size for icon-only Buttons. #52353 @​afc163
  • 💄 Fix Button missing box-shadow style. #52304 @​zombieJ
• RTL
  • 💄 Fix Collapse arrow direction in RTL mode. #52374 @​aojunhao123
  • 💄 Fix Layout.Sider arrow direction in RTL mode. #52374 @​aojunhao123

---

• 🆕 新增 Tree 组件叶子节点的 className 用于区分节点类型。#52274 @​EmilyyyLiu
• 🐞 修复 DatePicker superPrevIcon/superNextIcon/prevIcon/nextIcon 设置为 null 时切换按钮依旧存在的问题。#52327 @​afc163
• 🐞 修复 Select 组件在 jest 测试中报错 not a valid selector 的问题。#51844 @​renovate
• 🐞 修复 Layout.Sider 直接嵌套在 ConfigProvider 下时，theme 配置无效的问题。#52302 @​zombieJ
• 🐞 修复 Splitter 二次展开时丢失上一次状态的问题。#52222 @​jjlstruggle
• 🐞 修复 Table 树形展示且设置 checkStrictly 为 false 时，某些行被错误选中的问题。#52338 @​LeeSSHH
• Button
  • 🐞 调整 Button 纯图标的大小从而修复按钮对齐和图标居中问题。#52353 @​afc163
  • 💄 修复 Button 丢失阴影样式的问题。#52304 @​zombieJ
• RTL
  • 💄 修复 Collapse 在 RTL 模式下的箭头方向。#52374 @​aojunhao123

... (truncated)

Changelog

Sourced from antd's changelog.

5.23.2

2025-01-20

• 🐞 Fix Space.Compact throwing Should not use more than one & in a selector warning. #52489
• 💄 Fix the Layout switching sidebar button style was lost. #52477
• 💄 Fix the scroll bar height is not 0 when the first row of the virtual scroll Table is collapsed. #52447 @​LeeSSHH
• 💄 Fix the last item in Descriptions did not correctly fill the remaining space. #52410 @​anyuxuan
• 💄 Fix extra margin for the last item in Radio. #52433
• 💄 Fix the Input/Mentions clear button padding was incorrect. #52407 @​ustcfury
• 💄 Fix rounded corners of addonAfter in Input compact mode. #52490 @​DDDDD12138
• 💄 Fix Menu.Item links were still clickable and lacked disabled styles when in disabled state. #52402 @​aojunhao123
• TypeScript
  • 🤖 MISC: Optimize PurePanel to use React.ComponentType type. #52480
  • 🤖 Fix missing token type for Skeleton and Rate. #52406 @​coding-ice

5.23.1

2025-01-13

• 🆕 Add Tree leaf node className for differentiate node type. #52274 @​EmilyyyLiu
• 🐞 Fix DatePicker switch buttons is not hidden when superPrevIcon/superNextIcon/prevIcon/nextIcon is null. #52327 @​afc163
• 🐞 Fix Select throws error not a valid selector in Jest tests. #51844 @​renovate
• 🐞 Fix Layout.Sider under ConfigProvider directly, the theme not working. #52302 @​zombieJ
• 🐞 Fix Splitter lost previous state when re-expanding. #52222 @​jjlstruggle
• 🐞 Fix Table unexpected row selections when set checkStrictly to false in tree mode. #52338 @​LeeSSHH
• Button
  • 🐞 Fix Button alignment and icon centering by adjusting the icon size for icon-only Buttons. #52353 @​afc163
  • 💄 Fix Button missing box-shadow style. #52304 @​zombieJ
• RTL
  • 💄 Fix Collapse arrow direction in RTL mode. #52374 @​aojunhao123
  • 💄 Fix Layout.Sider arrow direction in RTL mode. #52374 @​aojunhao123

5.23.0

2025-01-06

• 🔥 TreeSelect support maxCount to limit the maximum number of selections. #51759 @​aojunhao123
• 🔥 Modal width support responsive size. #51653 @​zombieJ
• 🔥 Splitter support lazy mode. #51557 @​OysterD3
• Button
  • 🔥 Button color support full color palette. #51550 @​OysterD3
  • 🆕 Button support loading={{ icon: ReactNode }} to customize loading icon. #51758 @​zhangchao-wooc
• Menu
  • 🐞 Fix Menu extra font size and vertical align issue. #52217 @​guoyunhe
  • 🆕 Menu add token subMenuItemSelectedColor to resolve submenu title color being overrided by itemSelectedColor. #52182 @​afc163
• 🆕 Semantic Props
  • 🆕 ConfigProvider support Empty semantic props classNames and styles. #52208 @​thinkasany
  • 🆕 ConfigProvider support Popconfirm semantic props classNames and styles. #52126 @​thinkasany

... (truncated)

Commits

• 89bac66 docs: add changelog 5.23.2 (#52497)
• 9a21923 docs(tour): update prop types for target and placement in documentation (#52498)
• b2beee5 docs: fix demo suspense (#52495)
• 0d51109 fix(input): border-radius issue with addonAfter in compact mode (#52490)
• f50a8e6 chore: remove warning of cssinjs in Space.Compact (#52489)
• 5f9bbb8 chore: Update README.md (#52493)
• bc21d43 docs: imporove contributors fallback style (#52491)
• 3ea2b8c site: fix react duplicated key in DumiDemoGrid (#52488)
• 0106647 fix: Layout zero width trigger missing style (#52477)
• 57bcc68 type: replace any type with React.ComponentType (#52480)
• Additional commits viewable in compare view

Updates i18next from 23.16.5 to 24.2.1

Release notes

Sourced from i18next's releases.

v24.2.1

• Standardize null/undefined checks across codebase 2275
• fix(typescript): make TFunction augmentable again 2279, fixes 2278

v24.2.0

• feat(typescript): Add strictKeyChecks option to enforce checking key existence when defaultValue is used 2274, fixes 2043

v24.1.2

• optimize fix: Bug Report: Unsafe Behavior in i18n.t Function Leading to Potential Code Execution 2273

v24.1.1

• fix: Bug Report: Unsafe Behavior in i18n.t Function Leading to Potential Code Execution 2273

v24.1.0

• try to address 2270 by cloning the store data 2271

v24.0.5

• remove extra log for 2268

v24.0.4

• simplify fix: incorrect locale detected 2268

v24.0.3

• fix: incorrect locale detected 2268
• fix: Intl.getCanonicalLocales throws with custom regions 2267

v24.0.2

• if no Intl api, log error and use dummy rule

v24.0.1

• early return and log error, if no Intl api

v24.0.0

This is a major breaking release:

• remove support for older environments
• remove old i18next JSON formats
  • To convert your existing v3 translations to the v4 format, have a look at i18next-v4-format-converter or this web tool.
• remove support for compatibility to v1 API
• Intl API is mandatory now and will not fallback anymore
• possible compatibility layer for older formats: test/compatibility/v4/v4Compatibility.js
• rename initImmediate to initAsync
• fallback to dev language if plural rule not found
• remove TypeScript v4 support. TypeScript v5 is now an optional peer dependency
• addresses
  • 2244
  • 2184
  • 2213
  • 2206
  • 2208

... (truncated)

Changelog

Sourced from i18next's changelog.

24.2.1

• Standardize null/undefined checks across codebase 2275
• fix(typescript): make TFunction augmentable again 2279, fixes 2278

24.2.0

• feat(typescript): Add strictKeyChecks option to enforce checking key existence when defaultValue is used 2274, fixes 2043

24.1.2

• optimize fix: Bug Report: Unsafe Behavior in i18n.t Function Leading to Potential Code Execution 2273

24.1.1

• fix: Bug Report: Unsafe Behavior in i18n.t Function Leading to Potential Code Execution 2273

24.1.0

• try to address 2270 by cloning the store data 2271

24.0.5

• remove extra log for 2268

24.0.4

• simplify fix: incorrect locale detected 2268

24.0.3

• fix: incorrect locale detected 2268
• fix: Intl.getCanonicalLocales throws with custom regions 2267

24.0.2

• if no Intl api, log error and use dummy rule

24.0.1

• early return and log error, if no Intl api

24.0.0

This is a major breaking release:

• remove support for older environments
• remove old i18next JSON formats
  • To convert your existing v3 translations to the v4 format, have a look at i18next-v4-format-converter or this web tool.
• remove support for compatibility to v1 API

... (truncated)

Commits

• 7e0b526 24.2.1
• 73940cc release
• 009c457 fix: make TFunction type augmentable (#2279)
• dd78378 update ts example
• e2797d5 prpare changelog
• 6e6d899 Standardize null/undefined checks across codebase (#2275)
• c55cbe8 24.2.0
• dfff2cd added some tests for undefined or null keys
• 62daae4 feat(typescript): Add strictKeyChecks option to enforce checking key existe...
• c51950e 24.1.2
• Additional commits viewable in compare view

Updates i18next-browser-languagedetector from 8.0.0 to 8.0.2

Changelog

Sourced from i18next-browser-languagedetector's changelog.

8.0.2

• fix for when passed services are null, should address 296

8.0.1

• some environments, throws when accessing document.cookie

Commits

• 9d765ed 8.0.2
• 0cd29a8 fix for when passed services are null, should address #296
• be02df9 8.0.1
• 6c1886c some environments, throws when accessing document.cookie
• e6e4089 Bump elliptic from 6.5.7 to 6.6.0 (#295)
• 5131d9a Bump elliptic from 6.5.4 to 6.5.7 (#294)
• 1f74f59 Use arrow function and implicit return in index.js (#290)
• c9f0f35 Bump braces from 3.0.2 to 3.0.3 (#289)
• e161380 refactor: Defaults (#288)
• See full diff in compare view

Updates i18next-http-backend from 2.6.2 to 3.0.1

Changelog

Sourced from i18next-http-backend's changelog.

3.0.1

• try to get rid of top-level await

3.0.0

• fix for Deno 2 and removal of unnecessary .cjs file
• for esm build environments not supporting top-level await, you should import the i18next-http-backend/cjs export or stay at v2.6.2 or v2.7.1

2.7.1

• same as 2.6.2

2.7.0

• deprecated, same as v3.0.0

Commits

• 3c0ada7 3.0.1
• dd21d68 try to get rid of top-level await
• 2f975d7 update changelog
• 00f0e59 update changelog
• 30e4fc5 3.0.0
• 8d8bf8d bump major
• 09dc9c9 update i18next dep
• 1c233f1 Mention JSONC in docs & tests (#159)
• 64e4a2e changelog
• d9629f9 typo in changelog
• Additional commits viewable in compare view

Updates react from 18.3.1 to 19.0.0

Release notes

Sourced from react's releases.

19.0.0 (December 5, 2024)

Below is a list of all new features, APIs, deprecations, and breaking changes. Read React 19 release post and React 19 upgrade guide for more information.

Note: To help make the upgrade to React 19 easier, we’ve published a react@18.3 release that is identical to 18.2 but adds warnings for deprecated APIs and other changes that are needed for React 19. We recommend upgrading to React 18.3.1 first to help identify any issues before upgrading to React 19.

New Features

React

• Actions: startTransition can now accept async functions. Functions passed to startTransition are called “Actions”. A given Transition can include one or more Actions which update state in the background and update the UI with one commit. In addition to updating state, Actions can now perform side effects including async requests, and the Action will wait for the work to finish before finishing the Transition. This feature allows Transitions to include side effects like fetch() in the pending state, and provides support for error handling, and optimistic updates.
• useActionState: is a new hook to order Actions inside of a Transition with access to the state of the action, and the pending state. It accepts a reducer that can call Actions, and the initial state used for first render. It also accepts an optional string that is used if the action is passed to a form action prop to support progressive enhancement in forms.
• useOptimistic: is a new hook to update state while a Transition is in progress. It returns the state, and a set function that can be called inside a transition to “optimistically” update the state to expected final value immediately while the Transition completes in the background. When the transition finishes, the state is updated to the new value.
• use: is a new API that allows reading resources in render. In React 19, use accepts a promise or Context. If provided a promise, use will suspend until a value is resolved. use can only be used in render but can be called conditionally.
• ref as a prop: Refs can now be used as props, removing the need for forwardRef.
• Suspense sibling pre-warming: When a component suspends, React will immediately commit the fallback of the nearest Suspense boundary, without waiting for the entire sibling tree to render. After the fallback commits, React will schedule another render for the suspended siblings to “pre-warm” lazy requests.

React DOM Client

• <form> action prop: Form Actions allow you to manage forms automatically and integrate with useFormStatus. When a <form> action succeeds, React will automatically reset the form for uncontrolled components. The form can be reset manually with the new requestFormReset API.
• <button> and <input> formAction prop: Actions can be passed to the formAction prop to configure form submission behavior. This allows using different Actions depending on the input.
• useFormStatus: is a new hook that provides the status of the parent <form> action, as if the form was a Context provider. The hook returns the values: pending, data, method, and action.
• Support for Document Metadata: We’ve added support for rendering document metadata tags in components natively. React will automatically hoist them into the <head> section of the document.
• Support for Stylesheets: React 19 will ensure stylesheets are inserted into the <head> on the client before revealing the content of a Suspense boundary that depends on that stylesheet.
• Support for async scripts: Async scripts can be rendered anywhere in the component tree and React will handle ordering and deduplication.
• Support for preloading resources: React 19 ships with preinit, preload, prefetchDNS, and preconnect APIs to optimize initial page loads by moving discovery of additional resources like fonts out of stylesheet loading. They can also be used to prefetch resources used by an anticipated navigation.

React DOM Server

• Added prerender and prerenderToNodeStream APIs for static site generation. They are designed to work with streaming environments like Node.js Streams and Web Streams. Unlike renderToString, they wait for data to load for HTML generation.

React Server Components

• RSC features such as directives, server components, and server functions are now stable. This means libraries that ship with Server Components can now target React 19 as a peer dependency with a react-server export condition for use in frameworks that support the Full-stack React Architecture. The underlying APIs used to implement a React Server Components bundler or framework do not follow semver and may break between minors in React 19.x. See docs for how to support React Server Components.

Deprecations

• Deprecated: element.ref access: React 19 supports ref as a prop, so we’re deprecating element.ref in favor of element.props.ref. Accessing will result in a warning.
• react-test-renderer: In React 19, react-test-renderer logs a deprecation warning and has switched to concurrent rendering for web usage. We recommend migrating your tests to @​testinglibrary.com/docs/react-testing-library/intro/) or @​testingesting-library.com/docs/react-native-testing-library/intro)

Breaking Changes

React 19 brings in a number of breaking changes, including the removals of long-deprecated APIs. We recommend first upgrading to 18.3.1, where we've added additional deprecation warnings. Check out the upgrade guide for more details and guidance on codemodding.

React

• New JSX Transform is now required: We introduced a new JSX transform in 2020 to improve bundle size and use JSX without importing React. In React 19, we’re adding additional improvements like using ref as a prop and JSX speed improvements that require the new transform.
• Errors in render are not re-thrown: Errors that are not caught by an Error Boundary are now reported to window.reportError. Errors that are caught by an Error Boundary are reported to console.error. We’ve introduced onUncaughtError and onCaughtError methods to createRoot and hydrateRoot to customize this error handling.
• Removed: propTypes: Using propTypes will now be silently ignored. If required, we recommend migrating to TypeScript or another type-checking solution.
• Removed: defaultProps for functions: ES6 default parameters can be used in place. Class components continue to support defaultProps since there is no ES6 alternative.
• Removed: contextTypes and getChildContext: Legacy Context for class components has been removed in favor of the contextType API.

... (truncated)

Changelog

Sourced from react's changelog.

19.0.0 (December 5, 2024)

Below is a list of all new features, APIs, deprecations, and breaking changes. Read React 19 release post and React 19 upgrade guide for more information.

Note: To help make the upgrade to React 19 easier, we’ve published a react@18.3 release that is identical to 18.2 but adds warnings for deprecated APIs and other changes that are needed for React 19. We recommend upgrading to React 18.3.1 first to help identify any issues before upgrading to React 19.

New Features

React

• Actions: startTransition can now accept async functions. Functions passed to startTransition are called “Actions”. A given Transition can include one or more Actions which update state in the background and update the UI with one commit. In addition to updating state, Actions can now perform side effects including async requests, and the Action will wait for the work to finish before finishing the Transition. This feature allows Transitions to ...

  Description has been truncated

[dependabot]

Looks like these dependencies are updatable in another way, so this is no longer needed.