Skip to content

build(deps): bump the package-updates group across 1 directory with 22 updates #202

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.

Sign up for GitHub

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

Jump to bottom
Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

build(deps): bump the package-updates group across 1 directory with 22 updates #202

wants to merge 1 commit into from

Conversation

@dependabot
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Dec 30, 2024

Bumps the package-updates group with 22 updates in the / directory:

Package From To
@chakra-ui/react 2.8.2 3.2.3
@emotion/react 11.13.3 11.14.0
@emotion/styled 11.13.0 11.14.0
@testing-library/jest-dom 6.5.0 6.6.3
@testing-library/react 16.0.1 16.1.0
@types/jest 29.5.13 29.5.14
@types/node 22.7.4 22.10.2
framer-motion 11.9.0 11.15.0
markdown-to-jsx 7.5.0 7.7.2
prettier 3.3.3 3.4.2
react 18.3.1 19.0.0
@types/react 18.3.10 19.0.2
react-dom 18.3.1 19.0.0
@types/react-dom 18.3.0 19.0.2
react-icons 5.3.0 5.4.0
react-router-dom 6.26.2 7.1.1
react-syntax-highlighter 15.5.0 15.6.1
typescript 5.6.2 5.7.2
web-vitals 4.2.3 4.2.4
yaml 2.5.1 2.6.1
@vitejs/plugin-react 4.3.2 4.3.4
vite 5.4.8 6.0.6

Updates @chakra-ui/react from 2.8.2 to 3.2.3

Release notes

Sourced from @​chakra-ui/react's releases.

@​chakra-ui/react@​3.2.3

Patch Changes

@​chakra-ui/react@​3.2.2

Patch Changes

  • 7234d75 Thanks @​segunadebayo! - - Slider

    • Add DraggingIndicator component to show an element only while dragging

    • Fix issue where slider marks were not styled correctly in vertical orientation

    • Menu: Update recipe to use --available-height css variable to keep the menu's height within the available space

    • System: Fixed issue where exporting withRootProvider would result in type error

    • Snippets / Slider

      • Move MarkerGroup into the Control component
      • Remove hardcoded margin values in favor of recipes and data-has-mark-label attribute

@​chakra-ui/react@​3.2.1

Patch Changes

  • #9240 561ccc0 Thanks @​Pagebakers! - - System: Fix issue where exporting withProvider and withContext would result in type error

    • Timeline: Fix issue where TimelineTitle was missing from the export
    • Tabs: Fix issue where useTabs and useTabsContext were not exported
    • Snippets / ColorPicker: Fix flex direction of ColorPickerChannelInputs and ColorPickerChannelSliders

@​chakra-ui/react@​3.2.0

Minor Changes

  • #9130 e5880fb Thanks @​segunadebayo! - - [Preview] Add new ColorPicker component to allow users pick a color in hsl, rgb, hsb formats.

    • Add new ColorSwatch component to preview a color.
    • Fix issue where mergeConfigs mutates the underlying configs passed to it.

... (truncated)

Changelog

Sourced from @​chakra-ui/react's changelog.

3.2.3

Patch Changes

3.2.2

Patch Changes

  • 7234d75 Thanks @​segunadebayo! - - Slider

    • Add DraggingIndicator component to show an element only while dragging

    • Fix issue where slider marks were not styled correctly in vertical orientation

    • Menu: Update recipe to use --available-height css variable to keep the menu's height within the available space

    • System: Fixed issue where exporting withRootProvider would result in type error

    • Snippets / Slider

      • Move MarkerGroup into the Control component
      • Remove hardcoded margin values in favor of recipes and data-has-mark-label attribute

3.2.1

Patch Changes

  • #9240 561ccc0 Thanks @​Pagebakers! - - System: Fix issue where exporting withProvider and withContext would result in type error

    • Timeline: Fix issue where TimelineTitle was missing from the export
    • Tabs: Fix issue where useTabs and useTabsContext were not exported
    • Snippets / ColorPicker: Fix flex direction of ColorPickerChannelInputs and ColorPickerChannelSliders

