Skip to content

Bump the development-dependencies group across 1 directory with 11 updates #544

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
Merged
merged 1 commit into from
Apr 14, 2025
Merged

Bump the development-dependencies group across 1 directory with 11 updates #544

merged 1 commit into from
Apr 14, 2025

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Apr 14, 2025

Bumps the development-dependencies group with 11 updates in the / directory:

Package From To
@changesets/cli 2.28.1 2.29.0
@rollup/wasm-node 4.36.0 4.40.0
@testing-library/react 16.2.0 16.3.0
@types/node 22.13.10 22.14.1
esbuild 0.25.1 0.25.2
eslint-plugin-prettier 5.2.3 5.2.6
react 19.0.0 19.1.0
@types/react 19.0.11 19.1.2
react-dom 19.0.0 19.1.0
rollup 4.36.0 4.40.0
typescript 5.8.2 5.8.3

Updates @changesets/cli from 2.28.1 to 2.29.0

Release notes

Sourced from @​changesets/cli's releases.

@​changesets/cli@​2.29.0

Minor Changes

Commits

Updates @rollup/wasm-node from 4.36.0 to 4.40.0

Release notes

Sourced from @​rollup/wasm-node's releases.

v4.40.0

4.40.0

2025-04-12

Features

  • Only show eval warnings on first render and only when the call is not tree-shaken (#5892)
  • Tree-shake non-included dynamic import members when the handler just maps to one named export (#5898)

Bug Fixes

  • Consider dynamic imports nested within top-level-awaited dynamic import expressions to be awaited as well (#5900)
  • Fix namespace rendering when tree-shaking is disabled (#5908)
  • When using multiple transform hook filters, all of them need to be satisfied together (#5909)

Pull Requests

v4.39.0

4.39.0

2025-04-02

Features

  • Do not create separate facade chunks if a chunk would contain several entry modules that allow export extension if there are no export name conflicts (#5891)

Bug Fixes

  • Mark the id property as optional in the filter for the resolveId hook (#5896)

Pull Requests

v4.38.0

... (truncated)

Changelog

Sourced from @​rollup/wasm-node's changelog.

4.40.0

2025-04-12

Features

  • Only show eval warnings on first render and only when the call is not tree-shaken (#5892)
  • Tree-shake non-included dynamic import members when the handler just maps to one named export (#5898)

Bug Fixes

  • Consider dynamic imports nested within top-level-awaited dynamic import expressions to be awaited as well (#5900)
  • Fix namespace rendering when tree-shaking is disabled (#5908)
  • When using multiple transform hook filters, all of them need to be satisfied together (#5909)

Pull Requests

4.39.0

2025-04-02

Features

  • Do not create separate facade chunks if a chunk would contain several entry modules that allow export extension if there are no export name conflicts (#5891)

Bug Fixes

  • Mark the id property as optional in the filter for the resolveId hook (#5896)

Pull Requests

4.38.0

2025-03-29

... (truncated)

Commits
  • 1f2d579 4.40.0
  • cf0512f Fix release script
  • 4ded099 feat: treeshake dynamic import chained member expression (#5898)
  • 8bb7b6f chore(deps): lock file maintenance minor/patch updates (#5917)
  • 19fb519 consider the dynamic import within a TLA call expression as a TLA import (#5900)
  • aba2ea9 Fix treeshake: false breaking destructured namespace imports (#5908)
  • 02a060d Correct the behavior when multiple transform filter options are specified (#5...
  • 051a502 chore(deps): update dependency @​types/picomatch to v4 (#5915)
  • 7d7ae3f fix(deps): update rust crate swc_compiler_base to v17 (#5916)
  • 86e1ccd chore(deps): update dependency vite to v6.2.6 [security] (#5918)
  • Additional commits viewable in compare view

Updates @testing-library/react from 16.2.0 to 16.3.0

Release notes

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

v16.3.0

16.3.0 (2025-04-02)

Features

  • add bernardobelchior as a contributor for code, and doc (#1391) (9fc6a75)
Commits

Updates @types/node from 22.13.10 to 22.14.1

Commits

Updates esbuild from 0.25.1 to 0.25.2

Release notes

Sourced from esbuild's releases.

v0.25.2

  • Support flags in regular expressions for the API (#4121)

    The JavaScript plugin API for esbuild takes JavaScript regular expression objects for the filter option. Internally these are translated into Go regular expressions. However, this translation previously ignored the flags property of the regular expression. With this release, esbuild will now translate JavaScript regular expression flags into Go regular expression flags. Specifically the JavaScript regular expression /\.[jt]sx?$/i is turned into the Go regular expression `(?i)\.[jt]sx?$` internally inside of esbuild's API. This should make it possible to use JavaScript regular expressions with the i flag. Note that JavaScript and Go don't support all of the same regular expression features, so this mapping is only approximate.

  • Fix node-specific annotations for string literal export names (#4100)

    When node instantiates a CommonJS module, it scans the AST to look for names to expose via ESM named exports. This is a heuristic that looks for certain patterns such as exports.NAME = ... or module.exports = { ... }. This behavior is used by esbuild to "annotate" CommonJS code that was converted from ESM with the original ESM export names. For example, when converting the file export let foo, bar from ESM to CommonJS, esbuild appends this to the end of the file:

    // Annotate the CommonJS export names for ESM import in node:
0 && (module.exports = {
  bar,
  foo
});

    However, this feature previously didn't work correctly for export names that are not valid identifiers, which can be constructed using string literal export names. The generated code contained a syntax error. That problem is fixed in this release:

    // Original code
let foo
export { foo as "foo!" }
// Old output (with --format=cjs --platform=node)
...
0 && (module.exports = {
"foo!"
});
// New output (with --format=cjs --platform=node)
...
0 && (module.exports = {
"foo!": null
});

  • Basic support for index source maps (#3439, #4109)

    The source map specification has an optional mode called index source maps that makes it easier for tools to create an aggregate JavaScript file by concatenating many smaller JavaScript files with source maps, and then generate an aggregate source map by simply providing the original source maps along with some offset information. My understanding is that this is rarely used in practice. I'm only aware of two uses of it in the wild: ClojureScript and Turbopack.

    This release provides basic support for indexed source maps. However, the implementation has not been tested on a real app (just on very simple test input). If you are using index source maps in a real app, please try this out and report back if anything isn't working for you.

    Note that this is also not a complete implementation. For example, index source maps technically allows nesting source maps to an arbitrary depth, while esbuild's implementation in this release only supports a single level of nesting. It's unclear whether supporting more than one level of nesting is important or not given the lack of available test cases.

    This feature was contributed by @​clyfish.

Changelog

Sourced from esbuild's changelog.

0.25.2

  • Support flags in regular expressions for the API (#4121)

    The JavaScript plugin API for esbuild takes JavaScript regular expression objects for the filter option. Internally these are translated into Go regular expressions. However, this translation previously ignored the flags property of the regular expression. With this release, esbuild will now translate JavaScript regular expression flags into Go regular expression flags. Specifically the JavaScript regular expression /\.[jt]sx?$/i is turned into the Go regular expression `(?i)\.[jt]sx?$` internally inside of esbuild's API. This should make it possible to use JavaScript regular expressions with the i flag. Note that JavaScript and Go don't support all of the same regular expression features, so this mapping is only approximate.

  • Fix node-specific annotations for string literal export names (#4100)

    When node instantiates a CommonJS module, it scans the AST to look for names to expose via ESM named exports. This is a heuristic that looks for certain patterns such as exports.NAME = ... or module.exports = { ... }. This behavior is used by esbuild to "annotate" CommonJS code that was converted from ESM with the original ESM export names. For example, when converting the file export let foo, bar from ESM to CommonJS, esbuild appends this to the end of the file:

    // Annotate the CommonJS export names for ESM import in node:
0 && (module.exports = {
  bar,
  foo
});

    However, this feature previously didn't work correctly for export names that are not valid identifiers, which can be constructed using string literal export names. The generated code contained a syntax error. That problem is fixed in this release:

    // Original code
let foo
export { foo as "foo!" }
// Old output (with --format=cjs --platform=node)
...
0 && (module.exports = {
"foo!"
});
// New output (with --format=cjs --platform=node)
...
0 && (module.exports = {
"foo!": null
});

  • Basic support for index source maps (#3439, #4109)

    The source map specification has an optional mode called index source maps that makes it easier for tools to create an aggregate JavaScript file by concatenating many smaller JavaScript files with source maps, and then generate an aggregate source map by simply providing the original source maps along with some offset information. My understanding is that this is rarely used in practice. I'm only aware of two uses of it in the wild: ClojureScript and Turbopack.

    This release provides basic support for indexed source maps. However, the implementation has not been tested on a real app (just on very simple test input). If you are using index source maps in a real app, please try this out and report back if anything isn't working for you.

    Note that this is also not a complete implementation. For example, index source maps technically allows nesting source maps to an arbitrary depth, while esbuild's implementation in this release only supports a single level of nesting. It's unclear whether supporting more than one level of nesting is important or not given the lack of available test cases.

    This feature was contributed by @​clyfish.

Commits

Updates eslint-plugin-prettier from 5.2.3 to 5.2.6

Release notes

Sourced from eslint-plugin-prettier's releases.

v5.2.6

Patch Changes

v5.2.5

Patch Changes

v5.2.4

Patch Changes

Changelog

Sourced from eslint-plugin-prettier's changelog.

5.2.6

Patch Changes

5.2.5

Patch Changes

5.2.4

Patch Changes

Commits

Updates react from 19.0.0 to 19.1.0

Release notes

Sourced from react's releases.

19.1.0 (March 28, 2025)

Owner Stack

An Owner Stack is a string representing the components that are directly responsible for rendering a particular component. You can log Owner Stacks when debugging or use Owner Stacks to enhance error overlays or other development tools. Owner Stacks are only available in development builds. Component Stacks in production are unchanged.

  • An Owner Stack is a development-only stack trace that helps identify which components are responsible for rendering a particular component. An Owner Stack is distinct from a Component Stacks, which shows the hierarchy of components leading to an error.
  • The captureOwnerStack API is only available in development mode and returns a Owner Stack, if available. The API can be used to enhance error overlays or log component relationships when debugging. #29923, #32353, #30306, #32538, #32529, #32538

React

  • Enhanced support for Suspense boundaries to be used anywhere, including the client, server, and during hydration. #32069, #32163, #32224, #32252
  • Reduced unnecessary client rendering through improved hydration scheduling #31751
  • Increased priority of client rendered Suspense boundaries #31776
  • Fixed frozen fallback states by rendering unfinished Suspense boundaries on the client. #31620
  • Reduced garbage collection pressure by improving Suspense boundary retries. #31667
  • Fixed erroneous “Waiting for Paint” log when the passive effect phase was not delayed #31526
  • Fixed a regression causing key warnings for flattened positional children in development mode. #32117
  • Updated useId to use valid CSS selectors, changing format from :r123: to «r123». #32001
  • Added a dev-only warning for null/undefined created in useEffect, useInsertionEffect, and useLayoutEffect. #32355
  • Fixed a bug where dev-only methods were exported in production builds. React.act is no longer available in production builds. #32200
  • Improved consistency across prod and dev to improve compatibility with Google Closure Complier and bindings #31808
  • Improve passive effect scheduling for consistent task yielding. #31785
  • Fixed asserts in React Native when passChildrenWhenCloningPersistedNodes is enabled for OffscreenComponent rendering. #32528
  • Fixed component name resolution for Portal #32640
  • Added support for beforetoggle and toggle events on the dialog element. #32479 #32479

React DOM

  • Fixed double warning when the href attribute is an empty string #31783
  • Fixed an edge case where getHoistableRoot() didn’t work properly when the container was a Document #32321
  • Removed support for using HTML comments (e.g. <!-- -->) as a DOM container. #32250
  • Added support for <script> and \<template> tags to be nested within <select> tags. #31837
  • Fixed responsive images to be preloaded as HTML instead of headers #32445

use-sync-external-store

  • Added exports field to package.json for use-sync-external-store to support various entrypoints. #25231

React Server Components

  • Added unstable_prerender, a new experimental API for prerendering React Server Components on the server #31724
  • Fixed an issue where streams would hang when receiving new chunks after a global error #31840, #31851
  • Fixed an issue where pending chunks were counted twice. #31833
  • Added support for streaming in edge environments #31852
  • Added support for sending custom error names from a server so that they are available in the client for console replaying. #32116
  • Updated the server component wire format to remove IDs for hints and console.log because they have no return value #31671
  • Exposed registerServerReference in client builds to handle server references in different environments. #32534
  • Added react-server-dom-parcel package which integrates Server Components with the Parcel bundler #31725, #32132, #31799, #32294, #31741
Changelog

Sourced from react's changelog.

19.1.0 (March 28, 2025)

Owner Stack

An Owner Stack is a string representing the components that are directly responsible for rendering a particular component. You can log Owner Stacks when debugging or use Owner Stacks to enhance error overlays or other development tools. Owner Stacks are only available in development builds. Component Stacks in production are unchanged.

  • An Owner Stack is a development-only stack trace that helps identify which components are responsible for rendering a particular component. An Owner Stack is distinct from a Component Stacks, which shows the hierarchy of components leading to an error.
  • The captureOwnerStack API is only available in development mode and returns a Owner Stack, if available. The API can be used to enhance error overlays or log component relationships when debugging. #29923, #32353, #30306, #32538, #32529, #32538

React

  • Enhanced support for Suspense boundaries to be used anywhere, including the client, server, and during hydration. #32069, #32163, #32224, #32252
  • Reduced unnecessary client rendering through improved hydration scheduling #31751
  • Increased priority of client rendered Suspense boundaries #31776
  • Fixed frozen fallback states by rendering unfinished Suspense boundaries on the client. #31620
  • Reduced garbage collection pressure by improving Suspense boundary retries. #31667
  • Fixed erroneous “Waiting for Paint” log when the passive effect phase was not delayed #31526
  • Fixed a regression causing key warnings for flattened positional children in development mode. #32117
  • Updated useId to use valid CSS selectors, changing format from :r123: to «r123». #32001
  • Added a dev-only warning for null/undefined created in useEffect, useInsertionEffect, and useLayoutEffect. #32355
  • Fixed a bug where dev-only methods were exported in production builds. React.act is no longer available in production builds. #32200
  • Improved consistency across prod and dev to improve compatibility with Google Closure Complier and bindings #31808
  • Improve passive effect scheduling for consistent task yielding. #31785
  • Fixed asserts in React Native when passChildrenWhenCloningPersistedNodes is enabled for OffscreenComponent rendering. #32528
  • Fixed component name resolution for Portal #32640
  • Added support for beforetoggle and toggle events on the dialog element. #32479 #32479

React DOM

  • Fixed double warning when the href attribute is an empty string #31783
  • Fixed an edge case where getHoistableRoot() didn’t work properly when the container was a Document #32321
  • Removed support for using HTML comments (e.g. <!-- -->) as a DOM container. #32250
  • Added support for <script> and \<template> tags to be nested within <select> tags. #31837
  • Fixed responsive images to be preloaded as HTML instead of headers #32445

use-sync-external-store

  • Added exports field to package.json for use-sync-external-store to support various entrypoints. #25231

React Server Components

  • Added unstable_prerender, a new experimental API for prerendering React Server Components on the server #31724
  • Fixed an issue where streams would hang when receiving new chunks after a global error #31840, #31851
  • Fixed an issue where pending chunks were counted twice. #31833
  • Added support for streaming in edge environments #31852
  • Added support for sending custom error names from a server so that they are available in the client for console replaying. #32116
  • Updated the server component wire format to remove IDs for hints and console.log because they have no return value #31671
  • Exposed registerServerReference in client builds to handle server references in different environments. #32534
  • Added react-server-dom-parcel package which integrates Server Components with the Parcel bundler #31725, #32132, #31799, #32294, #31741
Commits

Updates @types/react from 19.0.11 to 19.1.2

Commits

Updates react-dom from 19.0.0 to 19.1.0

Release notes

Sourced from react-dom's releases.

19.1.0 (March 28, 2025)

Owner Stack

An Owner Stack is a string representing the components that are directly responsible for rendering a particular component. You can log Owner Stacks when debugging or use Owner Stacks to enhance error overlays or other development tools. Owner Stacks are only available in development builds. Component Stacks in production are unchanged.

  • An Owner Stack is a development-only stack trace that helps identify which components are responsible for rendering a particular component. An Owner Stack is distinct from a Component Stacks, which shows the hierarchy of components leading to an error.
  • The captureOwnerStack API is only available in development mode and returns a Owner Stack, if available. The API can be used to enhance error overlays or log component relationships when debugging. #29923, #32353, #30306, #32538, #32529, #32538

React

  • Enhanced support for Suspense boundaries to be used anywhere, including the client, server, and during hydration. #32069, #32163, #32224, #32252
  • Reduced unnecessary client rendering through improved hydration scheduling #31751
  • Increased priority of client rendered Suspense boundaries #31776
  • Fixed frozen fallback states by rendering unfinished Suspense boundaries on the client. #31620
  • Reduced garbage collection pressure by improving Suspense boundary retries. #31667
  • Fixed erroneous “Waiting for Paint” log when the passive effect phase was not delayed #31526
  • Fixed a regression causing key warnings for flattened positional children in development mode. #32117
  • Updated useId to use valid CSS selectors, changing format from :r123: to «r123». #32001
  • Added a dev-only warning for null/undefined created in useEffect, useInsertionEffect, and useLayoutEffect. #32355
  • Fixed a bug where dev-only methods were exported in production builds. React.act is no longer available in production builds. #32200
  • Improved consistency across prod and dev to improve compatibility with Google Closure Complier and bindings #31808
  • Improve passive effect scheduling for consistent task yielding. #31785
  • Fixed asserts in React Native when passChildrenWhenCloningPersistedNodes is enabled for OffscreenComponent rendering. #32528
  • Fixed component name resolution for Portal #32640
  • Added support for beforetoggle and toggle events on the dialog element. #32479 #32479

React DOM

  • Fixed double warning when the href attribute is an empty string #31783
  • Fixed an edge case where getHoistableRoot() didn’t work properly when the container was a Document #32321
  • Removed support for using HTML comments (e.g. <!-- -->) as a DOM container. #32250
  • Added support for <script> and \<template> tags to be nested within <select> tags. #31837
  • Fixed responsive images to be preloaded as HTML instead of headers #32445

use-sync-external-store

  • Added exports field to package.json for use-sync-external-store to support various entrypoints. #25231

React Server Components

  • Added unstable_prerender, a new experimental API for prerendering React Server Components on the server #31724
  • Fixed an issue where streams would hang when receiving new chunks after a global error #31840, #31851
  • Fixed an issue where pending chunks were counted twice. #31833
  • Added support for streaming in edge environments #31852
  • Added support for sending custom error names from a server so that they are available in the client for console replaying. #32116
  • Updated the server component wire format to remove IDs for hints and console.log because they have no return value #31671
  • Exposed registerServerReference in client builds to handle server references in different environments. #32534
  • Added react-server-dom-parcel package which integrates Server Components with the Parcel bundler #31725, #32132, #31799, #32294, #31741
Changelog

Sourced from react-dom's changelog.

19.1.0 (March 28, 2025)

Owner Stack

An Owner Stack is a string representing the components that are directly responsible for rendering a particular component. You can log Owner Stacks when debugging or use Owner Stacks to enhance error overlays or other development tools. Owner Stacks are only available in development builds. Component Stacks in production are unchanged.

  • An Owner Stack is a development-only stack trace that helps identify which components are responsible for rendering a particular component. An Owner Stack is distinct from a Component Stacks, which shows the hierarchy of components leading to an error.
  • The captureOwnerStack API is only available in development mode and returns a Owner Stack, if available. The API can be used to enhance error overlays or log component relationships when debugging. #29923, #32353, #30306, #32538, #32529, #32538

React

  • Enhanced support for Suspense boundaries to be used anywhere, including the client, server, and during hydration. #32069, #32163, #32224, #32252
  • Reduced unnecessary client rendering through improved hydration scheduling #31751
  • Increased priority of client rendered Suspense boundaries #31776
  • Fixed frozen fallback states by rendering unfinished Suspense boundaries on the client. #31620
  • Reduced garbage collection pressure by improving Suspense boundary retries. #31667
  • Fixed erroneous “Waiting for Paint” log when the passive effect phase was not delayed #31526
  • Fixed a regression causing key warnings for flattened positional children in development mode. #32117
  • Updated useId to use valid CSS selectors, changing format from :r123: to «r123». #32001
  • Added a dev-only warning for null/undefined created in useEffect, useInsertionEffect, and useLayoutEffect. #32355
  • Fixed a bug where dev-only methods were exported in production builds. React.act is no longer available in production builds. #32200
  • Improved consistency across prod and dev to improve compatibility with Google Closure Complier and bindings #31808
  • Improve passive effect scheduling for consistent task yielding. #31785
  • Fixed asserts in React Native when passChildrenWhenCloningPersistedNodes is enabled for OffscreenComponent rendering. #32528
  • Fixed component name resolution for Portal #32640
  • Added support for beforetoggle and toggle events on the dialog element. #32479 #32479

React DOM

  • Fixed double warning when the href attribute is an empty string #31783
  • Fixed an edge case where getHoistableRoot() didn’t work properly when the container was a Document #32321
  • Removed support for using HTML comments (e.g. <!-- -->) as a DOM container. #32250<...

    Description has been truncated

@dependabot
Bump the development-dependencies group across 1 directory with 11 up…
204fd24 
…dates

Bumps the development-dependencies group with 11 updates in the / directory:

| Package | From | To |
| --- | --- | --- |
| [@changesets/cli](https://github.com/changesets/changesets) | `2.28.1` | `2.29.0` |
| [@rollup/wasm-node](https://github.com/rollup/rollup) | `4.36.0` | `4.40.0` |
| [@testing-library/react](https://github.com/testing-library/react-testing-library) | `16.2.0` | `16.3.0` |
| [@types/node](https://github.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/node) | `22.13.10` | `22.14.1` |
| [esbuild](https://github.com/evanw/esbuild) | `0.25.1` | `0.25.2` |
| [eslint-plugin-prettier](https://github.com/prettier/eslint-plugin-prettier) | `5.2.3` | `5.2.6` |
| [react](https://github.com/facebook/react/tree/HEAD/packages/react) | `19.0.0` | `19.1.0` |
| [@types/react](https://github.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/react) | `19.0.11` | `19.1.2` |
| [react-dom](https://github.com/facebook/react/tree/HEAD/packages/react-dom) | `19.0.0` | `19.1.0` |
| [rollup](https://github.com/rollup/rollup) | `4.36.0` | `4.40.0` |
| [typescript](https://github.com/microsoft/TypeScript) | `5.8.2` | `5.8.3` |



Updates `@changesets/cli` from 2.28.1 to 2.29.0
- [Release notes](https://github.com/changesets/changesets/releases)
- [Changelog](https://github.com/changesets/changesets/blob/main/docs/modifying-changelog-format.md)
- [Commits](https://github.com/changesets/changesets/compare/@changesets/[email protected]...@changesets/[email protected])

Updates `@rollup/wasm-node` from 4.36.0 to 4.40.0
- [Release notes](https://github.com/rollup/rollup/releases)
- [Changelog](https://github.com/rollup/rollup/blob/master/CHANGELOG.md)
- [Commits](rollup/rollup@v4.36.0...v4.40.0)

Updates `@testing-library/react` from 16.2.0 to 16.3.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.2.0...v16.3.0)

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

Updates `esbuild` from 0.25.1 to 0.25.2
- [Release notes](https://github.com/evanw/esbuild/releases)
- [Changelog](https://github.com/evanw/esbuild/blob/main/CHANGELOG.md)
- [Commits](evanw/esbuild@v0.25.1...v0.25.2)

Updates `eslint-plugin-prettier` from 5.2.3 to 5.2.6
- [Release notes](https://github.com/prettier/eslint-plugin-prettier/releases)
- [Changelog](https://github.com/prettier/eslint-plugin-prettier/blob/main/CHANGELOG.md)
- [Commits](prettier/eslint-plugin-prettier@v5.2.3...v5.2.6)

Updates `react` from 19.0.0 to 19.1.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.1.0/packages/react)

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

Updates `react-dom` from 19.0.0 to 19.1.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.1.0/packages/react-dom)

Updates `rollup` from 4.36.0 to 4.40.0
- [Release notes](https://github.com/rollup/rollup/releases)
- [Changelog](https://github.com/rollup/rollup/blob/master/CHANGELOG.md)
- [Commits](rollup/rollup@v4.36.0...v4.40.0)

Updates `typescript` from 5.8.2 to 5.8.3
- [Release notes](https://github.com/microsoft/TypeScript/releases)
- [Changelog](https://github.com/microsoft/TypeScript/blob/main/azure-pipelines.release-publish.yml)
- [Commits](microsoft/TypeScript@v5.8.2...v5.8.3)

---
updated-dependencies:
- dependency-name: "@changesets/cli"
  dependency-version: 2.29.0
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: development-dependencies
- dependency-name: "@rollup/wasm-node"
  dependency-version: 4.40.0
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: development-dependencies
- dependency-name: "@testing-library/react"
  dependency-version: 16.3.0
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: development-dependencies
- dependency-name: "@types/node"
  dependency-version: 22.14.1
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: development-dependencies
- dependency-name: esbuild
  dependency-version: 0.25.2
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: development-dependencies
- dependency-name: eslint-plugin-prettier
  dependency-version: 5.2.6
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: development-dependencies
- dependency-name: react
  dependency-version: 19.1.0
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: development-dependencies
- dependency-name: "@types/react"
  dependency-version: 19.1.2
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: development-dependencies
- dependency-name: react-dom
  dependency-version: 19.1.0
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: development-dependencies
- dependency-name: rollup
  dependency-version: 4.40.0
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: development-dependencies
- dependency-name: typescript
  dependency-version: 5.8.3
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: development-dependencies
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot added the dependencies Pull requests that update a dependency file label Apr 14, 2025
@dependabot dependabot bot requested a review from a team as a code owner April 14, 2025 23:03
@dependabot dependabot bot added the skip changeset Skip the check for changesets label Apr 14, 2025
@dependabot dependabot bot requested a review from hectahertz April 14, 2025 23:03
@changeset-bot changeset-bot
Copy link

changeset-bot bot commented Apr 14, 2025

⚠️ No Changeset found

Latest commit: 204fd24

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@francinelucca francinelucca merged commit a404bf4 into main Apr 14, 2025
11 checks passed
@francinelucca francinelucca deleted the dependabot/npm_and_yarn/development-dependencies-30e09205e9 branch April 14, 2025 23:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@francinelucca francinelucca francinelucca approved these changes

@hectahertz hectahertz Awaiting requested review from hectahertz hectahertz is a code owner automatically assigned from primer/engineer-reviewers

Assignees
No one assigned
Labels
dependencies Pull requests that update a dependency file skip changeset Skip the check for changesets
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
1 participant
@francinelucca