Bump the all group with 45 updates

[dependabot]

Bumps the all group with 45 updates:

Package	From	To
@dnd-kit/core	6.1.0	6.3.1
@dnd-kit/modifiers	7.0.0	9.0.0
@dnd-kit/sortable	8.0.0	10.0.0
@fontsource-variable/inter	5.0.16	5.1.1
@fontsource/inter	5.0.16	5.1.1
@fontsource/permanent-marker	5.0.8	5.1.1
@next/font	14.1.0	14.2.15
@resvg/resvg-js	2.6.0	2.6.2
@types/node	20.11.14	22.13.0
@vercel/og	0.6.2	0.6.5
clsx	2.1.0	2.1.1
eslint-config-next	14.1.0	15.1.6
lucide-react	0.320.0	0.474.0
next	14.1.0	15.1.6
p-queue	8.0.1	8.1.0
react	18.2.0	19.0.0
@types/react	18.2.49	19.0.8
react-dom	18.2.0	19.0.0
@types/react-dom	18.2.18	19.0.3
react-use	17.5.0	17.6.0
remark-rehype	11.1.0	11.1.1
sharp	0.33.2	0.33.5
typescript	5.3.3	5.7.3
unified	11.0.4	11.0.5
zod	3.22.4	3.24.1
zod-validation-error	3.0.0	3.4.0
@tailwindcss/typography	0.5.10	0.5.16
@testing-library/jest-dom	6.4.1	6.6.3
@testing-library/react	14.2.0	16.2.0
@types/culori	2.0.4	2.1.1
@types/jest	29.5.11	29.5.14
@typescript-eslint/eslint-plugin	6.20.0	8.22.0
@typescript-eslint/parser	6.20.0	8.22.0
autoprefixer	10.4.17	10.4.20
eslint-config-airbnb-typescript	17.1.0	18.0.0
eslint-config-prettier	9.1.0	10.0.1
eslint-plugin-prettier	5.1.3	5.2.3
ora	8.0.1	8.1.1
postcss	8.4.33	8.5.1
prettier	3.2.4	3.4.2
prettier-plugin-organize-imports	3.2.4	4.1.0
prettier-plugin-tailwindcss	0.5.11	0.6.11
rimraf	5.0.5	6.0.1
tailwindcss	3.4.1	4.0.2
tsx	4.7.0	4.19.2

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/modifiers from 7.0.0 to 9.0.0

Release notes

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

@​dnd-kit/modifiers@​9.0.0

Patch Changes

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

@​dnd-kit/modifiers@​8.0.0

Patch Changes

• Updated dependencies [00ec286, 995dc23, f629ec6, 99643f6, 6bbe39b, 545a41c, bcaf7c4]:
  • @​dnd-kit/core@​6.2.0

Changelog

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

9.0.0

Patch Changes

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

8.0.0

Patch Changes

• Updated dependencies [00ec286, 995dc23, f629ec6, 99643f6, 6bbe39b, 545a41c, bcaf7c4]:
  • @​dnd-kit/core@​6.2.0

Commits

• 060c982 Version Packages
• 2eedcc3 Version Packages
• See full diff 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 @fontsource-variable/inter from 5.0.16 to 5.1.1

Commits

• See full diff in compare view

Updates @fontsource/inter from 5.0.16 to 5.1.1

Commits

• See full diff in compare view

Updates @fontsource/permanent-marker from 5.0.8 to 5.1.1

Commits

• See full diff in compare view

Updates @next/font from 14.1.0 to 14.2.15

Commits

• 737c29e v14.2.15
• dbbec6a v14.2.14
• f550237 v14.2.13
• 6d7ced4 v14.2.12
• bfbc92a v14.2.11
• 937651f v14.2.10
• 6fa8982 v14.2.9
• 63b999c v14.2.8
• a1c3a03 v14.2.7
• dd32e0f Update font data (#68639)
• Additional commits viewable in compare view

Updates @resvg/resvg-js from 2.6.0 to 2.6.2

Release notes

Sourced from @​resvg/resvg-js's releases.

v2.6.2

No release notes provided.

v2.6.1

What's Changed

This version solves the problem of missing DLLs caused by not installing Visual C++ Redistributable on Windows.

Added

• chore(deps): update yarn to v3.8.1
• chore(deps): update actions/cache action to v4
• chore(deps): upgrade dependencies such as napi-rs #311
• chore(ci): adding Node.js v20 to the CI
• chore(ci): use macOS M1 machines
• doc: clarify that the default value of the defaultFontFamily is empty
• doc: improved change log documentation for M/L/C error
• test: add a bbox test with stroke
• fix(deps): update rust crate svgtypes to 0.14.0

Fixed

• fix: enable static link for windows-msvc #308 Thanks to @​Zagrios
• fix: test bindings on x86_64-unknown-linux-musl #306 Thanks to @​Brooooooklyn

New Contributors

• @​Zagrios made their first contribution in yisibl/resvg-js#308

Full Changelog: thx/resvg-js@v2.6.0...v2.6.1

v2.6.1-beta.0

What's Changed

This version solves the problem of missing DLLs caused by not installing Visual C++ Redistributable on Windows.

Added

• chore(deps): upgrade dependencies such as napi-rs #311
• chore(ci): adding Node.js v20 to the CI
• chore(ci): use macOS M1 machines
• doc: clarify that the default value of the defaultFontFamily is empty
• doc: improved change log documentation for M/L/C error
• test: add a bbox test with stroke
• fix(deps): update rust crate svgtypes to 0.14.0

Fixed

• fix: enable static link for windows-msvc #308 Thanks to @​Zagrios
• fix: test bindings on x86_64-unknown-linux-musl #306 Thanks to @​Brooooooklyn

... (truncated)

Changelog

Sourced from @​resvg/resvg-js's changelog.

[2.6.2] - 2024-03-26

Fixed

• fix: Uncaught LinkError WebAssembly.instantiate() #322

[2.6.1] - 2024-03-25

Added

• chore(deps): update yarn to v3.8.1
• chore(deps): update actions/cache action to v4

[2.6.1-beta.0] - 2024-03-11

This version solves the problem of missing DLLs caused by not installing Visual C++ Redistributable on Windows.

Added

• chore(deps): upgrade dependencies such as napi-rs #311
• chore(ci): adding Node.js v20 to the CI
• chore(ci): use macOS M1 machines
• doc: clarify that the default value of the defaultFontFamily is empty
• doc: improved change log documentation for M/L/C error
• test: add a bbox test with stroke
• fix(deps): update rust crate svgtypes to 0.14.0

Fixed

• fix: enable static link for windows-msvc #308 Thanks to @​Zagrios
• fix: test bindings on x86_64-unknown-linux-musl #306 Thanks to @​Brooooooklyn

Commits

• 9ca0584 2.6.2
• 11ea519 fix: Uncaught LinkError WebAssembly.instantiate()
• 60942db fix(ci): missing .node file for x86_64-apple-darwin
• 3b9733f 2.6.1
• f664edf chore(deps): update yarn to v3.8.1
• 761fd8e chore(deps): update actions/cache action to v4
• f8087c4 2.6.1-beta.0
• b05682b chore(deps): upgrade dependencies such as napi-rs
• caf40aa fix(deps): update rust crate svgtypes to 0.14.0
• d1ef7c8 chore(deps): update dependency @​swc-node/register to v1.9.0
• Additional commits viewable in compare view

Updates @types/node from 20.11.14 to 22.13.0

Commits

• See full diff in compare view

Updates @vercel/og from 0.6.2 to 0.6.5

Updates clsx from 2.1.0 to 2.1.1

Release notes

Sourced from clsx's releases.

v2.1.1

Patches

• (types) Include bigint in ClassValue type: (#96): 3d960ab Accommodates recent @types/react changes to ReactNode. Thank you @​ViliamKopecky~!

Chores

• Add licenses.dev badge: 684509c This service recursively analyzes entire dependency graphs to ensure that a package (or your project) is using permissive licenses. For example, here's a results table for polka@next and a larger astro example.

---

Full Changelog: lukeed/clsx@v2.1.0...v2.1.1

Commits

• 925494c 2.1.1
• 3d960ab fix(types): include bigint in ClassValue type (#96)
• 684509c chore: add licenses badge
• See full diff in compare view

Updates eslint-config-next from 14.1.0 to 15.1.6

Release notes

Sourced from eslint-config-next's releases.

v15.1.6

[!NOTE]
This release is backporting bug fixes. It does not include all pending features/changes on canary.

Core Changes

• fix: don't memory-leak promises passed to waitUntil (#75041)
• backport: fix prerender issue with intercepting routes + generateStaticParams (#75170)

Credits

Huge thanks to @​lubieowoce and @​ztanner for helping!

v15.1.5

[!NOTE]
This release is backporting bug fixes. It does not include all pending features/changes on canary.

Core Changes

• Fix missing revalidate with notFound() (#75009)
• fix: when metadatabase is set we should not warn (#74840)
• Fix @​vercel/og license SPDX expression (#74745)
• fix: ts language server rule metadata should allow null (#74704)
• fix: eslint rule of using img in metadata routes (#74864)
• Fix presentation when onerror receives an event without error (#74643)
• fix fetch lock not being consistently released #74623 (#75028)

Credits

Huge thanks to @​ijjk, @​huozhi, @​matmannion and @​ztanner for helping!

v15.1.4

[!NOTE]
This release is backporting bug fixes. It does not include all pending features/changes on canary.

Core Changes

• backport: force module format for virtual client-proxy (#74608)
• Fix prerender tags when notFound is called (#74607)
• Use provided waitUntil for pending revalidates (#74604)
• Feature: next/image: add support for images.qualities in next.config (#74588)
• Chore: docs: add missing search: '' on remotePatterns (#74587)
• Chore: docs: update version history of next/image (#73923) (#74570)
• Chore: next/image: improve imgopt api bypass detection for unsupported images (#74569)

Credits

Huge thanks to @ and @ for helping!

... (truncated)

Commits

• 38a6d01 v15.1.6
• 47102ca v15.1.5
• 48f2588 v15.1.4
• 4cbaaa1 v15.1.3
• df392a1 v15.1.2
• 4384c68 v15.1.1
• dafcd43 v15.1.0
• 2deb35d v15.0.4-canary.52
• 3970d33 v15.0.4-canary.51
• c824c18 v15.0.4-canary.50
• Additional commits viewable in compare view

Updates lucide-react from 0.320.0 to 0.474.0

Release notes

Sourced from lucide-react's releases.

New icons 0.474.0

Modified Icons 🔨

• expand (#2677) by @​jguddas

New icons 0.473.0

Modified Icons 🔨

• package (#2706) by @​sezze

New icons 0.472.0

New icons 🎨

• battery-plus (#2693) by @​Footagesus
• map-plus (#2697) by @​Seanw265

What's Changed

• lucide-svelte: Make sure license ends up in SvelteKit bundles by @​Lettnald in lucide-icons/lucide#2728
• lucide-react: Fixes aliases imports.

Full Changelog: lucide-icons/lucide@0.471.1...0.472.0

Hotfix Lucide React exports

What's Changed

• fix(lucide-react) Adds type module in package.json by @​ericfennis in lucide-icons/lucide#2731

Dynamic Icon component Lucide React and new icons 0.471.0

New Dynamic Icon Component (lucide-react)

This is an easier approach than the previous dynamicIconImports we exported in the library. This one supports all environments. We removed the examples in the docs of how you can make a dynamic icon yourself with a dedicated DynamicIcon component. This one fetches the icon data itself and renders it instead of fetching the Icon component from the library. This makes it more flexible with all the frontend frameworks and libraries that exist for React.

🚨 Not recommended for regular applications that work fine with the regular static icon components. Using the dynamic icon component increases build time, separate bundles, and separate network requests for each icon.

How to use

DynamicIcon is useful for applications that want to show icons dynamically by icon name, for example when using a content management system where icon names are stored in a database.

const App = () => (
  <DynamicIcon name="camera" color="red" size={48} />
);
</tr></table> 

... (truncated)

Commits

• 961404d replace keyof ReactSVG with SVGElementType (#2668)
• 31c3fef fix(lucide-react) Adds type module in package.json (#2731)
• 58c2e10 feat(lucide-react): Add DynamicIcon component (#2686)
• 970fc3d fix(lucide-react): support React 19 (#2666)
• 4f038d5 feat(docs): add Bun.sh support to documentation (#2642)
• 1d5c725 Fix path image backer
• d9a0119 feat(readme): add pdfme as an awesome backer (#2639)
• c6c645c docs(readme): Update readme files (#2634)
• b177743 feat(lucide-react, lucide-preact, lucide-react-native, lucide-solid, lucide-v...
• b8cd54f chore: Update dependencies (#2570)
• Additional commits viewable in compare view

Updates next from 14.1.0 to 15.1.6

Release notes

Sourced from next's releases.

v15.1.6

[!NOTE]
This release is backporting bug fixes. It does not include all pending features/changes on canary.

Core Changes

• fix: don't memory-leak promises passed to waitUntil (#75041)
• backport: fix prerender issue with intercepting routes + generateStaticParams (#75170)

Credits

Huge thanks to @​lubieowoce and @​ztanner for helping!

v15.1.5

[!NOTE]
This release is backporting bug fixes. It does not include all pending features/changes on canary.

Core Changes

• Fix missing revalidate with notFound() (#75009)
• fix: when metadatabase is set we should not warn (#74840)
• Fix @​vercel/og license SPDX expression (#74745)
• fix: ts language server rule metadata should allow null (#74704)
• fix: eslint rule of using img in metadata routes (#74864)
• Fix presentation when onerror receives an event without error (#74643)
• fix fetch lock not being consistently released #74623 (#75028)

Credits

Huge thanks to @​ijjk, @​huozhi, @​matmannion and @​ztanner for helping!

v15.1.4

[!NOTE]
This release is backporting bug fixes. It does not include all pending features/changes on canary.

Core Changes

• backport: force module format for virtual client-proxy (#74608)
• Fix prerender tags when notFound is called (#74607)
• Use provided waitUntil for pending revalidates (#74604)
• Feature: next/image: add support for images.qualities in next.config (#74588)
• Chore: docs: add missing search: '' on remotePatterns (#74587)
• Chore: docs: update version history of next/image (#73923) (#74570)
• Chore: next/image: improve imgopt api bypass detection for unsupported images (#74569)

Credits

Huge thanks to @ and @ for helping!

... (truncated)

Commits

• 38a6d01 v15.1.6
• 7099753 backport: fix prerender issue with intercepting routes + generateStaticParams...
• 819d575 [E2E] Fix config file conflict (#73818)
• 20f5a79 fix: don't memory-leak promises passed to waitUntil (#75041)
• 47102ca v15.1.5
• 9431336 fix fetch lock not being consistently released (#75028)
• 25e8443 test: fix testing snapshot
• 30b9c8f test: add feature of overriding files (#74716)
• 79bdd86 Fix presentation when onerror receives an event without error (#74643)
• 1882acb fix: eslint rule of using img in metadata routes (#74864)
• Additional commits viewable in compare view

Updates p-queue from 8.0.1 to 8.1.0

Release notes

Sourced from p-queue's releases.

v8.1.0

• Add .setPriority() for updating priority of a queued promise function (#209) 6e5cbc9

sindresorhus/p-queue@v8.0.1...v8.1.0

Commits

• 70dd11f 8.1.0
• 6e5cbc9 Add .setPriority() for updating priority of a queued promise function (#209)
• cbdbbb7 Clarify add() return value
• See full diff in compare view

Updates react from 18.2.0 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 [email protected] 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 [email protected] 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 ...

  Description has been truncated

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
ourflags-lgbt	❌ Failed (Inspect)			Feb 1, 2025 6:46am

[socket-security]

🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎

To accept the risk, merge this PR and you will not be notified again.

Alert	Package	Note	Source	CI
Possible typosquat attack	npm/[email protected]	Did you mean: ~~css-~~gradient-parser	package-lock.json package.json	⚠︎

View full report↗︎

Next steps

What is a typosquat?

Package name is similar to other popular packages and may not be the package you want.

Use care when consuming similarly named packages and ensure that you did not intend to consume a different package. Malicious packages often publish using similar names as existing popular packages.

Take a deeper look at the dependency

Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support [AT] socket [DOT] dev.

Remove the package

If you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency.

Mark a package as acceptable risk

To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of ecosystem/package-name@version specifiers. e.g. @SocketSecurity ignore npm/[email protected] or ignore all packages with @SocketSecurity ignore-all

• @SocketSecurity ignore npm/[email protected]