3.2.0

Minor Changes

... (truncated)

Commits

Updates @emotion/react from 11.13.3 to 11.14.0

Release notes

Sourced from @​emotion/react's releases.

@​emotion/react@​11.14.0

Minor Changes

  • #3281 fc4d7bd Thanks @​Andarist! - Source code has been migrated to TypeScript. From now on type declarations will be emitted based on that, instead of being hand-written.

Patch Changes

  • Updated dependencies [8dc1a6d, e1bf17e]:
    • @​emotion/cache@​11.14.0
    • @​emotion/use-insertion-effect-with-fallbacks@​1.2.0

@​emotion/react@​11.13.5

Patch Changes

  • #3270 77d930d Thanks @​emmatown! - Fix inconsistent hashes using development vs production bundles/exports conditions when using @emotion/babel-plugin with sourceMap: true (the default). This is particularly visible when using Emotion with the Next.js Pages router where the development condition is used when bundling code but not when importing external code with Node.js.

  • Updated dependencies [77d930d]:

    • @​emotion/serialize@​1.3.3
    • @​emotion/cache@​11.13.5
    • @​emotion/utils@​1.4.2
    • @​emotion/babel-plugin@​11.13.5
Commits

Updates @emotion/styled from 11.13.0 to 11.14.0

Release notes

Sourced from @​emotion/styled's releases.

@​emotion/styled@​11.14.0

Minor Changes

  • #3284 a19d019 Thanks @​Andarist! - Source code has been migrated to TypeScript. From now on type declarations will be emitted based on that, instead of being hand-written.

Patch Changes

  • Updated dependencies [e1bf17e]:
    • @​emotion/use-insertion-effect-with-fallbacks@​1.2.0

@​emotion/styled@​11.13.5

Patch Changes

  • #3270 77d930d Thanks @​emmatown! - Fix inconsistent hashes using development vs production bundles/exports conditions when using @emotion/babel-plugin with sourceMap: true (the default). This is particularly visible when using Emotion with the Next.js Pages router where the development condition is used when bundling code but not when importing external code with Node.js.

  • Updated dependencies [77d930d]:

    • @​emotion/serialize@​1.3.3
    • @​emotion/utils@​1.4.2
    • @​emotion/babel-plugin@​11.13.5
Commits

Updates @testing-library/jest-dom from 6.5.0 to 6.6.3

Release notes

Sourced from @​testing-library/jest-dom's releases.

v6.6.3

6.6.3 (2024-10-31)

