Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
deps(example): bump the dependencies group across 1 directory with 6 …
…updates (#2562) Bumps the dependencies group with 6 updates in the /examples/nextjs-app-dir-validate-email directory: | 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.12` | `19.0.1` | | [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.1` | `19.0.2` | | [eslint-config-next](https://github.com/vercel/next.js/tree/HEAD/packages/eslint-config-next) | `15.0.3` | `15.1.0` | | [tailwindcss](https://github.com/tailwindlabs/tailwindcss) | `3.4.15` | `3.4.16` | 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><form> action</code> prop: Form Actions allow you to manage forms automatically and integrate with <code>useFormStatus</code>. When a <code><form> 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><button> and <input> 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><form> 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><head></code> section of the document.</li> <li>Support for Stylesheets: React 19 will ensure stylesheets are inserted into the <code><head></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><form> action</code> prop: Form Actions allow you to manage forms automatically and integrate with <code>useFormStatus</code>. When a <code><form> 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><button> and <input> 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><form> 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><head></code> section of the document.</li> <li>Support for Stylesheets: React 19 will ensure stylesheets are inserted into the <code><head></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.12 to 19.0.1 <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><form> action</code> prop: Form Actions allow you to manage forms automatically and integrate with <code>useFormStatus</code>. When a <code><form> 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><button> and <input> 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><form> 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><head></code> section of the document.</li> <li>Support for Stylesheets: React 19 will ensure stylesheets are inserted into the <code><head></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><form> action</code> prop: Form Actions allow you to manage forms automatically and integrate with <code>useFormStatus</code>. When a <code><form> 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><button> and <input> 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><form> 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><head></code> section of the document.</li> <li>Support for Stylesheets: React 19 will ensure stylesheets are inserted into the <code><head></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 "[Re-land] Make prerendering always non-blocking (<a href="https://github.com/facebook/react/tree/HEAD/packages/react-dom/issues/31268">#31268</a>)" (<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 "Make prerendering always non-blocking" (<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.1 to 19.0.2 <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.12 to 19.0.1 <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.1 to 19.0.2 <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 `eslint-config-next` from 15.0.3 to 15.1.0 <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/vercel/next.js/releases">eslint-config-next's releases</a>.</em></p> <blockquote> <h2>v15.1.0</h2> <h3>Core Changes</h3> <ul> <li>fix: decrypt bound args before generating a cache key: <a href="https://github.com/vercel/next.js/tree/HEAD/packages/eslint-config-next/issues/72463">#72463</a></li> <li>Fix the path to the next/experimental/testing/server export: <a href="https://github.com/vercel/next.js/tree/HEAD/packages/eslint-config-next/issues/72527">#72527</a></li> <li>Expand <code>server-source-maps</code> scenarios to cover Edge runtime: <a href="https://github.com/vercel/next.js/tree/HEAD/packages/eslint-config-next/issues/72288">#72288</a></li> <li>Ensure logged errors in Edge runtime include the stack: <a href="https://github.com/vercel/next.js/tree/HEAD/packages/eslint-config-next/issues/72394">#72394</a></li> <li>fix: added cache control headers for static app routes: <a href="https://github.com/vercel/next.js/tree/HEAD/packages/eslint-config-next/issues/72521">#72521</a></li> <li>capture console issues as console errors: <a href="https://github.com/vercel/next.js/tree/HEAD/packages/eslint-config-next/issues/72468">#72468</a></li> <li>Add expireTag and expirePath APIs: <a href="https://github.com/vercel/next.js/tree/HEAD/packages/eslint-config-next/issues/72485">#72485</a></li> <li>fix: try/catch access to localStorage within __NEXT_APP_ISR_INDICATOR useEffect: <a href="https://github.com/vercel/next.js/tree/HEAD/packages/eslint-config-next/issues/72362">#72362</a></li> <li>Move client build ID to a global variable: <a href="https://github.com/vercel/next.js/tree/HEAD/packages/eslint-config-next/issues/72592">#72592</a></li> <li>refactor(turbopack): Remove <code>swc_css</code>: <a href="https://github.com/vercel/next.js/tree/HEAD/packages/eslint-config-next/issues/72602">#72602</a></li> <li>Bypass source map dev middleware for client chunks: <a href="https://github.com/vercel/next.js/tree/HEAD/packages/eslint-config-next/issues/72581">#72581</a></li> <li>chore: remove <code>rc</code> from URL: <a href="https://github.com/vercel/next.js/tree/HEAD/packages/eslint-config-next/issues/72599">#72599</a></li> <li>improve <code>no-img-element</code> lint error message: <a href="https://github.com/vercel/next.js/tree/HEAD/packages/eslint-config-next/issues/72410">#72410</a></li> <li>Combine bound <code>"use cache"</code> closure args into a single parameter: <a href="https://github.com/vercel/next.js/tree/HEAD/packages/eslint-config-next/issues/72587">#72587</a></li> <li>[Turbopack] add BackendOptions and allow to disable dependencies, children and storage: <a href="https://github.com/vercel/next.js/tree/HEAD/packages/eslint-config-next/issues/72426">#72426</a></li> <li>Omit unused args when calling <code>"use cache"</code> functions: <a href="https://github.com/vercel/next.js/tree/HEAD/packages/eslint-config-next/issues/72506">#72506</a></li> <li>Add experimental <code>clientSegmentCache</code> flag: <a href="https://github.com/vercel/next.js/tree/HEAD/packages/eslint-config-next/issues/72626">#72626</a></li> <li>Add <code>compiler.define</code> option: <a href="https://github.com/vercel/next.js/tree/HEAD/packages/eslint-config-next/issues/71802">#71802</a></li> <li>Fix static indicator with dynamicIO: <a href="https://github.com/vercel/next.js/tree/HEAD/packages/eslint-config-next/issues/72631">#72631</a></li> <li>Allow usage of Node.js prereleases: <a href="https://github.com/vercel/next.js/tree/HEAD/packages/eslint-config-next/issues/72635">#72635</a></li> <li>improved network url in (dev) cli: <a href="https://github.com/vercel/next.js/tree/HEAD/packages/eslint-config-next/issues/72634">#72634</a></li> <li>chore: update <code>getting-started/react-essentials</code> path: <a href="https://github.com/vercel/next.js/tree/HEAD/packages/eslint-config-next/issues/72250">#72250</a></li> <li>Fix static indicator for pure IO case: <a href="https://github.com/vercel/next.js/tree/HEAD/packages/eslint-config-next/issues/72639">#72639</a></li> <li>Bump the monorepo packages TypeScript to <code>5.6.3</code>: <a href="https://github.com/vercel/next.js/tree/HEAD/packages/eslint-config-next/issues/72625">#72625</a></li> <li>Bump <code>@capsizecss/metrics</code> to 3.4.0 for Geist Google Font: <a href="https://github.com/vercel/next.js/tree/HEAD/packages/eslint-config-next/issues/72746">#72746</a></li> <li>refactor: remove unused asNotFound property: <a href="https://github.com/vercel/next.js/tree/HEAD/packages/eslint-config-next/issues/72585">#72585</a></li> <li>Remove unused <code>enabled</code> config from server actions transforms: <a href="https://github.com/vercel/next.js/tree/HEAD/packages/eslint-config-next/issues/72755">#72755</a></li> <li>Ensure Next.js is ignore-listed when used as external: <a href="https://github.com/vercel/next.js/tree/HEAD/packages/eslint-config-next/issues/72498">#72498</a></li> <li>Bump <code>eslint-plugin-react</code> to 7.37.0: <a href="https://github.com/vercel/next.js/tree/HEAD/packages/eslint-config-next/issues/72759">#72759</a></li> <li>upgrade amphtml-validator to 1.0.38: <a href="https://github.com/vercel/next.js/tree/HEAD/packages/eslint-config-next/issues/72645">#72645</a></li> <li>fix multi-level redirect in server actions: <a href="https://github.com/vercel/next.js/tree/HEAD/packages/eslint-config-next/issues/72770">#72770</a></li> <li>refactor: rename error boundary not-found to http-error-fallback: <a href="https://github.com/vercel/next.js/tree/HEAD/packages/eslint-config-next/issues/72586">#72586</a></li> <li>Upgrade React from <code>5c56b873-20241107</code> to <code>7ac8e612-20241113</code>: <a href="https://github.com/vercel/next.js/tree/HEAD/packages/eslint-config-next/issues/72768">#72768</a></li> <li>Re-use randomly selected dev server port for automatic restarts: <a href="https://github.com/vercel/next.js/tree/HEAD/packages/eslint-config-next/issues/72771">#72771</a></li> <li>Emit build error when <code>"use cache"</code> is used without <code>dynamicIO</code> enabled: <a href="https://github.com/vercel/next.js/tree/HEAD/packages/eslint-config-next/issues/72781">#72781</a></li> <li>fix: not found bounary prop: <a href="https://github.com/vercel/next.js/tree/HEAD/packages/eslint-config-next/issues/72784">#72784</a></li> <li>silence sass <code>legacy-js-api</code> warning: <a href="https://github.com/vercel/next.js/tree/HEAD/packages/eslint-config-next/issues/72632">#72632</a></li> <li>[Segment Prefetch] Move access token to route tree: <a href="https://github.com/vercel/next.js/tree/HEAD/packages/eslint-config-next/issues/72775">#72775</a></li> <li>Add internal affordances to show ignore-listed stackframes in terminal: <a href="https://github.com/vercel/next.js/tree/HEAD/packages/eslint-config-next/issues/72763">#72763</a></li> <li>chore(turbopack): Centralize reqwest TLS feature configs in turbo-tasks-fetch: <a href="https://github.com/vercel/next.js/tree/HEAD/packages/eslint-config-next/issues/72526">#72526</a></li> <li>Upgrade React from <code>7ac8e612-20241113</code> to <code>380f5d67-20241113</code>: <a href="https://github.com/vercel/next.js/tree/HEAD/packages/eslint-config-next/issues/72819">#72819</a></li> <li>Shorten unsourcemapped absolute locations in terminal stacktraces: <a href="https://github.com/vercel/next.js/tree/HEAD/packages/eslint-config-next/issues/72764">#72764</a></li> <li>codemod: replace <code>revalidate(Tag|Path)</code> to <code>expire(Tag|Path)</code>: <a href="https://github.com/vercel/next.js/tree/HEAD/packages/eslint-config-next/issues/72826">#72826</a></li> <li>"Fix": Lift type check out of loop: <a href="https://github.com/vercel/next.js/tree/HEAD/packages/eslint-config-next/issues/72840">#72840</a></li> <li>hide stack trace in CanaryOnlyError: <a href="https://github.com/vercel/next.js/tree/HEAD/packages/eslint-config-next/issues/72859">#72859</a></li> <li>Allow missing CacheNodeSeedData during prefetch: <a href="https://github.com/vercel/next.js/tree/HEAD/packages/eslint-config-next/issues/72857">#72857</a></li> <li>Add Segment Cache feature check to <code>prefetch</code> API: <a href="https://github.com/vercel/next.js/tree/HEAD/packages/eslint-config-next/issues/72861">#72861</a></li> </ul> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/vercel/next.js/commit/dafcd43fac3ef9d0ffd94f9c94fd61db4449df25"><code>dafcd43</code></a> v15.1.0</li> <li><a href="https://github.com/vercel/next.js/commit/2deb35d487f20d0e0459b29e313b8f2d4e793fde"><code>2deb35d</code></a> v15.0.4-canary.52</li> <li><a href="https://github.com/vercel/next.js/commit/3970d33e6d4bb055a8596c2b6f7ddbcaa5ca55dc"><code>3970d33</code></a> v15.0.4-canary.51</li> <li><a href="https://github.com/vercel/next.js/commit/c824c183d064f2e3594b2f6dd5db55c134bf18da"><code>c824c18</code></a> v15.0.4-canary.50</li> <li><a href="https://github.com/vercel/next.js/commit/657c2cbd72ebf8f9a58edb4a7393c596246e3161"><code>657c2cb</code></a> v15.0.4-canary.49</li> <li><a href="https://github.com/vercel/next.js/commit/c2078d0c05a03e9fde449a01ff2a10afbdad48bb"><code>c2078d0</code></a> v15.0.4-canary.48</li> <li><a href="https://github.com/vercel/next.js/commit/6b9baaace0ddd75d9c95fe763298522ae93c9d50"><code>6b9baaa</code></a> v15.0.4-canary.47</li> <li><a href="https://github.com/vercel/next.js/commit/2caf05122a23ebb16f561944726be4a493028722"><code>2caf051</code></a> v15.0.4-canary.46</li> <li><a href="https://github.com/vercel/next.js/commit/a6da830de821d584c08a67dbd753ed00bc09c8b7"><code>a6da830</code></a> v15.0.4-canary.45</li> <li><a href="https://github.com/vercel/next.js/commit/85062ae41e5b737ffb2df9722918349749108c67"><code>85062ae</code></a> v15.0.4-canary.44</li> <li>Additional commits viewable in <a href="https://github.com/vercel/next.js/commits/v15.1.0/packages/eslint-config-next">compare view</a></li> </ul> </details> <br /> Updates `tailwindcss` from 3.4.15 to 3.4.16 <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/tailwindlabs/tailwindcss/releases">tailwindcss's releases</a>.</em></p> <blockquote> <h2>v3.4.16</h2> <h3>Fixed</h3> <ul> <li>Ensure the TypeScript types for <code>PluginsConfig</code> allow <code>undefined</code> values (<a href="https://redirect.github.com/tailwindlabs/tailwindcss/pull/14668">#14668</a>)</li> </ul> <h1>Changed</h1> <ul> <li>Bumped lilconfig to v3.x (<a href="https://redirect.github.com/tailwindlabs/tailwindcss/pull/15289">#15289</a>)</li> </ul> </blockquote> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/tailwindlabs/tailwindcss/blob/v3.4.16/CHANGELOG.md">tailwindcss's changelog</a>.</em></p> <blockquote> <h2>[3.4.16] - 2024-12-03</h2> <h3>Fixed</h3> <ul> <li>Ensure the TypeScript types for <code>PluginsConfig</code> allow <code>undefined</code> values (<a href="https://redirect.github.com/tailwindlabs/tailwindcss/pull/14668">#14668</a>)</li> </ul> <h1>Changed</h1> <ul> <li>Bumped lilconfig to v3.x (<a href="https://redirect.github.com/tailwindlabs/tailwindcss/pull/15289">#15289</a>)</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/tailwindlabs/tailwindcss/commit/f875ab9706cae8262e15e5b382580fc8e2d4197f"><code>f875ab9</code></a> Bump macos version</li> <li><a href="https://github.com/tailwindlabs/tailwindcss/commit/8f91c27d3e638d4c7835e2738adfd1e5b62c51c5"><code>8f91c27</code></a> v3.4.16</li> <li><a href="https://github.com/tailwindlabs/tailwindcss/commit/8c8c986e09249fc485e1ba4886c0b76477291b2d"><code>8c8c986</code></a> fix: update lilconfig for ESM and Windows support (<a href="https://redirect.github.com/tailwindlabs/tailwindcss/issues/15289">#15289</a>)</li> <li><a href="https://github.com/tailwindlabs/tailwindcss/commit/2702cfcc2c04f0615f0d53846850cbe769d57262"><code>2702cfc</code></a> Fix Plugin type issue (<a href="https://redirect.github.com/tailwindlabs/tailwindcss/issues/14668">#14668</a>)</li> <li>See full diff in <a href="https://github.com/tailwindlabs/tailwindcss/compare/v3.4.15...v3.4.16">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>
- Loading branch information
1 parent
ab26f3c
commit 22da4f3