chore(deps): bump the kitchen-sink group in /examples/kitchen-sink with 8 updates (#9809)

Bumps the kitchen-sink group in /examples/kitchen-sink with 8 updates:

| Package | From | To |
| --- | --- | --- |
| [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.18` | `19.0.8` |
|
[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.5` | `19.0.3` |
| [vite](https://github.com/vitejs/vite/tree/HEAD/packages/vite) |
`5.4.14` | `6.0.11` |
|
[@types/express](https://github.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/express)
| `4.17.21` | `5.0.0` |
| [tsup](https://github.com/egoist/tsup) | `8.3.5` | `8.3.6` |
|
[vite-tsconfig-paths](https://github.com/aleclarson/vite-tsconfig-paths)
| `4.3.2` | `5.1.4` |

Updates `react` from 18.3.1 to 19.0.0
<details>
<summary>Release notes</summary>
<p><em>Sourced from <a
href="https://github.com/facebook/react/releases">react's
releases</a>.</em></p>
<blockquote>
<h2>19.0.0 (December 5, 2024)</h2>
<p>Below is a list of all new features, APIs, deprecations, and breaking
changes. Read <a href="https://react.dev/blog/2024/04/25/react-19">React
19 release post</a> and <a
href="https://react.dev/blog/2024/04/25/react-19-upgrade-guide">React 19
upgrade guide</a> for more information.</p>
<blockquote>
<p>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.</p>
</blockquote>
<h2>New Features</h2>
<h3>React</h3>
<ul>
<li>Actions: <code>startTransition</code> can now accept async
functions. Functions passed to <code>startTransition</code> 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 <code>fetch()</code> in the pending state,
and provides support for error handling, and optimistic updates.</li>
<li><code>useActionState</code>: 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 <code>action</code> prop to support
progressive enhancement in forms.</li>
<li><code>useOptimistic</code>: 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.</li>
<li><code>use</code>: is a new API that allows reading resources in
render. In React 19, <code>use</code> accepts a promise or Context. If
provided a promise, <code>use</code> will suspend until a value is
resolved. <code>use</code> can only be used in render but can be called
conditionally.</li>
<li><code>ref</code> as a prop: Refs can now be used as props, removing
the need for <code>forwardRef</code>.</li>
<li><strong>Suspense sibling pre-warming</strong>: 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.</li>
</ul>
<h3>React DOM Client</h3>
<ul>
<li><code>&lt;form&gt; action</code> prop: Form Actions allow you to
manage forms automatically and integrate with
<code>useFormStatus</code>. When a <code>&lt;form&gt; action</code>
succeeds, React will automatically reset the form for uncontrolled
components. The form can be reset manually with the new
<code>requestFormReset</code> API.</li>
<li><code>&lt;button&gt; and &lt;input&gt; formAction</code> prop:
Actions can be passed to the <code>formAction</code> prop to configure
form submission behavior. This allows using different Actions depending
on the input.</li>
<li><code>useFormStatus</code>: is a new hook that provides the status
of the parent <code>&lt;form&gt; action</code>, as if the form was a
Context provider. The hook returns the values: <code>pending</code>,
<code>data</code>, <code>method</code>, and <code>action</code>.</li>
<li>Support for Document Metadata: We’ve added support for rendering
document metadata tags in components natively. React will automatically
hoist them into the <code>&lt;head&gt;</code> section of the
document.</li>
<li>Support for Stylesheets: React 19 will ensure stylesheets are
inserted into the <code>&lt;head&gt;</code> on the client before
revealing the content of a Suspense boundary that depends on that
stylesheet.</li>
<li>Support for async scripts: Async scripts can be rendered anywhere in
the component tree and React will handle ordering and
deduplication.</li>
<li>Support for preloading resources: React 19 ships with
<code>preinit</code>, <code>preload</code>, <code>prefetchDNS</code>,
and <code>preconnect</code> 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.</li>
</ul>
<h3>React DOM Server</h3>
<ul>
<li>Added <code>prerender</code> and <code>prerenderToNodeStream</code>
APIs for static site generation. They are designed to work with
streaming environments like Node.js Streams and Web Streams. Unlike
<code>renderToString</code>, they wait for data to load for HTML
generation.</li>
</ul>
<h3>React Server Components</h3>
<ul>
<li>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 <a
href="https://19.react.dev/reference/rsc/server-components">docs</a> for
how to support React Server Components.</li>
</ul>
<h2>Deprecations</h2>
<ul>
<li>Deprecated: <code>element.ref</code> access: React 19 supports ref
as a prop, so we’re deprecating <code>element.ref</code> in favor of
<code>element.props.ref</code>. Accessing will result in a warning.</li>
<li><code>react-test-renderer</code>: 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 <a
href="https://github.com/testinglibrary"><code>@​testinglibrary</code></a>.com/docs/react-testing-library/intro/)
or <a
href="https://github.com/testingesting-library"><code>@​testingesting-library</code></a>.com/docs/react-native-testing-library/intro)</li>
</ul>
<h2>Breaking Changes</h2>
<p>React 19 brings in a number of breaking changes, including the
removals of long-deprecated APIs. We recommend first upgrading to
<code>18.3.1</code>, where we've added additional deprecation warnings.
Check out the <a
href="https://19.react.dev/blog/2024/04/25/react-19-upgrade-guide">upgrade
guide</a> for more details and guidance on codemodding.</p>
<h3>React</h3>
<ul>
<li>New JSX Transform is now required: We introduced <a
href="https://legacy.reactjs.org/blog/2020/09/22/introducing-the-new-jsx-transform.html">a
new JSX transform</a> 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.</li>
<li>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 <code>onUncaughtError</code> and <code>onCaughtError</code>
methods to <code>createRoot</code> and <code>hydrateRoot</code> to
customize this error handling.</li>
<li>Removed: <code>propTypes</code>: Using <code>propTypes</code> will
now be silently ignored. If required, we recommend migrating to
TypeScript or another type-checking solution.</li>
<li>Removed: <code>defaultProps</code> for functions: ES6 default
parameters can be used in place. Class components continue to support
<code>defaultProps</code> since there is no ES6 alternative.</li>
<li>Removed: <code>contextTypes</code> and <code>getChildContext</code>:
Legacy Context for class components has been removed in favor of the
<code>contextType</code> API.</li>
</ul>
<!-- raw HTML omitted -->
</blockquote>
<p>... (truncated)</p>
</details>
<details>
<summary>Changelog</summary>
<p><em>Sourced from <a
href="https://github.com/facebook/react/blob/main/CHANGELOG.md">react's
changelog</a>.</em></p>
<blockquote>
<h2>19.0.0 (December 5, 2024)</h2>
<p>Below is a list of all new features, APIs, deprecations, and breaking
changes. Read <a href="https://react.dev/blog/2024/04/25/react-19">React
19 release post</a> and <a
href="https://react.dev/blog/2024/04/25/react-19-upgrade-guide">React 19
upgrade guide</a> for more information.</p>
<blockquote>
<p>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.</p>
</blockquote>
<h3>New Features</h3>
<h4>React</h4>
<ul>
<li>Actions: <code>startTransition</code> can now accept async
functions. Functions passed to <code>startTransition</code> 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 <code>fetch()</code> in the pending state,
and provides support for error handling, and optimistic updates.</li>
<li><code>useActionState</code>: 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 <code>action</code> prop to support
progressive enhancement in forms.</li>
<li><code>useOptimistic</code>: 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.</li>
<li><code>use</code>: is a new API that allows reading resources in
render. In React 19, <code>use</code> accepts a promise or Context. If
provided a promise, <code>use</code> will suspend until a value is
resolved. <code>use</code> can only be used in render but can be called
conditionally.</li>
<li><code>ref</code> as a prop: Refs can now be used as props, removing
the need for <code>forwardRef</code>.</li>
<li><strong>Suspense sibling pre-warming</strong>: 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.</li>
</ul>
<h4>React DOM Client</h4>
<ul>
<li><code>&lt;form&gt; action</code> prop: Form Actions allow you to
manage forms automatically and integrate with
<code>useFormStatus</code>. When a <code>&lt;form&gt; action</code>
succeeds, React will automatically reset the form for uncontrolled
components. The form can be reset manually with the new
<code>requestFormReset</code> API.</li>
<li><code>&lt;button&gt; and &lt;input&gt; formAction</code> prop:
Actions can be passed to the <code>formAction</code> prop to configure
form submission behavior. This allows using different Actions depending
on the input.</li>
<li><code>useFormStatus</code>: is a new hook that provides the status
of the parent <code>&lt;form&gt; action</code>, as if the form was a
Context provider. The hook returns the values: <code>pending</code>,
<code>data</code>, <code>method</code>, and <code>action</code>.</li>
<li>Support for Document Metadata: We’ve added support for rendering
document metadata tags in components natively. React will automatically
hoist them into the <code>&lt;head&gt;</code> section of the
document.</li>
<li>Support for Stylesheets: React 19 will ensure stylesheets are
inserted into the <code>&lt;head&gt;</code> on the client before
revealing the content of a Suspense boundary that depends on that
stylesheet.</li>
<li>Support for async scripts: Async scripts can be rendered anywhere in
the component tree and React will handle ordering and
deduplication.</li>
<li>Support for preloading resources: React 19 ships with
<code>preinit</code>, <code>preload</code>, <code>prefetchDNS</code>,
and <code>preconnect</code> 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.</li>
</ul>
<h4>React DOM Server</h4>
<ul>
<li>Added <code>prerender</code> and <code>prerenderToNodeStream</code>
APIs for static site generation. They are designed to work with
streaming environments like Node.js Streams and Web Streams. Unlike
<code>renderToString</code>, they wait for data to load for HTML
generation.</li>
</ul>
<h4>React Server Components</h4>
<ul>
<li>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 <a
href="https://19.react.dev/reference/rsc/server-components">docs</a> for
how to support React Server Components.</li>
</ul>
<h3>Deprecations</h3>
<ul>
<li>Deprecated: <code>element.ref</code> access: React 19 supports ref
as a prop, so we’re deprecating <code>element.ref</code> in favor of
<code>element.props.ref</code>. Accessing will result in a warning.</li>
<li><code>react-test-renderer</code>: 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 <a
href="https://testing-library.com/docs/react-testing-library/intro/"><code>@​testing-library/react</code></a>
or <a
href="https://testing-library.com/docs/react-native-testing-library/intro"><code>@​testing-library/react-native</code></a></li>
</ul>
<h3>Breaking Changes</h3>
<p>React 19 brings in a number of breaking changes, including the
removals of long-deprecated APIs. We recommend first upgrading to
<code>18.3.1</code>, where we've added additional deprecation warnings.
Check out the <a
href="https://19.react.dev/blog/2024/04/25/react-19-upgrade-guide">upgrade
guide</a> for more details and guidance on codemodding.</p>
<h3>React</h3>
<ul>
<li>New JSX Transform is now required: We introduced <a
href="https://legacy.reactjs.org/blog/2020/09/22/introducing-the-new-jsx-transform.html">a
new JSX transform</a> 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.</li>
<li>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 <code>onUncaughtError</code> and <code>onCaughtError</code>
methods to <code>createRoot</code> and <code>hydrateRoot</code> to
customize this error handling.</li>
<li>Removed: <code>propTypes</code>: Using <code>propTypes</code> will
now be silently ignored. If required, we recommend migrating to
TypeScript or another type-checking solution.</li>
<li>Removed: <code>defaultProps</code> for functions: ES6 default
parameters can be used in place. Class components continue to support
<code>defaultProps</code> since there is no ES6 alternative.</li>
</ul>
<!-- raw HTML omitted -->
</blockquote>
<p>... (truncated)</p>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a
href="https://github.com/facebook/react/commit/e1378902bbb322aa1fe1953780f4b2b5f80d26b1"><code>e137890</code></a>
[string-refs] cleanup string ref code (<a
href="https://github.com/facebook/react/tree/HEAD/packages/react/issues/31443">#31443</a>)</li>
<li><a
href="https://github.com/facebook/react/commit/d1f04722d617600cc6cd96dcebc1c2ef7affc904"><code>d1f0472</code></a>
[string-refs] remove enableLogStringRefsProd flag (<a
href="https://github.com/facebook/react/tree/HEAD/packages/react/issues/31414">#31414</a>)</li>
<li><a
href="https://github.com/facebook/react/commit/3dc1e4820ec985baa6668a4fa799760c4b99f5d9"><code>3dc1e48</code></a>
Followup: remove dead test code from <a
href="https://github.com/facebook/react/tree/HEAD/packages/react/issues/30346">#30346</a>
(<a
href="https://github.com/facebook/react/tree/HEAD/packages/react/issues/31415">#31415</a>)</li>
<li><a
href="https://github.com/facebook/react/commit/07aa494432e97f63fca9faf2fad6f76fead31063"><code>07aa494</code></a>
Remove enableRefAsProp feature flag (<a
href="https://github.com/facebook/react/tree/HEAD/packages/react/issues/30346">#30346</a>)</li>
<li><a
href="https://github.com/facebook/react/commit/45804af18d589fd2c181f3b020f07661c46b73ea"><code>45804af</code></a>
[flow] Eliminate usage of more than 1-arg
<code>React.AbstractComponent</code> in React ...</li>
<li><a
href="https://github.com/facebook/react/commit/5636fad840942cfea80301d91e931a50c6370d19"><code>5636fad</code></a>
[string-refs] log string ref from prod (<a
href="https://github.com/facebook/react/tree/HEAD/packages/react/issues/31161">#31161</a>)</li>
<li><a
href="https://github.com/facebook/react/commit/b78a7f2f35e554a8647c3262d7f392e68d06febc"><code>b78a7f2</code></a>
[rcr] Re-export useMemoCache in top level React namespace (<a
href="https://github.com/facebook/react/tree/HEAD/packages/react/issues/31139">#31139</a>)</li>
<li><a
href="https://github.com/facebook/react/commit/4e9540e3c2a8f9ae56318b967939c99b3a815190"><code>4e9540e</code></a>
[Fiber] Log the Render/Commit phases and the gaps in between (<a
href="https://github.com/facebook/react/tree/HEAD/packages/react/issues/31016">#31016</a>)</li>
<li><a
href="https://github.com/facebook/react/commit/d4688dfaafe51a4cb6e3c51fc2330662cb4e2296"><code>d4688df</code></a>
[Fiber] Track Event Time, startTransition Time and setState Time (<a
href="https://github.com/facebook/react/tree/HEAD/packages/react/issues/31008">#31008</a>)</li>
<li><a
href="https://github.com/facebook/react/commit/15da9174518f18f82869767ebe2a21be2fc8bd90"><code>15da917</code></a>
Don't read currentTransition back from internals (<a
href="https://github.com/facebook/react/tree/HEAD/packages/react/issues/30991">#30991</a>)</li>
<li>Additional commits viewable in <a
href="https://github.com/facebook/react/commits/v19.0.0/packages/react">compare
view</a></li>
</ul>
</details>
<br />

Updates `@types/react` from 18.3.18 to 19.0.8
<details>
<summary>Commits</summary>
<ul>
<li>See full diff in <a
href="https://github.com/DefinitelyTyped/DefinitelyTyped/commits/HEAD/types/react">compare
view</a></li>
</ul>
</details>
<br />

Updates `react-dom` from 18.3.1 to 19.0.0
<details>
<summary>Release notes</summary>
<p><em>Sourced from <a
href="https://github.com/facebook/react/releases">react-dom's
releases</a>.</em></p>
<blockquote>
<h2>19.0.0 (December 5, 2024)</h2>
<p>Below is a list of all new features, APIs, deprecations, and breaking
changes. Read <a href="https://react.dev/blog/2024/04/25/react-19">React
19 release post</a> and <a
href="https://react.dev/blog/2024/04/25/react-19-upgrade-guide">React 19
upgrade guide</a> for more information.</p>
<blockquote>
<p>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.</p>
</blockquote>
<h2>New Features</h2>
<h3>React</h3>
<ul>
<li>Actions: <code>startTransition</code> can now accept async
functions. Functions passed to <code>startTransition</code> 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 <code>fetch()</code> in the pending state,
and provides support for error handling, and optimistic updates.</li>
<li><code>useActionState</code>: 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 <code>action</code> prop to support
progressive enhancement in forms.</li>
<li><code>useOptimistic</code>: 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.</li>
<li><code>use</code>: is a new API that allows reading resources in
render. In React 19, <code>use</code> accepts a promise or Context. If
provided a promise, <code>use</code> will suspend until a value is
resolved. <code>use</code> can only be used in render but can be called
conditionally.</li>
<li><code>ref</code> as a prop: Refs can now be used as props, removing
the need for <code>forwardRef</code>.</li>
<li><strong>Suspense sibling pre-warming</strong>: 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.</li>
</ul>
<h3>React DOM Client</h3>
<ul>
<li><code>&lt;form&gt; action</code> prop: Form Actions allow you to
manage forms automatically and integrate with
<code>useFormStatus</code>. When a <code>&lt;form&gt; action</code>
succeeds, React will automatically reset the form for uncontrolled
components. The form can be reset manually with the new
<code>requestFormReset</code> API.</li>
<li><code>&lt;button&gt; and &lt;input&gt; formAction</code> prop:
Actions can be passed to the <code>formAction</code> prop to configure
form submission behavior. This allows using different Actions depending
on the input.</li>
<li><code>useFormStatus</code>: is a new hook that provides the status
of the parent <code>&lt;form&gt; action</code>, as if the form was a
Context provider. The hook returns the values: <code>pending</code>,
<code>data</code>, <code>method</code>, and <code>action</code>.</li>
<li>Support for Document Metadata: We’ve added support for rendering
document metadata tags in components natively. React will automatically
hoist them into the <code>&lt;head&gt;</code> section of the
document.</li>
<li>Support for Stylesheets: React 19 will ensure stylesheets are
inserted into the <code>&lt;head&gt;</code> on the client before
revealing the content of a Suspense boundary that depends on that
stylesheet.</li>
<li>Support for async scripts: Async scripts can be rendered anywhere in
the component tree and React will handle ordering and
deduplication.</li>
<li>Support for preloading resources: React 19 ships with
<code>preinit</code>, <code>preload</code>, <code>prefetchDNS</code>,
and <code>preconnect</code> 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.</li>
</ul>
<h3>React DOM Server</h3>
<ul>
<li>Added <code>prerender</code> and <code>prerenderToNodeStream</code>
APIs for static site generation. They are designed to work with
streaming environments like Node.js Streams and Web Streams. Unlike
<code>renderToString</code>, they wait for data to load for HTML
generation.</li>
</ul>
<h3>React Server Components</h3>
<ul>
<li>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 <a
href="https://19.react.dev/reference/rsc/server-components">docs</a> for
how to support React Server Components.</li>
</ul>
<h2>Deprecations</h2>
<ul>
<li>Deprecated: <code>element.ref</code> access: React 19 supports ref
as a prop, so we’re deprecating <code>element.ref</code> in favor of
<code>element.props.ref</code>. Accessing will result in a warning.</li>
<li><code>react-test-renderer</code>: 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 <a
href="https://github.com/testinglibrary"><code>@​testinglibrary</code></a>.com/docs/react-testing-library/intro/)
or <a
href="https://github.com/testingesting-library"><code>@​testingesting-library</code></a>.com/docs/react-native-testing-library/intro)</li>
</ul>
<h2>Breaking Changes</h2>
<p>React 19 brings in a number of breaking changes, including the
removals of long-deprecated APIs. We recommend first upgrading to
<code>18.3.1</code>, where we've added additional deprecation warnings.
Check out the <a
href="https://19.react.dev/blog/2024/04/25/react-19-upgrade-guide">upgrade
guide</a> for more details and guidance on codemodding.</p>
<h3>React</h3>
<ul>
<li>New JSX Transform is now required: We introduced <a
href="https://legacy.reactjs.org/blog/2020/09/22/introducing-the-new-jsx-transform.html">a
new JSX transform</a> 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.</li>
<li>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 <code>onUncaughtError</code> and <code>onCaughtError</code>
methods to <code>createRoot</code> and <code>hydrateRoot</code> to
customize this error handling.</li>
<li>Removed: <code>propTypes</code>: Using <code>propTypes</code> will
now be silently ignored. If required, we recommend migrating to
TypeScript or another type-checking solution.</li>
<li>Removed: <code>defaultProps</code> for functions: ES6 default
parameters can be used in place. Class components continue to support
<code>defaultProps</code> since there is no ES6 alternative.</li>
<li>Removed: <code>contextTypes</code> and <code>getChildContext</code>:
Legacy Context for class components has been removed in favor of the
<code>contextType</code> API.</li>
</ul>
<!-- raw HTML omitted -->
</blockquote>
<p>... (truncated)</p>
</details>
<details>
<summary>Changelog</summary>
<p><em>Sourced from <a
href="https://github.com/facebook/react/blob/main/CHANGELOG.md">react-dom's
changelog</a>.</em></p>
<blockquote>
<h2>19.0.0 (December 5, 2024)</h2>
<p>Below is a list of all new features, APIs, deprecations, and breaking
changes. Read <a href="https://react.dev/blog/2024/04/25/react-19">React
19 release post</a> and <a
href="https://react.dev/blog/2024/04/25/react-19-upgrade-guide">React 19
upgrade guide</a> for more information.</p>
<blockquote>
<p>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.</p>
</blockquote>
<h3>New Features</h3>
<h4>React</h4>
<ul>
<li>Actions: <code>startTransition</code> can now accept async
functions. Functions passed to <code>startTransition</code> 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 <code>fetch()</code> in the pending state,
and provides support for error handling, and optimistic updates.</li>
<li><code>useActionState</code>: 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 <code>action</code> prop to support
progressive enhancement in forms.</li>
<li><code>useOptimistic</code>: 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.</li>
<li><code>use</code>: is a new API that allows reading resources in
render. In React 19, <code>use</code> accepts a promise or Context. If
provided a promise, <code>use</code> will suspend until a value is
resolved. <code>use</code> can only be used in render but can be called
conditionally.</li>
<li><code>ref</code> as a prop: Refs can now be used as props, removing
the need for <code>forwardRef</code>.</li>
<li><strong>Suspense sibling pre-warming</strong>: 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.</li>
</ul>
<h4>React DOM Client</h4>
<ul>
<li><code>&lt;form&gt; action</code> prop: Form Actions allow you to
manage forms automatically and integrate with
<code>useFormStatus</code>. When a <code>&lt;form&gt; action</code>
succeeds, React will automatically reset the form for uncontrolled
components. The form can be reset manually with the new
<code>requestFormReset</code> API.</li>
<li><code>&lt;button&gt; and &lt;input&gt; formAction</code> prop:
Actions can be passed to the <code>formAction</code> prop to configure
form submission behavior. This allows using different Actions depending
on the input.</li>
<li><code>useFormStatus</code>: is a new hook that provides the status
of the parent <code>&lt;form&gt; action</code>, as if the form was a
Context provider. The hook returns the values: <code>pending</code>,
<code>data</code>, <code>method</code>, and <code>action</code>.</li>
<li>Support for Document Metadata: We’ve added support for rendering
document metadata tags in components natively. React will automatically
hoist them into the <code>&lt;head&gt;</code> section of the
document.</li>
<li>Support for Stylesheets: React 19 will ensure stylesheets are
inserted into the <code>&lt;head&gt;</code> on the client before
revealing the content of a Suspense boundary that depends on that
stylesheet.</li>
<li>Support for async scripts: Async scripts can be rendered anywhere in
the component tree and React will handle ordering and
deduplication.</li>
<li>Support for preloading resources: React 19 ships with
<code>preinit</code>, <code>preload</code>, <code>prefetchDNS</code>,
and <code>preconnect</code> 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.</li>
</ul>
<h4>React DOM Server</h4>
<ul>
<li>Added <code>prerender</code> and <code>prerenderToNodeStream</code>
APIs for static site generation. They are designed to work with
streaming environments like Node.js Streams and Web Streams. Unlike
<code>renderToString</code>, they wait for data to load for HTML
generation.</li>
</ul>
<h4>React Server Components</h4>
<ul>
<li>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 <a
href="https://19.react.dev/reference/rsc/server-components">docs</a> for
how to support React Server Components.</li>
</ul>
<h3>Deprecations</h3>
<ul>
<li>Deprecated: <code>element.ref</code> access: React 19 supports ref
as a prop, so we’re deprecating <code>element.ref</code> in favor of
<code>element.props.ref</code>. Accessing will result in a warning.</li>
<li><code>react-test-renderer</code>: 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 <a
href="https://testing-library.com/docs/react-testing-library/intro/"><code>@​testing-library/react</code></a>
or <a
href="https://testing-library.com/docs/react-native-testing-library/intro"><code>@​testing-library/react-native</code></a></li>
</ul>
<h3>Breaking Changes</h3>
<p>React 19 brings in a number of breaking changes, including the
removals of long-deprecated APIs. We recommend first upgrading to
<code>18.3.1</code>, where we've added additional deprecation warnings.
Check out the <a
href="https://19.react.dev/blog/2024/04/25/react-19-upgrade-guide">upgrade
guide</a> for more details and guidance on codemodding.</p>
<h3>React</h3>
<ul>
<li>New JSX Transform is now required: We introduced <a
href="https://legacy.reactjs.org/blog/2020/09/22/introducing-the-new-jsx-transform.html">a
new JSX transform</a> 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.</li>
<li>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 <code>onUncaughtError</code> and <code>onCaughtError</code>
methods to <code>createRoot</code> and <code>hydrateRoot</code> to
customize this error handling.</li>
<li>Removed: <code>propTypes</code>: Using <code>propTypes</code> will
now be silently ignored. If required, we recommend migrating to
TypeScript or another type-checking solution.</li>
<li>Removed: <code>defaultProps</code> for functions: ES6 default
parameters can be used in place. Class components continue to support
<code>defaultProps</code> since there is no ES6 alternative.</li>
</ul>
<!-- raw HTML omitted -->
</blockquote>
<p>... (truncated)</p>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a
href="https://github.com/facebook/react/commit/989af12f72080c17db03ead91d99b6394a215564"><code>989af12</code></a>
Make prerendering always non-blocking with fix (<a
href="https://github.com/facebook/react/tree/HEAD/packages/react-dom/issues/31452">#31452</a>)</li>
<li><a
href="https://github.com/facebook/react/commit/e1378902bbb322aa1fe1953780f4b2b5f80d26b1"><code>e137890</code></a>
[string-refs] cleanup string ref code (<a
href="https://github.com/facebook/react/tree/HEAD/packages/react-dom/issues/31443">#31443</a>)</li>
<li><a
href="https://github.com/facebook/react/commit/07aa494432e97f63fca9faf2fad6f76fead31063"><code>07aa494</code></a>
Remove enableRefAsProp feature flag (<a
href="https://github.com/facebook/react/tree/HEAD/packages/react-dom/issues/30346">#30346</a>)</li>
<li><a
href="https://github.com/facebook/react/commit/cae764ce81b1bd6c418e9e23651794b6b09208e8"><code>cae764c</code></a>
Revert &quot;[Re-land] Make prerendering always non-blocking (<a
href="https://github.com/facebook/react/tree/HEAD/packages/react-dom/issues/31268">#31268</a>)&quot;
(<a
href="https://github.com/facebook/react/tree/HEAD/packages/react-dom/issues/31355">#31355</a>)</li>
<li><a
href="https://github.com/facebook/react/commit/d49123f73f12564223c890bfa36be537de2c571d"><code>d49123f</code></a>
Expose prerender() for SSG in stable (<a
href="https://github.com/facebook/react/tree/HEAD/packages/react-dom/issues/31298">#31298</a>)</li>
<li><a
href="https://github.com/facebook/react/commit/6c4bbc783286bf6eebd9927cb52e8fec5ad4dd74"><code>6c4bbc7</code></a>
[Re-land] Make prerendering always non-blocking (<a
href="https://github.com/facebook/react/tree/HEAD/packages/react-dom/issues/31268">#31268</a>)</li>
<li><a
href="https://github.com/facebook/react/commit/d8c90fa48d3addefe4b805ec56a3c65e4ee39127"><code>d8c90fa</code></a>
Disable infinite render loop detection (<a
href="https://github.com/facebook/react/tree/HEAD/packages/react-dom/issues/31088">#31088</a>)</li>
<li><a
href="https://github.com/facebook/react/commit/67fee58b1f72754cc77488c40c44e786572ef954"><code>67fee58</code></a>
[Fizz] Start initial work immediately (<a
href="https://github.com/facebook/react/tree/HEAD/packages/react-dom/issues/31079">#31079</a>)</li>
<li><a
href="https://github.com/facebook/react/commit/76aee6f39d94caa04c11be92d75d12cb9ee56494"><code>76aee6f</code></a>
Revert &quot;Make prerendering always non-blocking&quot; (<a
href="https://github.com/facebook/react/tree/HEAD/packages/react-dom/issues/31080">#31080</a>)</li>
<li><a
href="https://github.com/facebook/react/commit/0f1856c49febe96923e469f98c0b123130ea015c"><code>0f1856c</code></a>
Make prerendering always non-blocking (<a
href="https://github.com/facebook/react/tree/HEAD/packages/react-dom/issues/31056">#31056</a>)</li>
<li>Additional commits viewable in <a
href="https://github.com/facebook/react/commits/v19.0.0/packages/react-dom">compare
view</a></li>
</ul>
</details>
<br />

Updates `@types/react-dom` from 18.3.5 to 19.0.3
<details>
<summary>Commits</summary>
<ul>
<li>See full diff in <a
href="https://github.com/DefinitelyTyped/DefinitelyTyped/commits/HEAD/types/react-dom">compare
view</a></li>
</ul>
</details>
<br />

Updates `@types/react` from 18.3.18 to 19.0.8
<details>
<summary>Commits</summary>
<ul>
<li>See full diff in <a
href="https://github.com/DefinitelyTyped/DefinitelyTyped/commits/HEAD/types/react">compare
view</a></li>
</ul>
</details>
<br />

Updates `@types/react-dom` from 18.3.5 to 19.0.3
<details>
<summary>Commits</summary>
<ul>
<li>See full diff in <a
href="https://github.com/DefinitelyTyped/DefinitelyTyped/commits/HEAD/types/react-dom">compare
view</a></li>
</ul>
</details>
<br />

Updates `vite` from 5.4.14 to 6.0.11
<details>
<summary>Release notes</summary>
<p><em>Sourced from <a
href="https://github.com/vitejs/vite/releases">vite's
releases</a>.</em></p>
<blockquote>
<h2>v6.0.11</h2>
<p>Please refer to <a
href="https://github.com/vitejs/vite/blob/v6.0.11/packages/vite/CHANGELOG.md">CHANGELOG.md</a>
for details.</p>
<h2>v6.0.10</h2>
<p>Please refer to <a
href="https://github.com/vitejs/vite/blob/v6.0.10/packages/vite/CHANGELOG.md">CHANGELOG.md</a>
for details.</p>
<h2>v6.0.9</h2>
<p>This version contains a breaking change due to security fixes. See <a
href="https://github.com/vitejs/vite/security/advisories/GHSA-vg6x-rcgg-rjx6">https://github.com/vitejs/vite/security/advisories/GHSA-vg6x-rcgg-rjx6</a>
for more details.</p>
<p>Please refer to <a
href="https://github.com/vitejs/vite/blob/v6.0.9/packages/vite/CHANGELOG.md">CHANGELOG.md</a>
for details.</p>
<h2>v6.0.8</h2>
<p>Please refer to <a
href="https://github.com/vitejs/vite/blob/v6.0.8/packages/vite/CHANGELOG.md">CHANGELOG.md</a>
for details.</p>
<h2>v6.0.7</h2>
<p>Please refer to <a
href="https://github.com/vitejs/vite/blob/v6.0.7/packages/vite/CHANGELOG.md">CHANGELOG.md</a>
for details.</p>
<h2>v6.0.6</h2>
<p>Please refer to <a
href="https://github.com/vitejs/vite/blob/v6.0.6/packages/vite/CHANGELOG.md">CHANGELOG.md</a>
for details.</p>
<h2>v6.0.5</h2>
<p>Please refer to <a
href="https://github.com/vitejs/vite/blob/v6.0.5/packages/vite/CHANGELOG.md">CHANGELOG.md</a>
for details.</p>
<h2>v6.0.4</h2>
<p>Please refer to <a
href="https://github.com/vitejs/vite/blob/v6.0.4/packages/vite/CHANGELOG.md">CHANGELOG.md</a>
for details.</p>
<h2>v6.0.3</h2>
<p>Please refer to <a
href="https://github.com/vitejs/vite/blob/v6.0.3/packages/vite/CHANGELOG.md">CHANGELOG.md</a>
for details.</p>
<h2>v6.0.2</h2>
<p>Please refer to <a
href="https://github.com/vitejs/vite/blob/v6.0.2/packages/vite/CHANGELOG.md">CHANGELOG.md</a>
for details.</p>
<h2>[email protected]</h2>
<p>Please refer to <a
href="https://github.com/vitejs/vite/blob/[email protected]/packages/create-vite/CHANGELOG.md">CHANGELOG.md</a>
for details.</p>
<h2>v6.0.1</h2>
<p>Please refer to <a
href="https://github.com/vitejs/vite/blob/v6.0.1/packages/vite/CHANGELOG.md">CHANGELOG.md</a>
for details.</p>
<h2>[email protected]</h2>
<p>Please refer to <a
href="https://github.com/vitejs/vite/blob/[email protected]/packages/create-vite/CHANGELOG.md">CHANGELOG.md</a>
for details.</p>
<h2>[email protected]</h2>
<p>Please refer to <a
href="https://github.com/vitejs/vite/blob/[email protected]/packages/plugin-legacy/CHANGELOG.md">CHANGELOG.md</a>
for details.</p>
<h2>v6.0.0</h2>
<p>Please refer to <a
href="https://github.com/vitejs/vite/blob/v6.0.0/packages/vite/CHANGELOG.md">CHANGELOG.md</a>
for details.</p>
<h2>v6.0.0-beta.10</h2>
<p>Please refer to <a
href="https://github.com/vitejs/vite/blob/v6.0.0-beta.10/packages/vite/CHANGELOG.md">CHANGELOG.md</a>
for details.</p>
<!-- raw HTML omitted -->
</blockquote>
<p>... (truncated)</p>
</details>
<details>
<summary>Changelog</summary>
<p><em>Sourced from <a
href="https://github.com/vitejs/vite/blob/main/packages/vite/CHANGELOG.md">vite's
changelog</a>.</em></p>
<blockquote>
<h2><!-- raw HTML omitted -->6.0.11 (2025-01-21)<!-- raw HTML omitted
--></h2>
<ul>
<li>fix: <code>preview.allowedHosts</code> with specific values was not
respected (<a
href="https://github.com/vitejs/vite/tree/HEAD/packages/vite/issues/19246">#19246</a>)
(<a
href="https://github.com/vitejs/vite/commit/aeb3ec84a288d6be227a1284607f13428a4f14a1">aeb3ec8</a>),
closes <a
href="https://redirect.github.com/vitejs/vite/issues/19246">#19246</a></li>
<li>fix: allow CORS from loopback addresses by default (<a
href="https://github.com/vitejs/vite/tree/HEAD/packages/vite/issues/19249">#19249</a>)
(<a
href="https://github.com/vitejs/vite/commit/3d038997377a30022b6a6b7916e0b4b5d8b9a363">3d03899</a>),
closes <a
href="https://redirect.github.com/vitejs/vite/issues/19249">#19249</a></li>
</ul>
<h2><!-- raw HTML omitted -->6.0.10 (2025-01-20)<!-- raw HTML omitted
--></h2>
<ul>
<li>fix: try parse <code>server.origin</code> URL (<a
href="https://github.com/vitejs/vite/tree/HEAD/packages/vite/issues/19241">#19241</a>)
(<a
href="https://github.com/vitejs/vite/commit/2495022420fda05ee389c2dcf26921b21e2aed3b">2495022</a>),
closes <a
href="https://redirect.github.com/vitejs/vite/issues/19241">#19241</a></li>
</ul>
<h2><!-- raw HTML omitted -->6.0.9 (2025-01-20)<!-- raw HTML omitted
--></h2>
<ul>
<li>fix!: check host header to prevent DNS rebinding attacks and
introduce <code>server.allowedHosts</code> (<a
href="https://github.com/vitejs/vite/commit/bd896fb5f312fc0ff1730166d1d142fc0d34ba6d">bd896fb</a>)</li>
<li>fix!: default <code>server.cors: false</code> to disallow fetching
from untrusted origins (<a
href="https://github.com/vitejs/vite/commit/b09572acc939351f4e4c50ddf793017a92c678b1">b09572a</a>)</li>
<li>fix: verify token for HMR WebSocket connection (<a
href="https://github.com/vitejs/vite/commit/029dcd6d77d3e3ef10bc38e9a0829784d9760fdb">029dcd6</a>)</li>
</ul>
<h2><!-- raw HTML omitted -->6.0.8 (2025-01-20)<!-- raw HTML omitted
--></h2>
<ul>
<li>fix: avoid SSR HMR for HTML files (<a
href="https://github.com/vitejs/vite/tree/HEAD/packages/vite/issues/19193">#19193</a>)
(<a
href="https://github.com/vitejs/vite/commit/3bd55bcb7e831d2c4f66c90d7bbb3e1fbf7a02b6">3bd55bc</a>),
closes <a
href="https://redirect.github.com/vitejs/vite/issues/19193">#19193</a></li>
<li>fix: build time display 7m 60s (<a
href="https://github.com/vitejs/vite/tree/HEAD/packages/vite/issues/19108">#19108</a>)
(<a
href="https://github.com/vitejs/vite/commit/cf0d2c8e232a1af716c71cdd2218d180f7ecc02b">cf0d2c8</a>),
closes <a
href="https://redirect.github.com/vitejs/vite/issues/19108">#19108</a></li>
<li>fix: don't resolve URL starting with double slash (<a
href="https://github.com/vitejs/vite/tree/HEAD/packages/vite/issues/19059">#19059</a>)
(<a
href="https://github.com/vitejs/vite/commit/35942cde11fd8a68fa89bf25f7aa1ddb87d775b2">35942cd</a>),
closes <a
href="https://redirect.github.com/vitejs/vite/issues/19059">#19059</a></li>
<li>fix: ensure <code>server.close()</code> only called once (<a
href="https://github.com/vitejs/vite/tree/HEAD/packages/vite/issues/19204">#19204</a>)
(<a
href="https://github.com/vitejs/vite/commit/db81c2dada961f40c0882b5182adf2f34bb5c178">db81c2d</a>),
closes <a
href="https://redirect.github.com/vitejs/vite/issues/19204">#19204</a></li>
<li>fix: resolve.conditions in ResolvedConfig was
<code>defaultServerConditions</code> (<a
href="https://github.com/vitejs/vite/tree/HEAD/packages/vite/issues/19174">#19174</a>)
(<a
href="https://github.com/vitejs/vite/commit/ad75c56dce5618a3a416e18f9a5c3880d437a107">ad75c56</a>),
closes <a
href="https://redirect.github.com/vitejs/vite/issues/19174">#19174</a></li>
<li>fix: tree shake stringified JSON imports (<a
href="https://github.com/vitejs/vite/tree/HEAD/packages/vite/issues/19189">#19189</a>)
(<a
href="https://github.com/vitejs/vite/commit/f2aed62d0bf1b66e870ee6b4aab80cd1702793ab">f2aed62</a>),
closes <a
href="https://redirect.github.com/vitejs/vite/issues/19189">#19189</a></li>
<li>fix: use shared sigterm callback (<a
href="https://github.com/vitejs/vite/tree/HEAD/packages/vite/issues/19203">#19203</a>)
(<a
href="https://github.com/vitejs/vite/commit/47039f4643179be31a8d7c7fbff83c5c13deb787">47039f4</a>),
closes <a
href="https://redirect.github.com/vitejs/vite/issues/19203">#19203</a></li>
<li>fix(deps): update all non-major dependencies (<a
href="https://github.com/vitejs/vite/tree/HEAD/packages/vite/issues/19098">#19098</a>)
(<a
href="https://github.com/vitejs/vite/commit/8639538e6498d1109da583ad942c1472098b5919">8639538</a>),
closes <a
href="https://redirect.github.com/vitejs/vite/issues/19098">#19098</a></li>
<li>fix(optimizer): use correct default install state path for yarn PnP
(<a
href="https://github.com/vitejs/vite/tree/HEAD/packages/vite/issues/19119">#19119</a>)
(<a
href="https://github.com/vitejs/vite/commit/e690d8bb1e5741e81df5b7a6a5c8c3c1c971fa41">e690d8b</a>),
closes <a
href="https://redirect.github.com/vitejs/vite/issues/19119">#19119</a></li>
<li>fix(types): improve <code>ESBuildOptions.include / exclude</code>
type to allow <code>readonly (string | RegExp)[]</code> (<a
href="https://github.com/vitejs/vite/commit/ea53e7095297ea4192490fd58556414cc59a8975">ea53e70</a>),
closes <a
href="https://redirect.github.com/vitejs/vite/issues/19146">#19146</a></li>
<li>chore(deps): update dependency pathe to v2 (<a
href="https://github.com/vitejs/vite/tree/HEAD/packages/vite/issues/19139">#19139</a>)
(<a
href="https://github.com/vitejs/vite/commit/71506f0a8deda5254cb49c743cd439dfe42859ce">71506f0</a>),
closes <a
href="https://redirect.github.com/vitejs/vite/issues/19139">#19139</a></li>
</ul>
<h2><!-- raw HTML omitted -->6.0.7 (2025-01-02)<!-- raw HTML omitted
--></h2>
<ul>
<li>fix: fix <code>minify</code> when <code>builder.sharedPlugins:
true</code> (<a
href="https://github.com/vitejs/vite/tree/HEAD/packages/vite/issues/19025">#19025</a>)
(<a
href="https://github.com/vitejs/vite/commit/f7b1964d3a93a21f80b61638fa6ae9606d0a6f4f">f7b1964</a>),
closes <a
href="https://redirect.github.com/vitejs/vite/issues/19025">#19025</a></li>
<li>fix: skip the plugin if it has been called before with the same id
and importer (<a
href="https://github.com/vitejs/vite/tree/HEAD/packages/vite/issues/19016">#19016</a>)
(<a
href="https://github.com/vitejs/vite/commit/b178c90c7d175ea31f8b67dccad3918f820357a4">b178c90</a>),
closes <a
href="https://redirect.github.com/vitejs/vite/issues/19016">#19016</a></li>
<li>fix(html): error while removing <code>vite-ignore</code> attribute
for inline script (<a
href="https://github.com/vitejs/vite/tree/HEAD/packages/vite/issues/19062">#19062</a>)
(<a
href="https://github.com/vitejs/vite/commit/a4922537a8d705da7769d30626a0d846511fc124">a492253</a>),
closes <a
href="https://redirect.github.com/vitejs/vite/issues/19062">#19062</a></li>
<li>fix(ssr): fix semicolon injection by ssr transform (<a
href="https://github.com/vitejs/vite/tree/HEAD/packages/vite/issues/19097">#19097</a>)
(<a
href="https://github.com/vitejs/vite/commit/1c102d517de52531faf5765632703977a17de65a">1c102d5</a>),
closes <a
href="https://redirect.github.com/vitejs/vite/issues/19097">#19097</a></li>
<li>perf: skip globbing for static path in warmup (<a
href="https://github.com/vitejs/vite/tree/HEAD/packages/vite/issues/19107">#19107</a>)
(<a
href="https://github.com/vitejs/vite/commit/677508bf8268a7b8661e5557a3d0a2a76cab8bd1">677508b</a>),
closes <a
href="https://redirect.github.com/vitejs/vite/issues/19107">#19107</a></li>
<li>feat(css): show lightningcss warnings (<a
href="https://github.com/vitejs/vite/tree/HEAD/packages/vite/issues/19076">#19076</a>)
(<a
href="https://github.com/vitejs/vite/commit/b07c036faf6849fe5ffd03125f25dc00f460f8ba">b07c036</a>),
closes <a
href="https://redirect.github.com/vitejs/vite/issues/19076">#19076</a></li>
</ul>
<h2><!-- raw HTML omitted -->6.0.6 (2024-12-26)<!-- raw HTML omitted
--></h2>
<!-- raw HTML omitted -->
</blockquote>
<p>... (truncated)</p>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a
href="https://github.com/vitejs/vite/commit/a0ed4057c90a1135aa58d06305f446e232f63e2a"><code>a0ed405</code></a>
release: v6.0.11</li>
<li><a
href="https://github.com/vitejs/vite/commit/3d038997377a30022b6a6b7916e0b4b5d8b9a363"><code>3d03899</code></a>
fix: allow CORS from loopback addresses by default (<a
href="https://github.com/vitejs/vite/tree/HEAD/packages/vite/issues/19249">#19249</a>)</li>
<li><a
href="https://github.com/vitejs/vite/commit/aeb3ec84a288d6be227a1284607f13428a4f14a1"><code>aeb3ec8</code></a>
fix: <code>preview.allowedHosts</code> with specific values was not
respected (<a
href="https://github.com/vitejs/vite/tree/HEAD/packages/vite/issues/19246">#19246</a>)</li>
<li><a
href="https://github.com/vitejs/vite/commit/9654348258eaa0883171533a2b74b4e2825f5fb6"><code>9654348</code></a>
release: v6.0.10</li>
<li><a
href="https://github.com/vitejs/vite/commit/2495022420fda05ee389c2dcf26921b21e2aed3b"><code>2495022</code></a>
fix: try parse <code>server.origin</code> URL (<a
href="https://github.com/vitejs/vite/tree/HEAD/packages/vite/issues/19241">#19241</a>)</li>
<li><a
href="https://github.com/vitejs/vite/commit/a55f8ba3e43108de340610d4d021dcd926be5876"><code>a55f8ba</code></a>
release: v6.0.9</li>
<li><a
href="https://github.com/vitejs/vite/commit/bd896fb5f312fc0ff1730166d1d142fc0d34ba6d"><code>bd896fb</code></a>
fix!: check host header to prevent DNS rebinding attacks and introduce
`serve...</li>
<li><a
href="https://github.com/vitejs/vite/commit/029dcd6d77d3e3ef10bc38e9a0829784d9760fdb"><code>029dcd6</code></a>
fix: verify token for HMR WebSocket connection</li>
<li><a
href="https://github.com/vitejs/vite/commit/b09572acc939351f4e4c50ddf793017a92c678b1"><code>b09572a</code></a>
fix!: default <code>server.cors: false</code> to disallow fetching from
untrusted origins</li>
<li><a
href="https://github.com/vitejs/vite/commit/c0f72a695c5308cba605e3db4f851f4f6692e50c"><code>c0f72a6</code></a>
release: v6.0.8</li>
<li>Additional commits viewable in <a
href="https://github.com/vitejs/vite/commits/v6.0.11/packages/vite">compare
view</a></li>
</ul>
</details>
<br />

Updates `@types/express` from 4.17.21 to 5.0.0
<details>
<summary>Commits</summary>
<ul>
<li>See full diff in <a
href="https://github.com/DefinitelyTyped/DefinitelyTyped/commits/HEAD/types/express">compare
view</a></li>
</ul>
</details>
<br />

Updates `tsup` from 8.3.5 to 8.3.6
<details>
<summary>Release notes</summary>
<p><em>Sourced from <a
href="https://github.com/egoist/tsup/releases">tsup's
releases</a>.</em></p>
<blockquote>
<h2>v8.3.6</h2>
<h3>   🐞 Bug Fixes</h3>
<ul>
<li>Don't await sub-process of <code>onSuccess</code>  -  by <a
href="https://github.com/laat"><code>@​laat</code></a> in <a
href="https://redirect.github.com/egoist/tsup/issues/1256">egoist/tsup#1256</a>
<a href="https://github.com/egoist/tsup/commit/314a6d7"><!-- raw HTML
omitted -->(314a6)<!-- raw HTML omitted --></a></li>
</ul>
<h5>    <a
href="https://github.com/egoist/tsup/compare/v8.3.5...v8.3.6">View
changes on GitHub</a></h5>
</blockquote>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a
href="https://github.com/egoist/tsup/commit/bee8f42dc72c5b40c2946422fc632069dde2a55b"><code>bee8f42</code></a>
chore: release v8.3.6</li>
<li><a
href="https://github.com/egoist/tsup/commit/86c3b0bfac9daf2c94c8273f2a931c0d25205b42"><code>86c3b0b</code></a>
chore: fix pass options</li>
<li><a
href="https://github.com/egoist/tsup/commit/314a6d7ac4c2cb7c7dad2940734a961b9352453b"><code>314a6d7</code></a>
fix: don't await sub-process of <code>onSuccess</code> (<a
href="https://redirect.github.com/egoist/tsup/issues/1256">#1256</a>)</li>
<li>See full diff in <a
href="https://github.com/egoist/tsup/compare/v8.3.5...v8.3.6">compare
view</a></li>
</ul>
</details>
<br />

Updates `vite-tsconfig-paths` from 4.3.2 to 5.1.4
<details>
<summary>Release notes</summary>
<p><em>Sourced from <a
href="https://github.com/aleclarson/vite-tsconfig-paths/releases">vite-tsconfig-paths's
releases</a>.</em></p>
<blockquote>
<h2>v5.1.4</h2>
<ul>
<li><strong>fix:</strong> correctly infer the <code>paths</code> root
dir (eea1c17d0fe4ad6e3f8bc324216bc09173e3c778) (<a
href="https://redirect.github.com/aleclarson/vite-tsconfig-paths/issues/150">#150</a>)</li>
</ul>
<h2>v5.1.3</h2>
<ul>
<li><strong>fix:</strong> Once an importer is matched, end directory
traversal (b0d8ecb9b862412e93f73b172cc0692259ce01b8)</li>
<li><strong>feat:</strong> Add <code>vite-tsconfig-paths:resolve</code>
debug logs (7160d6e52673367a7f4766ca9023ddc1da43e5dd)</li>
<li><strong>chore:</strong> Ensure debug logs can be enabled in vitest
(0dc9a8b9b0ec8657f9d6980ac33d0bc090e278ef)</li>
</ul>
<h2>v5.1.2</h2>
<ul>
<li>fix Windows regression introduced in v5.1.1 (<a
href="https://redirect.github.com/aleclarson/vite-tsconfig-paths/issues/162">#162</a>)</li>
</ul>
<h2>v5.1.1</h2>
<ul>
<li>support <code>${configDir}</code> syntax in include/exclude (<a
href="https://redirect.github.com/aleclarson/vite-tsconfig-paths/issues/156">#156</a>)</li>
</ul>
<h2>v5.1.0</h2>
<ul>
<li>Add <code>skip</code> option for adding additional directories to be
skipped when searching for tsconfig.json files (<a
href="https://redirect.github.com/aleclarson/vite-tsconfig-paths/issues/146">#146</a>)</li>
<li>Fix path resolution on Windows when other Vite plugins neglect to
normalize the <code>importer</code> path before calling
<code>this.resolve</code> in their <code>resolveId</code> hooks (<a
href="https://redirect.github.com/aleclarson/vite-tsconfig-paths/issues/157">#157</a>)</li>
<li>Allow both tsconfig.json and jsconfig.json in the same directory
(4124b091607503d44b876bb4edd726667b386660)</li>
</ul>
<h2>v5.0.0</h2>
<p>This package is now ESM only in order to align with Vite: <a
href="https://vitejs.dev/guide/migration#deprecate-cjs-node-api">https://vitejs.dev/guide/migration#deprecate-cjs-node-api</a></p>
<p>If your project is using CommonJS, you can rename your Vite config to
use the <code>.mjs</code> or <code>.mts</code> extension (depending on
whether you use TypeScript or not). If you're not using Vite v5.0.0+,
you may want to pin your dependency to v4 of this plugin.</p>
</blockquote>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a
href="https://github.com/aleclarson/vite-tsconfig-paths/commit/f58afbc7ec75826c5034078007d143243dbab4c7"><code>f58afbc</code></a>
5.1.4</li>
<li><a
href="https://github.com/aleclarson/vite-tsconfig-paths/commit/ece58bf988e1a6de0b568103157da734bdfec3e6"><code>ece58bf</code></a>
chore: upgrade typescript</li>
<li><a
href="https://github.com/aleclarson/vite-tsconfig-paths/commit/593a611dcef7fbb9cd8e5d34e7b5538019f5575b"><code>593a611</code></a>
fix: ensure <code>parseNative</code> result is correctly handled</li>
<li><a
href="https://github.com/aleclarson/vite-tsconfig-paths/commit/eea1c17d0fe4ad6e3f8bc324216bc09173e3c778"><code>eea1c17</code></a>
fix: correctly infer the <code>paths</code> root dir</li>
<li><a
href="https://github.com/aleclarson/vite-tsconfig-paths/commit/34cb651fab6ad273b80b2cbbb11f18fbd5d0131b"><code>34cb651</code></a>
test: add case for resolving <code>paths</code> from an extended
tsconfig (<a
href="https://redirect.github.com/aleclarson/vite-tsconfig-paths/issues/166">#166</a>)</li>
<li><a
href="https://github.com/aleclarson/vite-tsconfig-paths/commit/2d187b9a455f1042ce0e4c4d8e8e75f3bbe57b92"><code>2d187b9</code></a>
chore: upgrade vite &amp; vitest</li>
<li><a
href="https://github.com/aleclarson/vite-tsconfig-paths/commit/a5bb13e9e2538ba4a6371dd935f3a6208d951f63"><code>a5bb13e</code></a>
chore: stop using yarn in package.json scripts</li>
<li><a
href="https://github.com/aleclarson/vite-tsconfig-paths/commit/dcb0c9d17fda505eddbda0ed681b795e7fcfa1bc"><code>dcb0c9d</code></a>
5.1.3</li>
<li><a
href="https://github.com/aleclarson/vite-tsconfig-paths/commit/16ef4b13ab774945005da004c1c0bf012e93dc1b"><code>16ef4b1</code></a>
test: ensure <code>root</code> option is set</li>
<li><a
href="https://github.com/aleclarson/vite-tsconfig-paths/commit/0dc9a8b9b0ec8657f9d6980ac33d0bc090e278ef"><code>0dc9a8b</code></a>
chore: ensure debug logs can be enabled in vitest</li>
<li>Additional commits viewable in <a
href="https://github.com/aleclarson/vite-tsconfig-paths/compare/v4.3.2...v5.1.4">compare
view</a></li>
</ul>
</details>
<br />


Dependabot will resolve any conflicts with this PR as long as you don't
alter it yourself. You can also trigger a rebase manually by commenting
`@dependabot rebase`.

[//]: # (dependabot-automerge-start)
[//]: # (dependabot-automerge-end)

---

<details>
<summary>Dependabot commands and options</summary>
<br />

You can trigger Dependabot actions by commenting on this PR:
- `@dependabot rebase` will rebase this PR
- `@dependabot recreate` will recreate this PR, overwriting any edits
that have been made to it
- `@dependabot merge` will merge this PR after your CI passes on it
- `@dependabot squash and merge` will squash and merge this PR after
your CI passes on it
- `@dependabot cancel merge` will cancel a previously requested merge
and block automerging
- `@dependabot reopen` will reopen this PR if it is closed
- `@dependabot close` will close this PR and stop Dependabot recreating
it. You can achieve the same result by closing it manually
- `@dependabot show <dependency name> ignore conditions` will show all
of the ignore conditions of the specified dependency
- `@dependabot ignore <dependency name> major version` will close this
group update PR and stop Dependabot creating any more for the specific
dependency's major version (unless you unignore this specific
dependency's major version or upgrade to it yourself)
- `@dependabot ignore <dependency name> minor version` will close this
group update PR and stop Dependabot creating any more for the specific
dependency's minor version (unless you unignore this specific
dependency's minor version or upgrade to it yourself)
- `@dependabot ignore <dependency name>` will close this group update PR
and stop Dependabot creating any more for the specific dependency
(unless you unignore this specific dependency or upgrade to it yourself)
- `@dependabot unignore <dependency name>` will remove all of the ignore
conditions of the specified dependency
- `@dependabot unignore <dependency name> <ignore condition>` will
remove the ignore condition of the specified dependency and ignore
conditions


</details>

---------

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Co-authored-by: Anthony Shew <[email protected]>
Co-authored-by: Anthony Shew <[email protected]>

Author: dependabot[bot]

.github/dependabot.yml

@@ -2,10 +2,6 @@
 # From what I can tell, we are forced into approaching it this way
 # because of the many workspace roots.
 
-# The GHA at .github/workflows/examples-autoaprove-and-automerge.yml
-# is responsible for merging them all to one umbrella PR
-# on the branch #dependabot-updates.
-
 version: 2
 updates:
   - package-ecosystem: "npm"
@@ -24,6 +20,8 @@ updates:
       basic:
         patterns:
           - "*"
+        update-types:
+          - "minor"
 
   - package-ecosystem: "npm"
     directory: "/examples/kitchen-sink"
@@ -41,6 +39,16 @@ updates:
       kitchen-sink:
         patterns:
           - "*"
+        update-types:
+          - "minor"
+    ignore:
+      # Types are just...broken?
+      - dependency-name: "@types/express"
+      # Remix is behind on updating these peer deps and npm doesn't like it
+      - dependency-name: "react"
+      - dependency-name: "react-dom"
+      - dependency-name: "@types/react"
+      - dependency-name: "@types/react-dom"
 
   - package-ecosystem: "npm"
     directory: "/examples/non-monorepo"
@@ -58,6 +66,8 @@ updates:
       non-monorepo:
         patterns:
           - "*"
+        update-types:
+          - "minor"
 
   - package-ecosystem: "npm"
     directory: "/examples/with-shell-commands"
@@ -75,6 +85,8 @@ updates:
       with-shell-commands:
         patterns:
           - "*"
+        update-types:
+          - "minor"
 
   - package-ecosystem: "npm"
     directory: "/examples/with-svelte"
@@ -92,6 +104,8 @@ updates:
       with-svelte:
         patterns:
           - "*"
+        update-types:
+          - "minor"
 
   - package-ecosystem: "npm"
     directory: "/examples/with-tailwind"
@@ -109,3 +123,5 @@ updates:
       with-tailwind:
         patterns:
           - "*"
+        update-types:
+          - "minor"

examples/kitchen-sink/apps/api/package.json

@@ -28,13 +28,13 @@
     "@repo/typescript-config": "workspace:*",
     "@types/body-parser": "^1.19.5",
     "@types/cors": "^2.8.17",
-    "@types/express": "^4.17.17",
+    "@types/express": "4.17.17",
     "@types/morgan": "^1.9.9",
     "@types/node": "^22.10.10",
     "@types/supertest": "^6.0.2",
     "jest": "^29.7.0",
     "supertest": "^7.0.0",
-    "tsup": "^8.3.5",
+    "tsup": "^8.3.6",
     "typescript": "5.7.3"
   }
 }

examples/kitchen-sink/apps/blog/package.json

@@ -25,14 +25,14 @@
     "@remix-run/dev": "^2.15.2",
     "@types/react": "^18.2.20",
     "@types/react-dom": "^18.2.7",
-    "@typescript-eslint/eslint-plugin": "^8.21.0",
-    "@typescript-eslint/parser": "^8.21.0",
+    "@typescript-eslint/eslint-plugin": "^8.22.0",
+    "@typescript-eslint/parser": "^8.22.0",
     "@vercel/remix": "2.15.2",
     "autoprefixer": "^10.4.20",
     "eslint": "^9.19.0",
     "typescript": "5.7.3",
     "vite": "^5.4.14",
-    "vite-tsconfig-paths": "^4.2.1"
+    "vite-tsconfig-paths": "4.2.1"
   },
   "engines": {
     "node": ">=18.0.0"

examples/kitchen-sink/packages/config-eslint/package.json

@@ -21,6 +21,6 @@
     "eslint-plugin-turbo": "^2.3.4",
     "globals": "^15.14.0",
     "typescript": "^5.7.3",
-    "typescript-eslint": "^8.21.0"
+    "typescript-eslint": "^8.22.0"
   }
 }

examples/kitchen-sink/packages/logger/package.json

@@ -26,7 +26,7 @@
     "@types/node": "^22.10.10",
     "eslint": "^9.19.0",
     "jest": "^29.7.0",
-    "tsup": "^8.3.5",
+    "tsup": "^8.3.6",
     "typescript": "5.7.3"
   }
 }

examples/kitchen-sink/packages/ui/package.json

@@ -40,7 +40,7 @@
     "jest": "^29.7.0",
     "react": "^19.0.0",
     "react-dom": "^19.0.0",
-    "tsup": "^8.3.5",
+    "tsup": "^8.3.6",
     "typescript": "5.7.3"
   }
 }