Bug Fixes

  • add vitest import when extending vitest matchers (#646) (5ba0156)

v6.6.2

6.6.2 (2024-10-17)

Bug Fixes

  • remove recursive type reference in vitest types (#636) (4468378)

v6.6.1

6.6.1 (2024-10-16)

Bug Fixes

  • fix lodash import in to-have-selection.js (#642) (ced792e)

v6.6.0

6.6.0 (2024-10-16)

Features

Commits
  • 5ba0156 fix: add vitest import when extending vitest matchers (#646)
  • 4468378 fix: remove recursive type reference in vitest types (#636)
  • abba961 docs: add billyjanitsch as a contributor for bug (#644)
  • 9490615 docs: add G-Rath as a contributor for code (#643)
  • ced792e fix: fix lodash import in to-have-selection.js (#642)
  • 9b14804 feat: implement toHaveSelection (#637)
  • f5b0e94 docs: add diegohaz as a contributor for ideas (#640)
  • 68e927e docs: add pwolaq as a contributor for code, and test (#639)
  • 04005db docs: add silviuaavram as a contributor for code, and test (#638)
  • 4723de3 docs: add mibcadet as a contributor for doc (#628)
  • Additional commits viewable in compare view

Updates @testing-library/react from 16.0.1 to 16.1.0

Release notes

Sourced from @​testing-library/react's releases.

v16.1.0

16.1.0 (2024-12-05)

Features

Commits

Updates @types/jest from 29.5.13 to 29.5.14

Commits

Updates @types/node from 22.7.4 to 22.10.2

Commits

Updates framer-motion from 11.9.0 to 11.15.0

Changelog

Sourced from framer-motion's changelog.

[11.15.0] 2024-12-13

Added

  • Add support for repeat in animation sequences.

Fixed

  • Clearing scheduled jobs at the end of an animation frame to ensure memory is released should the animation loop settle.

[11.14.4] 2024-12-13

Fixed

  • Exporting AnimationSequence via "motion" entrypoint.
  • Adding support for passing normal components to motion.create() in React 19.

[11.14.3] 2024-12-13

Fixed

  • Fixing motion-dom and motion-utils entrypoints.

[11.14.2] 2024-12-13

Fixed

  • Exporting time for internal use.
  • Making MotionValue.updatedAt public for internal use.

[11.14.1] 2024-12-12

Fixed

  • Fixing missing license in motion-dom and motion-utils packages.

[11.14.0] 2024-12-12

Added

  • Added press gesture in Motion+ early access.

[11.13.6] 2024-12-10

Fixed

  • Adding React 19 to optional peer dependencies in "motion" package also.

[11.13.5] 2024-12-10

... (truncated)

Commits

Updates markdown-to-jsx from 7.5.0 to 7.7.2

Release notes

Sourced from markdown-to-jsx's releases.

v7.7.2

Patch Changes

  • 52a727c: Use ReactNode instead of ReactChild for React 19 compatibility
  • 4fa87d8: Bump ws from 8.11.0 to 8.18.0

v7.7.1

Patch Changes

  • 9d42449: Factor out unnecessary element cloning.
  • 8920038: Remove use of explicit React.createElement.

v7.7.0

Minor Changes

  • 20777bf: Add support for GFM alert-style blockquotes.

    > [!Note]
> This is a note-flavored alert blockquote. The "Note" text is injected as a `<header>` by
> default and the blockquote can be styled via the injected class `markdown-alert-note`
> for example.

Patch Changes

  • 5d7900b: Adjust type signature for <Markdown> component to allow for easier composition.
  • 918b44b: Use newer React.JSX.* namespace instead of JSX.* for React 19 compatibility.
  • 91a5948: Arbitrary HTML no longer punches out pipes when parsing rows. If you absolutely need a pipe character that isn't a table separator, either escape it or enclose it in backticks to trigger inline code handling.
  • 23caecb: Drop encountered ref attributes when processing inline HTML, React doesn't handle it well.

v7.6.2

Patch Changes

  • 0274445: Fix false detection of tables in some scenarios.
  • 69f815e: Handle class attribute from arbitrary HTML properly to avoid React warnings.
  • 857809a: Fenced code blocks are now tolerant to a missing closing sequence; this improves use in LLM scenarios where the code block markdown is being streamed into the editor in chunks.

v7.6.1

Patch Changes

  • 87d8bd3: Handle class attribute from arbitrary HTML properly to avoid React warnings.

v7.6.0

Minor Changes

  • 2281a4d: Add options.disableAutoLink to customize bare URL handling behavior.

    By default, bare URLs in the markdown document will be converted into an anchor tag. This behavior can be disabled if desired.

... (truncated)

Changelog

Sourced from markdown-to-jsx's changelog.

7.7.2

Patch Changes

  • 52a727c: Use ReactNode instead of ReactChild for React 19 compatibility
  • 4fa87d8: Bump ws from 8.11.0 to 8.18.0

7.7.1

Patch Changes

  • 9d42449: Factor out unnecessary element cloning.
  • 8920038: Remove use of explicit React.createElement.

7.7.0

Minor Changes

  • 20777bf: Add support for GFM alert-style blockquotes.

    > [!Note]
> This is a note-flavored alert blockquote. The "Note" text is injected as a `<header>` by
> default and the blockquote can be styled via the injected class `markdown-alert-note`
> for example.

Patch Changes

  • 5d7900b: Adjust type signature for <Markdown> component to allow for easier composition.
  • 918b44b: Use newer React.JSX.* namespace instead of JSX.* for React 19 compatibility.
  • 91a5948: Arbitrary HTML no longer punches out pipes when parsing rows. If you absolutely need a pipe character that isn't a table separator, either escape it or enclose it in backticks to trigger inline code handling.
  • 23caecb: Drop encountered ref attributes when processing inline HTML, React doesn't handle it well.

7.6.2

Patch Changes

  • 0274445: Fix false detection of tables in some scenarios.
  • 69f815e: Handle class attribute from arbitrary HTML properly to avoid React warnings.
  • 857809a: Fenced code blocks are now tolerant to a missing closing sequence; this improves use in LLM scenarios where the code block markdown is being streamed into the editor in chunks.

7.6.1

Patch Changes

  • 87d8bd3: Handle class attribute from arbitrary HTML properly to avoid React warnings.

7.6.0

... (truncated)

Commits

Updates prettier from 3.3.3 to 3.4.2

Release notes

Sourced from prettier's releases.

3.4.2

🔗 Changelog

3.4.1

🔗 Changelog

3.4.0

diff

🔗 Release note

Changelog

Sourced from prettier's changelog.

3.4.2

diff

Treat U+30A0 & U+30FB in Katakana Block as CJK (#16796 by @​tats-u)

Prettier doesn't treat U+30A0 & U+30FB as Japanese. U+30FB is commonly used in Japanese to represent the delimitation of first and last names of non-Japanese people or “and”. The following “C言語・C++・Go・Rust” means “C language & C++ & Go & Rust” in Japanese.

<!-- Input (--prose-wrap=never) -->
C言
語
・
C++
・
Go
・
Rust
<!-- Prettier 3.4.1 -->
C言語・ C++ ・ Go ・ Rust
<!-- Prettier 3.4.2 -->
C言語・C++・Go・Rust

U+30A0 can be used as the replacement of the - in non-Japanese names (e.g. “Saint-Saëns” (Charles Camille Saint-Saëns) can be represented as “サン゠サーンス” in Japanese), but substituted by ASCII hyphen (U+002D) or U+FF1D (full width hyphen) in many cases (e.g. “サン=サーンス” or “サン＝サーンス”).

Fix comments print on class methods with decorators (#16891 by @​fisker)

// Input
class A {
  @decorator
  /** 
   * The method description
   *
  */
  async method(foo: Foo, bar: Bar) {
    console.log(foo);
  }
}
// Prettier 3.4.1
class A {
@​decorator
async /**
</tr></table>

... (truncated)

Commits

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 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 @​testing-library/react or @​testing-library/react-native

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.

... (truncated)

Commits
  • e137890 [string-refs] cleanup string ref code (#31443)
  • d1f0472 [string-refs] remove enableLogStringRefsProd flag (#31414)
  • 3dc1e48 Followup: remove dead test code from #30346 (#31415)
  • 07aa494 Remove enableRefAsProp feature flag (#30346)
  • 45804af [flow] Eliminate usage of more than 1-arg React.AbstractComponent in React ...
  • 5636fad [string-refs] log string ref from prod (#31161)
  • b78a7f2 [rcr] Re-export useMemoCache in top level React namespace (#31139)
  • 4e9540e [Fiber] Log the Render/Commit phases and the gaps in between (#31016)
  • d4688df [Fiber] Track Event Time, startTransition Time and setState Time (#31008)
  • 15da917 Don't read currentTransition back from internals (#30991)
  • Additional commits viewable in compare view

Updates @types/react from 18.3.10 to 19.0.2

Commits

Updates react-dom from 18.3.1 to 19.0.0

Release notes

Sourced from react-dom'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” ...

    Description has been truncated

@dependabot
build(deps): bump the package-updates group across 1 directory with 2…
67c18f3 
…2 updates

Bumps the package-updates group with 22 updates in the / directory:

| Package | From | To |
| --- | --- | --- |
| [@chakra-ui/react](https://github.com/chakra-ui/chakra-ui/tree/HEAD/packages/react) | `2.8.2` | `3.2.3` |
| [@emotion/react](https://github.com/emotion-js/emotion) | `11.13.3` | `11.14.0` |
| [@emotion/styled](https://github.com/emotion-js/emotion) | `11.13.0` | `11.14.0` |
| [@testing-library/jest-dom](https://github.com/testing-library/jest-dom) | `6.5.0` | `6.6.3` |
| [@testing-library/react](https://github.com/testing-library/react-testing-library) | `16.0.1` | `16.1.0` |
| [@types/jest](https://github.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/jest) | `29.5.13` | `29.5.14` |
| [@types/node](https://github.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/node) | `22.7.4` | `22.10.2` |
| [framer-motion](https://github.com/motiondivision/motion) | `11.9.0` | `11.15.0` |
| [markdown-to-jsx](https://github.com/quantizor/markdown-to-jsx) | `7.5.0` | `7.7.2` |
| [prettier](https://github.com/prettier/prettier) | `3.3.3` | `3.4.2` |
| [react](https://github.com/facebook/react/tree/HEAD/packages/react) | `18.3.1` | `19.0.0` |
| [@types/react](https://github.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/react) | `18.3.10` | `19.0.2` |
| [react-dom](https://github.com/facebook/react/tree/HEAD/packages/react-dom) | `18.3.1` | `19.0.0` |
| [@types/react-dom](https://github.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/react-dom) | `18.3.0` | `19.0.2` |
| [react-icons](https://github.com/react-icons/react-icons) | `5.3.0` | `5.4.0` |
| [react-router-dom](https://github.com/remix-run/react-router/tree/HEAD/packages/react-router-dom) | `6.26.2` | `7.1.1` |
| [react-syntax-highlighter](https://github.com/react-syntax-highlighter/react-syntax-highlighter) | `15.5.0` | `15.6.1` |
| [typescript](https://github.com/microsoft/TypeScript) | `5.6.2` | `5.7.2` |
| [web-vitals](https://github.com/GoogleChrome/web-vitals) | `4.2.3` | `4.2.4` |
| [yaml](https://github.com/eemeli/yaml) | `2.5.1` | `2.6.1` |
| [@vitejs/plugin-react](https://github.com/vitejs/vite-plugin-react/tree/HEAD/packages/plugin-react) | `4.3.2` | `4.3.4` |
| [vite](https://github.com/vitejs/vite/tree/HEAD/packages/vite) | `5.4.8` | `6.0.6` |



Updates `@chakra-ui/react` from 2.8.2 to 3.2.3
- [Release notes](https://github.com/chakra-ui/chakra-ui/releases)
- [Changelog](https://github.com/chakra-ui/chakra-ui/blob/main/packages/react/CHANGELOG.md)
- [Commits](https://github.com/chakra-ui/chakra-ui/commits/@chakra-ui/react@3.2.3/packages/react)

Updates `@emotion/react` from 11.13.3 to 11.14.0
- [Release notes](https://github.com/emotion-js/emotion/releases)
- [Changelog](https://github.com/emotion-js/emotion/blob/main/CHANGELOG.md)
- [Commits](https://github.com/emotion-js/emotion/compare/@emotion/react@11.13.3...@emotion/react@11.14.0)

Updates `@emotion/styled` from 11.13.0 to 11.14.0
- [Release notes](https://github.com/emotion-js/emotion/releases)
- [Changelog](https://github.com/emotion-js/emotion/blob/main/CHANGELOG.md)
- [Commits](https://github.com/emotion-js/emotion/compare/@emotion/styled@11.13.0...@emotion/styled@11.14.0)

Updates `@testing-library/jest-dom` from 6.5.0 to 6.6.3
- [Release notes](https://github.com/testing-library/jest-dom/releases)
- [Changelog](https://github.com/testing-library/jest-dom/blob/main/CHANGELOG.md)
- [Commits](testing-library/jest-dom@v6.5.0...v6.6.3)

Updates `@testing-library/react` from 16.0.1 to 16.1.0
- [Release notes](https://github.com/testing-library/react-testing-library/releases)
- [Changelog](https://github.com/testing-library/react-testing-library/blob/main/CHANGELOG.md)
- [Commits](testing-library/react-testing-library@v16.0.1...v16.1.0)

Updates `@types/jest` from 29.5.13 to 29.5.14
- [Release notes](https://github.com/DefinitelyTyped/DefinitelyTyped/releases)
- [Commits](https://github.com/DefinitelyTyped/DefinitelyTyped/commits/HEAD/types/jest)

Updates `@types/node` from 22.7.4 to 22.10.2
- [Release notes](https://github.com/DefinitelyTyped/DefinitelyTyped/releases)
- [Commits](https://github.com/DefinitelyTyped/DefinitelyTyped/commits/HEAD/types/node)

Updates `framer-motion` from 11.9.0 to 11.15.0
- [Changelog](https://github.com/motiondivision/motion/blob/main/CHANGELOG.md)
- [Commits](motiondivision/motion@v11.9.0...v11.15.0)

Updates `markdown-to-jsx` from 7.5.0 to 7.7.2
- [Release notes](https://github.com/quantizor/markdown-to-jsx/releases)
- [Changelog](https://github.com/quantizor/markdown-to-jsx/blob/main/CHANGELOG.md)
- [Commits](quantizor/markdown-to-jsx@v7.5.0...v7.7.2)

Updates `prettier` from 3.3.3 to 3.4.2
- [Release notes](https://github.com/prettier/prettier/releases)
- [Changelog](https://github.com/prettier/prettier/blob/main/CHANGELOG.md)
- [Commits](prettier/prettier@3.3.3...3.4.2)

Updates `react` from 18.3.1 to 19.0.0
- [Release notes](https://github.com/facebook/react/releases)
- [Changelog](https://github.com/facebook/react/blob/main/CHANGELOG.md)
- [Commits](https://github.com/facebook/react/commits/v19.0.0/packages/react)

Updates `@types/react` from 18.3.10 to 19.0.2
- [Release notes](https://github.com/DefinitelyTyped/DefinitelyTyped/releases)
- [Commits](https://github.com/DefinitelyTyped/DefinitelyTyped/commits/HEAD/types/react)

Updates `react-dom` from 18.3.1 to 19.0.0
- [Release notes](https://github.com/facebook/react/releases)
- [Changelog](https://github.com/facebook/react/blob/main/CHANGELOG.md)
- [Commits](https://github.com/facebook/react/commits/v19.0.0/packages/react-dom)

Updates `@types/react-dom` from 18.3.0 to 19.0.2
- [Release notes](https://github.com/DefinitelyTyped/DefinitelyTyped/releases)
- [Commits](https://github.com/DefinitelyTyped/DefinitelyTyped/commits/HEAD/types/react-dom)

Updates `react-icons` from 5.3.0 to 5.4.0
- [Release notes](https://github.com/react-icons/react-icons/releases)
- [Commits](react-icons/react-icons@v5.3.0...v5.4.0)

Updates `react-router-dom` from 6.26.2 to 7.1.1
- [Release notes](https://github.com/remix-run/react-router/releases)
- [Changelog](https://github.com/remix-run/react-router/blob/main/packages/react-router-dom/CHANGELOG.md)
- [Commits](https://github.com/remix-run/react-router/commits/react-router-dom@7.1.1/packages/react-router-dom)

Updates `react-syntax-highlighter` from 15.5.0 to 15.6.1
- [Release notes](https://github.com/react-syntax-highlighter/react-syntax-highlighter/releases)
- [Changelog](https://github.com/react-syntax-highlighter/react-syntax-highlighter/blob/master/CHANGELOG.MD)
- [Commits](react-syntax-highlighter/react-syntax-highlighter@15.5.0...v15.6.1)

Updates `typescript` from 5.6.2 to 5.7.2
- [Release notes](https://github.com/microsoft/TypeScript/releases)
- [Changelog](https://github.com/microsoft/TypeScript/blob/main/azure-pipelines.release.yml)
- [Commits](microsoft/TypeScript@v5.6.2...v5.7.2)

Updates `web-vitals` from 4.2.3 to 4.2.4
- [Changelog](https://github.com/GoogleChrome/web-vitals/blob/main/CHANGELOG.md)
- [Commits](GoogleChrome/web-vitals@v4.2.3...v4.2.4)

Updates `yaml` from 2.5.1 to 2.6.1
- [Release notes](https://github.com/eemeli/yaml/releases)
- [Commits](eemeli/yaml@v2.5.1...v2.6.1)

Updates `@vitejs/plugin-react` from 4.3.2 to 4.3.4
- [Release notes](https://github.com/vitejs/vite-plugin-react/releases)
- [Changelog](https://github.com/vitejs/vite-plugin-react/blob/main/packages/plugin-react/CHANGELOG.md)
- [Commits](https://github.com/vitejs/vite-plugin-react/commits/v4.3.4/packages/plugin-react)

Updates `vite` from 5.4.8 to 6.0.6
- [Release notes](https://github.com/vitejs/vite/releases)
- [Changelog](https://github.com/vitejs/vite/blob/main/packages/vite/CHANGELOG.md)
- [Commits](https://github.com/vitejs/vite/commits/v6.0.6/packages/vite)

---
updated-dependencies:
- dependency-name: "@chakra-ui/react"
  dependency-type: direct:production
  update-type: version-update:semver-major
  dependency-group: package-updates
- dependency-name: "@emotion/react"
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: package-updates
- dependency-name: "@emotion/styled"
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: package-updates
- dependency-name: "@testing-library/jest-dom"
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: package-updates
- dependency-name: "@testing-library/react"
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: package-updates
- dependency-name: "@types/jest"
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: package-updates
- dependency-name: "@types/node"
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: package-updates
- dependency-name: framer-motion
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: package-updates
- dependency-name: markdown-to-jsx
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: package-updates
- dependency-name: prettier
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: package-updates
- dependency-name: react
  dependency-type: direct:production
  update-type: version-update:semver-major
  dependency-group: package-updates
- dependency-name: "@types/react"
  dependency-type: direct:production
  update-type: version-update:semver-major
  dependency-group: package-updates
- dependency-name: react-dom
  dependency-type: direct:production
  update-type: version-update:semver-major
  dependency-group: package-updates
- dependency-name: "@types/react-dom"
  dependency-type: direct:production
  update-type: version-update:semver-major
  dependency-group: package-updates
- dependency-name: react-icons
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: package-updates
- dependency-name: react-router-dom
  dependency-type: direct:production
  update-type: version-update:semver-major
  dependency-group: package-updates
- dependency-name: react-syntax-highlighter
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: package-updates
- dependency-name: typescript
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: package-updates
- dependency-name: web-vitals
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: package-updates
- dependency-name: yaml
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: package-updates
- dependency-name: "@vitejs/plugin-react"
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: package-updates
- dependency-name: vite
  dependency-type: direct:development
  update-type: version-update:semver-major
  dependency-group: package-updates
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot requested a review from a team as a code owner December 30, 2024 02:16
@dependabot dependabot bot added the dependencies Pull requests that update a dependency file label Dec 30, 2024
@dependabot dependabot bot requested a review from zivkovicmilos December 30, 2024 02:16
@dependabot dependabot bot mentioned this pull request Dec 30, 2024
Closed
@netlify
Copy link

netlify bot commented Dec 30, 2024 •
edited
Loading

❌ Deploy Preview for gno-by-example failed. Why did it fail? →

Name Link
🔨 Latest commit 67c18f3
🔍 Latest deploy log https://app.netlify.com/sites/gno-by-example/deploys/67720294e72e3e0008c9c968

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@zivkovicmilos zivkovicmilos Awaiting requested review from zivkovicmilos

At least 1 approving review is required to merge this pull request.

Assignees

No one assigned

Labels

dependencies Pull requests that update a dependency file

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant