mirror of
https://github.com/tailwindlabs/tailwindcss.git
synced 2025-12-08 21:36:08 +00:00
61 Commits
| Author | SHA1 | Message | Date | |
|---|---|---|---|---|
depfu[bot]
|
cf2591c44b
|
Update eslint 9.22.0 → 9.24.0 (minor) (#17656)
Co-authored-by: depfu[bot] <23717796+depfu[bot]@users.noreply.github.com> Co-authored-by: Philipp Spiess <hello@philippspiess.com> |
||
|
depfu[bot]
|
cdecb55702
|
Update @types/react-dom 19.0.4 → 19.1.1 (minor) (#17619) | ||
|
depfu[bot]
|
76e18e679c
|
Update all of react 19.0.0 → 19.1.0 (minor) (#17564)
Here is everything you need to know about this update. Please take a good look at what changed and the test results before merging this pull request. ### What changed? #### ✳️ react (19.0.0 → 19.1.0) · [Repo](https://github.com/facebook/react) · [Changelog](https://github.com/facebook/react/blob/main/CHANGELOG.md) <details> <summary>Release Notes</summary> <h4><a href="https://github.com/facebook/react/releases/tag/v19.1.0">19.1.0</a></h4> <blockquote><h3 dir="auto">Owner Stack</h3> <p dir="auto">An Owner Stack is a string representing the components that are directly responsible for rendering a particular component. You can log Owner Stacks when debugging or use Owner Stacks to enhance error overlays or other development tools. Owner Stacks are only available in development builds. Component Stacks in production are unchanged.</p> <ul dir="auto"> <li>An Owner Stack is a development-only stack trace that helps identify which components are responsible for rendering a particular component. An Owner Stack is distinct from a Component Stacks, which shows the hierarchy of components leading to an error.</li> <li>The <a href="https://react.dev/reference/react/captureOwnerStack">captureOwnerStack API</a> is only available in development mode and returns a Owner Stack, if available. The API can be used to enhance error overlays or log component relationships when debugging. <a href="https://bounce.depfu.com/github.com/facebook/react/pull/29923">#29923</a>, <a href="https://bounce.depfu.com/github.com/facebook/react/pull/32353">#32353</a>, <a href="https://bounce.depfu.com/github.com/facebook/react/pull/30306">#30306</a>,<br> <a href="https://bounce.depfu.com/github.com/facebook/react/pull/32538">#32538</a>, <a href="https://bounce.depfu.com/github.com/facebook/react/pull/32529">#32529</a>, <a href="https://bounce.depfu.com/github.com/facebook/react/pull/32538">#32538</a> </li> </ul> <h3 dir="auto">React</h3> <ul dir="auto"> <li>Enhanced support for Suspense boundaries to be used anywhere, including the client, server, and during hydration. <a href="https://bounce.depfu.com/github.com/facebook/react/pull/32069">#32069</a>, <a href="https://bounce.depfu.com/github.com/facebook/react/pull/32163">#32163</a>, <a href="https://bounce.depfu.com/github.com/facebook/react/pull/32224">#32224</a>, <a href="https://bounce.depfu.com/github.com/facebook/react/pull/32252">#32252</a> </li> <li>Reduced unnecessary client rendering through improved hydration scheduling <a href="https://bounce.depfu.com/github.com/facebook/react/pull/31751">#31751</a> </li> <li>Increased priority of client rendered Suspense boundaries <a href="https://bounce.depfu.com/github.com/facebook/react/pull/31776">#31776</a> </li> <li>Fixed frozen fallback states by rendering unfinished Suspense boundaries on the client. <a href="https://bounce.depfu.com/github.com/facebook/react/pull/31620">#31620</a> </li> <li>Reduced garbage collection pressure by improving Suspense boundary retries. <a href="https://bounce.depfu.com/github.com/facebook/react/pull/31667">#31667</a> </li> <li>Fixed erroneous “Waiting for Paint” log when the passive effect phase was not delayed <a href="https://bounce.depfu.com/github.com/facebook/react/pull/31526">#31526</a> </li> <li>Fixed a regression causing key warnings for flattened positional children in development mode. <a href="https://bounce.depfu.com/github.com/facebook/react/pull/32117">#32117</a> </li> <li>Updated <code class="notranslate">useId</code> to use valid CSS selectors, changing format from <code class="notranslate">:r123:</code> to <code class="notranslate">«r123»</code>. <a href="https://bounce.depfu.com/github.com/facebook/react/pull/32001">#32001</a> </li> <li>Added a dev-only warning for null/undefined created in useEffect, useInsertionEffect, and useLayoutEffect. <a href="https://bounce.depfu.com/github.com/facebook/react/pull/32355">#32355</a> </li> <li>Fixed a bug where dev-only methods were exported in production builds. React.act is no longer available in production builds. <a href="https://bounce.depfu.com/github.com/facebook/react/pull/32200">#32200</a> </li> <li>Improved consistency across prod and dev to improve compatibility with Google Closure Complier and bindings <a href="https://bounce.depfu.com/github.com/facebook/react/pull/31808">#31808</a> </li> <li>Improve passive effect scheduling for consistent task yielding. <a href="https://bounce.depfu.com/github.com/facebook/react/pull/31785">#31785</a> </li> <li>Fixed asserts in React Native when passChildrenWhenCloningPersistedNodes is enabled for OffscreenComponent rendering. <a href="https://bounce.depfu.com/github.com/facebook/react/pull/32528">#32528</a> </li> <li>Fixed component name resolution for Portal <a href="https://bounce.depfu.com/github.com/facebook/react/pull/32640">#32640</a> </li> <li>Added support for beforetoggle and toggle events on the dialog element. <a href="https://bounce.depfu.com/github.com/facebook/react/pull/32479">#32479</a> <a href="https://bounce.depfu.com/github.com/facebook/react/pull/32479">#32479</a> </li> </ul> <h3 dir="auto">React DOM</h3> <ul dir="auto"> <li>Fixed double warning when the <code class="notranslate">href</code> attribute is an empty string <a href="https://bounce.depfu.com/github.com/facebook/react/pull/31783">#31783</a> </li> <li>Fixed an edge case where <code class="notranslate">getHoistableRoot()</code> didn’t work properly when the container was a Document <a href="https://bounce.depfu.com/github.com/facebook/react/pull/32321">#32321</a> </li> <li>Removed support for using HTML comments (e.g. <code class="notranslate"><!-- --></code>) as a DOM container. <a href="https://bounce.depfu.com/github.com/facebook/react/pull/32250">#32250</a> </li> <li>Added support for <code class="notranslate"><script></code> and <code class="notranslate"><template></code> tags to be nested within <code class="notranslate"><select></code> tags. <a href="https://bounce.depfu.com/github.com/facebook/react/pull/31837">#31837</a> </li> <li>Fixed responsive images to be preloaded as HTML instead of headers <a href="https://bounce.depfu.com/github.com/facebook/react/pull/32445">#32445</a> </li> </ul> <h3 dir="auto">use-sync-external-store</h3> <ul dir="auto"> <li>Added <code class="notranslate">exports</code> field to <code class="notranslate">package.json</code> for <code class="notranslate">use-sync-external-store</code> to support various entrypoints. <a href="https://bounce.depfu.com/github.com/facebook/react/pull/25231">#25231</a> </li> </ul> <h3 dir="auto">React Server Components</h3> <ul dir="auto"> <li>Added <code class="notranslate">unstable_prerender</code>, a new experimental API for prerendering React Server Components on the server <a href="https://bounce.depfu.com/github.com/facebook/react/pull/31724">#31724</a> </li> <li>Fixed an issue where streams would hang when receiving new chunks after a global error <a href="https://bounce.depfu.com/github.com/facebook/react/pull/31840">#31840</a>, <a href="https://bounce.depfu.com/github.com/facebook/react/pull/31851">#31851</a> </li> <li>Fixed an issue where pending chunks were counted twice. <a href="https://bounce.depfu.com/github.com/facebook/react/pull/31833">#31833</a> </li> <li>Added support for streaming in edge environments <a href="https://bounce.depfu.com/github.com/facebook/react/pull/31852">#31852</a> </li> <li>Added support for sending custom error names from a server so that they are available in the client for console replaying. <a href="https://bounce.depfu.com/github.com/facebook/react/pull/32116">#32116</a> </li> <li>Updated the server component wire format to remove IDs for hints and console.log because they have no return value <a href="https://bounce.depfu.com/github.com/facebook/react/pull/31671">#31671</a> </li> <li>Exposed <code class="notranslate">registerServerReference</code> in client builds to handle server references in different environments. <a href="https://bounce.depfu.com/github.com/facebook/react/pull/32534">#32534</a> </li> <li>Added react-server-dom-parcel package which integrates Server Components with the <a href="https://parceljs.org/">Parcel bundler</a> <a href="https://bounce.depfu.com/github.com/facebook/react/pull/31725">#31725</a>, <a href="https://bounce.depfu.com/github.com/facebook/react/pull/32132">#32132</a>, <a href="https://bounce.depfu.com/github.com/facebook/react/pull/31799">#31799</a>, <a href="https://bounce.depfu.com/github.com/facebook/react/pull/32294">#32294</a>, <a href="https://bounce.depfu.com/github.com/facebook/react/pull/31741">#31741</a> </li> </ul></blockquote> <p><em>Does any of this look wrong? <a href="https://depfu.com/packages/npm/react/feedback">Please let us know.</a></em></p> </details> <details> <summary>Commits</summary> <p><a href=" |
||
|
depfu[bot]
|
e5b2b0f12c
|
Update bun 1.2.4 → 1.2.8 (patch) (#17527) | ||
Philipp Spiess
|
156afc6d67
|
Improve compatibility with Safari 15 (#17435)
This PR improves the compatibility with Tailwind CSS v4 with unsupported
browsers with the goal to greatly improve compatibility with Safari 15.
To make this work, this PR makes the following changes to all code
- Change `oklab(…)` default theme values to use a percentage in the
first place (so instead of `--color-red-500: oklch(0.637 0.237 25.331);`
we now define it as `--color-red-500: oklch(63.7% 0.237 25.331);` since
this syntax has much broader support on Safari).
- Polyfill `@property` with a `@supports` query targeting older versions
of Safari and Firefox *
- Create fallbacks for the `color-mix(…)` function that use _inlined
color values from your theme_ so that they can be computed a compile
time by `lightningcss`. These fallbacks will convert to srgb to increase
compatibility.
- Create fallbacks for the _relative color_ feature used in the new
shadow utilities and using `color-mix(…)` in case _relative color_ is
applied on `currentcolor` (due to limited browser support)
- Create fallbacks for gradient interpolation methods (e.g. to support
`bg-linear-to-r/oklab`)
- Polyfill `@media` queries range syntax.
## A simplified example
Given this example CSS input:
```css
@import 'tailwindcss';
@source inline('from-cyan-500/50 bg-linear-45');
```
Here's the updated output CSS including the newly added polyfills and
updated `oklab` values:
```css
.bg-linear-45 {
--tw-gradient-position: 45deg;
background-image: linear-gradient(var(--tw-gradient-stops));
}
@supports (background-image: linear-gradient(in lab, red, red)) {
.bg-linear-45 {
--tw-gradient-position: 45deg in oklab;
}
}
.from-cyan-500\\/50 {
--tw-gradient-from: oklab(71.5% -.11682 -.08247 / .5);
--tw-gradient-stops: var(--tw-gradient-via-stops, var(--tw-gradient-position), var(--tw-gradient-from) var(--tw-gradient-from-position), var(--tw-gradient-to) var(--tw-gradient-to-position));
}
@supports (color: color-mix(in lab, red, red)) {
.from-cyan-500\\/50 {
--tw-gradient-from: color-mix(in oklab, var(--color-cyan-500) 50%, transparent);
}
}
:root, :host {
--color-cyan-500: oklch(71.5% .143 215.221);
}
@supports (((-webkit-hyphens: none)) and (not (margin-trim: 1lh))) or ((-moz-orient: inline) and (not (color: rgb(from red r g b)))) {
@layer base {
*, :before, :after, ::backdrop {
--tw-gradient-position: initial;
--tw-gradient-from: #0000;
--tw-gradient-via: #0000;
--tw-gradient-to: #0000;
--tw-gradient-stops: initial;
--tw-gradient-via-stops: initial;
--tw-gradient-from-position: 0%;
--tw-gradient-via-position: 50%;
--tw-gradient-to-position: 100%;
}
}
}
@property --tw-gradient-position {
syntax: "*";
inherits: false
}
@property --tw-gradient-from {
syntax: "<color>";
inherits: false;
initial-value: #0000;
}
@property --tw-gradient-via {
syntax: "<color>";
inherits: false;
initial-value: #0000;
}
@property --tw-gradient-to {
syntax: "<color>";
inherits: false;
initial-value: #0000;
}
@property --tw-gradient-stops {
syntax: "*";
inherits: false
}
@property --tw-gradient-via-stops {
syntax: "*";
inherits: false
}
@property --tw-gradient-from-position {
syntax: "<length-percentage>";
inherits: false;
initial-value: 0%;
}
@property --tw-gradient-via-position {
syntax: "<length-percentage>";
inherits: false;
initial-value: 50%;
}
@property --tw-gradient-to-position {
syntax: "<length-percentage>";
inherits: false;
initial-value: 100%;
}
```
## \* A note on `@property` polyfills and CSS modules
On Next.js, CSS module files are required to be _pure_, meaning that all
selectors must either be scoped to a class or an ID. Fortunatnyl for us,
this does not apply to `@property` rules which we've been using before
to initialize CSS variables.
However, since we're now bringing back the `@property` polyfills, that
would cause unexpected rules to be exported from the CSS file as this:
```css
@reference "tailwindcss";
.skew {
@apply skew-7;
}
```
Would turn to the following file:
```css
.skew {
/* … */
}
@supports (/*…*/) {
@layer base {
*, :before, :after, ::backdrop {
--tw-gradient-position: initial;
}
}
}
@property /* … */
```
Notice that this adds a `*` selector which is not considered pure.
Unfortunately there is no way for us to silence this warning or work
around it, as the dependency causing this errors
([`postcss-modules-local-by-default`](https://github.com/css-modules/postcss-modules-local-by-default))
is bundled into Next.js. To work around crashes, these polyfills will
not apply to CSS modules processed by the PostCSS extension for now.
## Testing on tailwindcss.com
To see the changes in effect, take a look at this screencast that
compares tailwindcss.com on iOS 15.5 with a version that has the patches
of this PR applied:
https://github.com/user-attachments/assets/1279d6f5-3c63-4f30-839c-198a789f4292
## Test plan
- Tested on tailwindcss.com via a preview build:
https://tailwindcss-com-git-legacy-browsers-tailwindlabs.vercel.app/
- Updated tests
- Ensure we also test on Chrome 111, Safari 16.4, Firefox 128 to
make sure we have no regressions. Also tested on Safari 16.4, 15.5, 18.0
|
||
|
depfu[bot]
|
80017ebabe
|
Update all of nextjs 15.2.3 → 15.2.4 (patch) (#17471) | ||
|
depfu[bot]
|
ec2f3bb1ad
|
Update @types/react 19.0.10 → 19.0.12 (patch) (#17377)
Here is everything you need to know about this update. Please take a good look at what changed and the test results before merging this pull request. ### What changed? #### ✳️ @types/react (19.0.10 → 19.0.12) · [Repo](https://github.com/DefinitelyTyped/DefinitelyTyped) Sorry, we couldn't find anything useful about this release. ---  [Depfu](https://depfu.com) will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with `@depfu rebase`. <details><summary>All Depfu comment commands</summary> <blockquote><dl> <dt>@depfu rebase</dt><dd>Rebases against your default branch and redoes this update</dd> <dt>@depfu recreate</dt><dd>Recreates this PR, overwriting any edits that you've made to it</dd> <dt>@depfu merge</dt><dd>Merges this PR once your tests are passing and conflicts are resolved</dd> <dt>@depfu cancel merge</dt><dd>Cancels automatic merging of this PR</dd> <dt>@depfu close</dt><dd>Closes this PR and deletes the branch</dd> <dt>@depfu reopen</dt><dd>Restores the branch and reopens this PR (if it's closed)</dd> <dt>@depfu pause</dt><dd>Ignores all future updates for this dependency and closes this PR</dd> <dt>@depfu pause [minor|major]</dt><dd>Ignores all future minor/major updates for this dependency and closes this PR</dd> <dt>@depfu resume</dt><dd>Future versions of this dependency will create PRs again (leaves this PR as is)</dd> </dl></blockquote> </details> Co-authored-by: depfu[bot] <23717796+depfu[bot]@users.noreply.github.com> |
||
|
depfu[bot]
|
1c481b81c7
|
Update all of nextjs 15.2.1 → 15.2.3 (patch) (#17337) | ||
|
depfu[bot]
|
1a88518d80
|
Update autoprefixer 10.4.20 → 10.4.21 (patch) (#17229) | ||
|
depfu[bot]
|
6b2b26287c
|
Update eslint 9.20.1 → 9.22.0 (minor) (#17207) | ||
|
depfu[bot]
|
5e2633bb6d
|
Update all of nextjs 15.1.7 → 15.2.1 (minor) (#17118) | ||
|
depfu[bot]
|
13acd24830
|
Update bun 1.2.3 → 1.2.4 (patch) (#16954) | ||
Jordan Pittman
|
662c6862ac
|
Make JS APIs available to plugins and configs in the Standalone CLI (#15934)
This PR ensures we bundle the relevant JS APIs in the Standalone CLI like `tailwindcss`, `tailwindcss/plugin`, `tailwindcss/colors`, etc… Before, when loading plugins or configs, imports for those resources would fail. Fixes #15235 --------- Co-authored-by: Philipp Spiess <hello@philippspiess.com> |
||
|
depfu[bot]
|
37ea0c3493
|
Update @types/react 19.0.8 → 19.0.10 (patch) (#16775) | ||
|
depfu[bot]
|
a893de22ba
|
Update @types/react-dom 19.0.3 → 19.0.4 (patch) (#16773) | ||
|
depfu[bot]
|
604be562e3
|
Update eslint 9.19.0 → 9.20.1 (minor) (#16726)
Here is everything you need to know about this update. Please take a good look at what changed and the test results before merging this pull request. ### What changed? #### ✳️ eslint (9.19.0 → 9.20.1) · [Repo](https://github.com/eslint/eslint) · [Changelog](https://github.com/eslint/eslint/blob/main/CHANGELOG.md) <details> <summary>Release Notes</summary> <h4><a href="https://github.com/eslint/eslint/releases/tag/v9.20.1">9.20.1</a></h4> <blockquote><h2 dir="auto">Bug Fixes</h2> <ul dir="auto"> <li> <a href=" |
||
|
depfu[bot]
|
61af484ff4
|
Update all of nextjs 15.1.6 → 15.1.7 (patch) (#16654) | ||
|
depfu[bot]
|
f678a7025f
|
Update @types/react 19.0.7 → 19.0.8 (patch) (#16423) | ||
|
depfu[bot]
|
1f84241f21
|
Update eslint 9.18.0 → 9.19.0 (minor) (#16357)
Here is everything you need to know about this update. Please take a good look at what changed and the test results before merging this pull request. ### What changed? #### ✳️ eslint (9.18.0 → 9.19.0) · [Repo](https://github.com/eslint/eslint) · [Changelog](https://github.com/eslint/eslint/blob/main/CHANGELOG.md) <details> <summary>Release Notes</summary> <h4><a href="https://github.com/eslint/eslint/releases/tag/v9.19.0">9.19.0</a></h4> <blockquote><h2 dir="auto">Features</h2> <ul dir="auto"> <li> <a href=" |
||
|
depfu[bot]
|
0ecc22b5cc
|
Update all of nextjs 15.1.4 → 15.1.6 (patch) (#16257) | ||
|
Philipp Spiess
|
9fd6766308
|
Ensure first argument to var(…) still unescapes \_ (#16206)
Resolves #16170 This PR fixes an issue where the previously opted-out escaping of the first argument for the `var(…)` function was not unescaped at all. This was introduced in https://github.com/tailwindlabs/tailwindcss/pull/14776 where the intention was to not require escaping of underscores in the var function (e.g. `ml-[var(--spacing-1_5)]`). However, I do think it still makes sense to unescape an eventually escaped underline for consistency. ## Test plan The example from #1670 now parses as expected: <img width="904" alt="Screenshot 2025-02-03 at 13 51 35" src="https://github.com/user-attachments/assets/cac0f06e-37da-4dcb-a554-9606d144a8d5" /> --------- Co-authored-by: Robin Malfait <malfait.robin@gmail.com> |
||
|
depfu[bot]
|
b009afa4ae
|
Update @types/react-dom 19.0.2 → 19.0.3 (patch) (#15669)
Here is everything you need to know about this update. Please take a good look at what changed and the test results before merging this pull request. ### What changed? #### ✳️ @types/react-dom (19.0.2 → 19.0.3) · [Repo](https://github.com/DefinitelyTyped/DefinitelyTyped) Sorry, we couldn't find anything useful about this release. ---  [Depfu](https://depfu.com) will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with `@depfu rebase`. <details><summary>All Depfu comment commands</summary> <blockquote><dl> <dt>@depfu rebase</dt><dd>Rebases against your default branch and redoes this update</dd> <dt>@depfu recreate</dt><dd>Recreates this PR, overwriting any edits that you've made to it</dd> <dt>@depfu merge</dt><dd>Merges this PR once your tests are passing and conflicts are resolved</dd> <dt>@depfu cancel merge</dt><dd>Cancels automatic merging of this PR</dd> <dt>@depfu close</dt><dd>Closes this PR and deletes the branch</dd> <dt>@depfu reopen</dt><dd>Restores the branch and reopens this PR (if it's closed)</dd> <dt>@depfu pause</dt><dd>Ignores all future updates for this dependency and closes this PR</dd> <dt>@depfu pause [minor|major]</dt><dd>Ignores all future minor/major updates for this dependency and closes this PR</dd> <dt>@depfu resume</dt><dd>Future versions of this dependency will create PRs again (leaves this PR as is)</dd> </dl></blockquote> </details> Co-authored-by: depfu[bot] <23717796+depfu[bot]@users.noreply.github.com> |
||
|
depfu[bot]
|
e1c084c1b1
|
Update all of nextjs 15.1.3 → 15.1.4 (patch) (#15630)
Here is everything you need to know about this update. Please take a good look at what changed and the test results before merging this pull request. ### What changed? #### ✳️ eslint-config-next (15.1.3 → 15.1.4) Sorry, we couldn't find anything useful about this release. #### ✳️ next (15.1.3 → 15.1.4) · [Repo](https://github.com/vercel/next.js) <details> <summary>Release Notes</summary> <h4><a href="https://github.com/vercel/next.js/releases/tag/v15.1.4">15.1.4</a></h4> <blockquote><div class="markdown-alert markdown-alert-note" dir="auto"> <p class="markdown-alert-title" dir="auto"><svg class="octicon octicon-info mr-2" viewbox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path d="M0 8a8 8 0 1 1 16 0A8 8 0 0 1 0 8Zm8-6.5a6.5 6.5 0 1 0 0 13 6.5 6.5 0 0 0 0-13ZM6.5 7.75A.75.75 0 0 1 7.25 7h1a.75.75 0 0 1 .75.75v2.75h.25a.75.75 0 0 1 0 1.5h-2a.75.75 0 0 1 0-1.5h.25v-2h-.25a.75.75 0 0 1-.75-.75ZM8 6a1 1 0 1 1 0-2 1 1 0 0 1 0 2Z"></path></svg>Note</p> <p dir="auto">This release is backporting bug fixes. It does <strong>not</strong> include all pending features/changes on canary.</p> </div> <h3 dir="auto">Core Changes</h3> <ul dir="auto"> <li>backport: force module format for virtual client-proxy (<a href="https://bounce.depfu.com/github.com/vercel/next.js/pull/74608">#74608</a>)</li> <li>Fix prerender tags when notFound is called (<a href="https://bounce.depfu.com/github.com/vercel/next.js/pull/74607">#74607</a>)</li> <li>Use provided waitUntil for pending revalidates (<a href="https://bounce.depfu.com/github.com/vercel/next.js/pull/74604">#74604</a>)</li> <li>Feature: next/image: add support for images.qualities in next.config (<a href="https://bounce.depfu.com/github.com/vercel/next.js/pull/74588">#74588</a>)</li> <li>Chore: docs: add missing search: '' on remotePatterns (<a href="https://bounce.depfu.com/github.com/vercel/next.js/pull/74587">#74587</a>)</li> <li>Chore: docs: update version history of next/image (<a href="https://bounce.depfu.com/github.com/vercel/next.js/pull/73923">#73923</a>) (<a href="https://bounce.depfu.com/github.com/vercel/next.js/pull/74570">#74570</a>)</li> <li>Chore: next/image: improve imgopt api bypass detection for unsupported images (<a href="https://bounce.depfu.com/github.com/vercel/next.js/pull/74569">#74569</a>)</li> </ul> <h3 dir="auto">Credits</h3> <p dir="auto">Huge thanks to @ and @ for helping!</p></blockquote> <p><em>Does any of this look wrong? <a href="https://depfu.com/packages/npm/next/feedback">Please let us know.</a></em></p> </details> <details> <summary>Commits</summary> <p><a href=" |
||
|
depfu[bot]
|
a707fed089
|
Update eslint 9.17.0 → 9.18.0 (minor) (#15664) | ||
|
depfu[bot]
|
14fea72016
|
Update @types/react 19.0.2 → 19.0.7 (patch) (#15682) | ||
|
depfu[bot]
|
ae8fb146a7
|
Update fast-glob 3.3.2 → 3.3.3 (patch) (#15607) | ||
|
depfu[bot]
|
27f8bab7ab
|
Update @types/react 18.3.12 → 19.0.2 (major) (#15588)
Here is everything you need to know about this upgrade. Please take a good look at what changed and the test results before merging this pull request. ### What changed? #### ✳️ @types/react (18.3.12 → 19.0.2) · [Repo](https://github.com/DefinitelyTyped/DefinitelyTyped) Sorry, we couldn't find anything useful about this release. ---  [Depfu](https://depfu.com) will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with `@depfu rebase`. <details><summary>All Depfu comment commands</summary> <blockquote><dl> <dt>@depfu rebase</dt><dd>Rebases against your default branch and redoes this update</dd> <dt>@depfu recreate</dt><dd>Recreates this PR, overwriting any edits that you've made to it</dd> <dt>@depfu merge</dt><dd>Merges this PR once your tests are passing and conflicts are resolved</dd> <dt>@depfu cancel merge</dt><dd>Cancels automatic merging of this PR</dd> <dt>@depfu close</dt><dd>Closes this PR and deletes the branch</dd> <dt>@depfu reopen</dt><dd>Restores the branch and reopens this PR (if it's closed)</dd> <dt>@depfu pause</dt><dd>Ignores all future updates for this dependency and closes this PR</dd> <dt>@depfu pause [minor|major]</dt><dd>Ignores all future minor/major updates for this dependency and closes this PR</dd> <dt>@depfu resume</dt><dd>Future versions of this dependency will create PRs again (leaves this PR as is)</dd> </dl></blockquote> </details> Co-authored-by: depfu[bot] <23717796+depfu[bot]@users.noreply.github.com> |
||
|
depfu[bot]
|
def9bf3406
|
Update all of react 18.3.1 → 19.0.0 (major) (#15586)
Here is everything you need to know about this upgrade. Please take a good look at what changed and the test results before merging this pull request. ### What changed? #### ✳️ react (18.3.1 → 19.0.0) · [Repo](https://github.com/facebook/react) · [Changelog](https://github.com/facebook/react/blob/main/CHANGELOG.md) <details> <summary>Release Notes</summary> <h4><a href="https://github.com/facebook/react/releases/tag/v19.0.0">19.0.0</a></h4> <blockquote><em>More info than we can show here.</em></blockquote> <p><em>Does any of this look wrong? <a href="https://depfu.com/packages/npm/react/feedback">Please let us know.</a></em></p> </details> <details> <summary>Commits</summary> <p><a href=" |
||
|
depfu[bot]
|
501c59f7aa
|
Update @types/react-dom 18.3.1 → 19.0.2 (major) (#15587)
Here is everything you need to know about this upgrade. Please take a good look at what changed and the test results before merging this pull request. ### What changed? #### ✳️ @types/react-dom (18.3.1 → 19.0.2) · [Repo](https://github.com/DefinitelyTyped/DefinitelyTyped) Sorry, we couldn't find anything useful about this release. ---  [Depfu](https://depfu.com) will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with `@depfu rebase`. <details><summary>All Depfu comment commands</summary> <blockquote><dl> <dt>@depfu rebase</dt><dd>Rebases against your default branch and redoes this update</dd> <dt>@depfu recreate</dt><dd>Recreates this PR, overwriting any edits that you've made to it</dd> <dt>@depfu merge</dt><dd>Merges this PR once your tests are passing and conflicts are resolved</dd> <dt>@depfu cancel merge</dt><dd>Cancels automatic merging of this PR</dd> <dt>@depfu close</dt><dd>Closes this PR and deletes the branch</dd> <dt>@depfu reopen</dt><dd>Restores the branch and reopens this PR (if it's closed)</dd> <dt>@depfu pause</dt><dd>Ignores all future updates for this dependency and closes this PR</dd> <dt>@depfu pause [minor|major]</dt><dd>Ignores all future minor/major updates for this dependency and closes this PR</dd> <dt>@depfu resume</dt><dd>Future versions of this dependency will create PRs again (leaves this PR as is)</dd> </dl></blockquote> </details> Co-authored-by: depfu[bot] <23717796+depfu[bot]@users.noreply.github.com> |
||
|
depfu[bot]
|
2cc4864a79
|
Update eslint 9.15.0 → 9.17.0 (minor) (#15584)
Here is everything you need to know about this update. Please take a good look at what changed and the test results before merging this pull request. ### What changed? #### ✳️ eslint (9.15.0 → 9.17.0) · [Repo](https://github.com/eslint/eslint) · [Changelog](https://github.com/eslint/eslint/blob/main/CHANGELOG.md) <details> <summary>Release Notes</summary> <h4><a href="https://github.com/eslint/eslint/releases/tag/v9.17.0">9.17.0</a></h4> <blockquote><h2 dir="auto">Features</h2> <ul dir="auto"> <li> <a href=" |
||
|
depfu[bot]
|
cd15caa846
|
🚨 [security] Update all of nextjs 15.1.0 → 15.1.3 (patch) (#15535)
<hr> 🚨 <b>Your current dependencies have known security vulnerabilities</b> 🚨 This dependency update fixes known security vulnerabilities. Please see the details below and assess their impact carefully. We recommend to merge and deploy this as soon as possible! <hr> Here is everything you need to know about this update. Please take a good look at what changed and the test results before merging this pull request. ### What changed? #### ✳️ eslint-config-next (15.1.0 → 15.1.3) Sorry, we couldn't find anything useful about this release. #### ✳️ next (15.1.0 → 15.1.3) · [Repo](https://github.com/vercel/next.js) <details> <summary>Security Advisories 🚨</summary> <h4><a href="https://bounce.depfu.com/github.com/vercel/next.js/security/advisories/GHSA-7m27-7ghc-44w9">🚨 Next.js Allows a Denial of Service (DoS) with Server Actions</a></h4> <blockquote><h3 dir="auto">Impact</h3> <p dir="auto">A Denial of Service (DoS) attack allows attackers to construct requests that leaves requests to Server Actions hanging until the hosting provider cancels the function execution.</p> <p dir="auto"><em>Note: Next.js server is idle during that time and only keeps the connection open. CPU and memory footprint are low during that time.</em></p> <p dir="auto">Deployments without any protection against long running Server Action invocations are especially vulnerable. Hosting providers like Vercel or Netlify set a default maximum duration on function execution to reduce the risk of excessive billing.</p> <p dir="auto">This is the same issue as if the incoming HTTP request has an invalid <code class="notranslate">Content-Length</code> header or never closes. If the host has no other mitigations to those then this vulnerability is novel.</p> <p dir="auto">This vulnerability affects only Next.js deployments using Server Actions.</p> <h3 dir="auto">Patches</h3> <p dir="auto">This vulnerability was resolved in Next.js 14.2.21, 15.1.2, and 13.5.8. We recommend that users upgrade to a safe version.</p> <h3 dir="auto">Workarounds</h3> <p dir="auto">There are no official workarounds for this vulnerability.</p> <h3 dir="auto">Credits</h3> <p dir="auto">Thanks to the PackDraw team for responsibly disclosing this vulnerability.</p></blockquote> </details> <details> <summary>Release Notes</summary> <h4><a href="https://github.com/vercel/next.js/releases/tag/v15.1.3">15.1.3</a></h4> <blockquote><div class="markdown-alert markdown-alert-note" dir="auto"> <p class="markdown-alert-title" dir="auto"><svg class="octicon octicon-info mr-2" viewbox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path d="M0 8a8 8 0 1 1 16 0A8 8 0 0 1 0 8Zm8-6.5a6.5 6.5 0 1 0 0 13 6.5 6.5 0 0 0 0-13ZM6.5 7.75A.75.75 0 0 1 7.25 7h1a.75.75 0 0 1 .75.75v2.75h.25a.75.75 0 0 1 0 1.5h-2a.75.75 0 0 1 0-1.5h.25v-2h-.25a.75.75 0 0 1-.75-.75ZM8 6a1 1 0 1 1 0-2 1 1 0 0 1 0 2Z"></path></svg>Note</p> <p dir="auto">This release is backporting bug fixes. It does <strong>not</strong> include all pending features/changes on canary.</p> </div> <h3 dir="auto">Core Changes</h3> <ul dir="auto"> <li>Retry manifest file loading only in dev mode: <a href="https://bounce.depfu.com/github.com/vercel/next.js/pull/73900">#73900</a> </li> <li>Use shared worker for lint & typecheck steps: <a href="https://bounce.depfu.com/github.com/vercel/next.js/pull/74154">#74154</a> </li> </ul> <h3 dir="auto">Credits</h3> <p dir="auto">Huge thanks to <a href="https://bounce.depfu.com/github.com/unstubbable">@unstubbable</a> and <a href="https://bounce.depfu.com/github.com/ztanner">@ztanner</a> for helping!</p></blockquote> <h4><a href="https://github.com/vercel/next.js/releases/tag/v15.1.2">15.1.2</a></h4> <blockquote><div class="markdown-alert markdown-alert-note" dir="auto"> <p class="markdown-alert-title" dir="auto"><svg class="octicon octicon-info mr-2" viewbox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path d="M0 8a8 8 0 1 1 16 0A8 8 0 0 1 0 8Zm8-6.5a6.5 6.5 0 1 0 0 13 6.5 6.5 0 0 0 0-13ZM6.5 7.75A.75.75 0 0 1 7.25 7h1a.75.75 0 0 1 .75.75v2.75h.25a.75.75 0 0 1 0 1.5h-2a.75.75 0 0 1 0-1.5h.25v-2h-.25a.75.75 0 0 1-.75-.75ZM8 6a1 1 0 1 1 0-2 1 1 0 0 1 0 2Z"></path></svg>Note</p> <p dir="auto">This release is backporting bug fixes. It does <strong>not</strong> include all pending features/changes on canary.</p> </div> <h3 dir="auto">Core Changes</h3> <ul dir="auto"> <li>Update React from 7283a213-20241206 to 65e06cb7-20241218: <a href="https://bounce.depfu.com/github.com/vercel/next.js/pull/74117">#74117</a> </li> </ul> <h3 dir="auto">Credits</h3> <p dir="auto">Huge thanks to <a href="https://bounce.depfu.com/github.com/ztanner">@ztanner</a> for helping!</p></blockquote> <h4><a href="https://github.com/vercel/next.js/releases/tag/v15.1.1">15.1.1</a></h4> <blockquote><div class="markdown-alert markdown-alert-note" dir="auto"> <p class="markdown-alert-title" dir="auto"><svg class="octicon octicon-info mr-2" viewbox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path d="M0 8a8 8 0 1 1 16 0A8 8 0 0 1 0 8Zm8-6.5a6.5 6.5 0 1 0 0 13 6.5 6.5 0 0 0 0-13ZM6.5 7.75A.75.75 0 0 1 7.25 7h1a.75.75 0 0 1 .75.75v2.75h.25a.75.75 0 0 1 0 1.5h-2a.75.75 0 0 1 0-1.5h.25v-2h-.25a.75.75 0 0 1-.75-.75ZM8 6a1 1 0 1 1 0-2 1 1 0 0 1 0 2Z"></path></svg>Note</p> <p dir="auto">This release is backporting bug fixes. It does <strong>not</strong> include all pending features/changes on canary.</p> </div> <h3 dir="auto">Core Changes</h3> <ul dir="auto"> <li>fix(turbo): sassOptions silenceDeprecations was not overwritten with user options: <a href="https://bounce.depfu.com/github.com/vercel/next.js/pull/73937">#73937</a> </li> <li>refactor collectAppPageSegments: <a href="https://bounce.depfu.com/github.com/vercel/next.js/pull/73908">#73908</a> </li> </ul> <h3 dir="auto">Credits</h3> <p dir="auto">Huge thanks to <a href="https://bounce.depfu.com/github.com/devjiwonchoi">@devjiwonchoi</a> and <a href="https://bounce.depfu.com/github.com/ztanner">@ztanner</a> for helping!</p></blockquote> <p><em>Does any of this look wrong? <a href="https://depfu.com/packages/npm/next/feedback">Please let us know.</a></em></p> </details> <details> <summary>Commits</summary> <p><a href=" |
||
|
depfu[bot]
|
bca432ed99
|
Update all of nextjs 15.0.3 → 15.1.0 (minor) (#15536)
Here is everything you need to know about this update. Please take a
good look at what changed and the test results before merging this pull
request.
### What changed?
#### ✳️ eslint-config-next (15.0.3 → 15.1.0)
Sorry, we couldn't find anything useful about this release.
#### ✳️ next (15.0.3 → 15.1.0) ·
[Repo](https://github.com/vercel/next.js)
<details>
<summary>Release Notes</summary>
<h4><a
href="https://github.com/vercel/next.js/releases/tag/v15.1.0">15.1.0</a></h4>
<blockquote><em>More info than we can show here.</em></blockquote>
<h4><a
href="https://github.com/vercel/next.js/releases/tag/v15.0.4">15.0.4</a></h4>
<blockquote><em>More info than we can show here.</em></blockquote>
<p><em>Does any of this look wrong? <a
href="https://depfu.com/packages/npm/next/feedback">Please let us
know.</a></em></p>
</details>
<details>
<summary>Commits</summary>
<p><a
href="
|
||
|
depfu[bot]
|
34340e3b82
|
Update @vitejs/plugin-react 4.3.1 → 4.3.4 (patch) (#15453)
Here is everything you need to know about this update. Please take a good look at what changed and the test results before merging this pull request. ### What changed? #### ✳️ @vitejs/plugin-react (4.3.1 → 4.3.4) · [Repo](https://github.com/vitejs/vite) · [Changelog](https://github.com/vitejs/vite/blob/main/packages/plugin-react/CHANGELOG.md) <details> <summary>Release Notes</summary> <h4><a href="https://github.com/vitejs/vite/releases/tag/v4.3.4">4.3.4</a></h4> <blockquote><p dir="auto">Please refer to <a href="https://bounce.depfu.com/github.com/vitejs/vite/blob/v4.3.4/packages/vite/CHANGELOG.md">CHANGELOG.md</a> for details.</p></blockquote> <h4><a href="https://github.com/vitejs/vite/releases/tag/v4.3.3">4.3.3</a></h4> <blockquote><p dir="auto">Please refer to <a href="https://bounce.depfu.com/github.com/vitejs/vite/blob/v4.3.3/packages/vite/CHANGELOG.md">CHANGELOG.md</a> for details.</p></blockquote> <h4><a href="https://github.com/vitejs/vite/releases/tag/v4.3.2">4.3.2</a></h4> <blockquote><p dir="auto">Please refer to <a href="https://bounce.depfu.com/github.com/vitejs/vite/blob/v4.3.2/packages/vite/CHANGELOG.md">CHANGELOG.md</a> for details.</p></blockquote> <p><em>Does any of this look wrong? <a href="https://depfu.com/packages/npm/@vitejs%2Fplugin-react/feedback">Please let us know.</a></em></p> </details> ---  [Depfu](https://depfu.com) will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with `@depfu rebase`. <details><summary>All Depfu comment commands</summary> <blockquote><dl> <dt>@depfu rebase</dt><dd>Rebases against your default branch and redoes this update</dd> <dt>@depfu recreate</dt><dd>Recreates this PR, overwriting any edits that you've made to it</dd> <dt>@depfu merge</dt><dd>Merges this PR once your tests are passing and conflicts are resolved</dd> <dt>@depfu cancel merge</dt><dd>Cancels automatic merging of this PR</dd> <dt>@depfu close</dt><dd>Closes this PR and deletes the branch</dd> <dt>@depfu reopen</dt><dd>Restores the branch and reopens this PR (if it's closed)</dd> <dt>@depfu pause</dt><dd>Ignores all future updates for this dependency and closes this PR</dd> <dt>@depfu pause [minor|major]</dt><dd>Ignores all future minor/major updates for this dependency and closes this PR</dd> <dt>@depfu resume</dt><dd>Future versions of this dependency will create PRs again (leaves this PR as is)</dd> </dl></blockquote> </details> Co-authored-by: depfu[bot] <23717796+depfu[bot]@users.noreply.github.com> |
||
|
depfu[bot]
|
f9355a3493
|
Update eslint 9.11.1 → 9.15.0 (minor) (#15123) | ||
|
depfu[bot]
|
8ae8f65f86
|
Update all of nextjs 14.1.0 → 15.0.3 (major) (#15200) | ||
Adam Wathan
|
0d0ce2ca42 | WIP | ||
|
Adam Wathan
|
a8b99f76f4 | Fix Vite playground warnings | ||
|
Philipp Spiess
|
98c279d1fb
|
Don't create bare spacing utilities with invalid multiples (#14962)
Closes #14960 When we moved to the `--spacing` multiples scale, we seemingly overlooked a bail that caused us to use non-numerical values as a spacing multiple. This caused the `-translate-x-full` and `-translate-y-full` utilities to treat `full` as a valid multiple in our spacing scale and created invalid CSS: ```css .-translate-x-full { --tw-translate-x: calc(var(--spacing) * -x-full); --tw-translate-y: calc(var(--spacing) * -x-full); translate: var(--tw-translate-x) var(--tw-translate-y); } ``` ## Test plan I reproduced the issue in our Vite playground and then created a failing test case. It requires a `--spacing` `@theme` variable to be defined so I've added this as a test case now in the unit tests. I also audited all places that are using `calc()` and wrapping some numbers. In doing so I found a few other broken cases: - `-translate-x-full` - `-translate-y-full` - `-space-x-full` - `-space-y-full` - `-inset-full` I validated that the fix indeed works and no longer creates broken CSS definitions for these cases: <kbd><img width="1405" alt="Screenshot 2024-11-11 at 19 33 51" src="https://github.com/user-attachments/assets/99072112-9ed4-4456-bad8-5679679e7198"></kbd> --------- Co-authored-by: Adam Wathan <adam.wathan@gmail.com> |
||
|
depfu[bot]
|
42430bcaed
|
Update @types/react 18.3.11 → 18.3.12 (patch) (#14832) | ||
|
Jordan Pittman
|
e52bf2eca8 |
Revert "Update bun 1.1.29 → 1.1.33 (patch) (#14813)"
This reverts commit 9b7b4a683c880c453103a40421dd503a41e3826c. |
||
|
depfu[bot]
|
9b7b4a683c
|
Update bun 1.1.29 → 1.1.33 (patch) (#14813)
<!--depfu-start--> > 👉 **This PR is queued up to get rebased by Depfu** <!--depfu-end--> Here is everything you need to know about this update. Please take a good look at what changed and the test results before merging this pull request. ### What changed? #### ✳️ bun (1.1.29 → 1.1.33) · [Repo](https://github.com/oven-sh/bun) Sorry, we couldn't find anything useful about this release. ---  [Depfu](https://depfu.com) will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with `@depfu rebase`. <details><summary>All Depfu comment commands</summary> <blockquote><dl> <dt>@depfu rebase</dt><dd>Rebases against your default branch and redoes this update</dd> <dt>@depfu recreate</dt><dd>Recreates this PR, overwriting any edits that you've made to it</dd> <dt>@depfu merge</dt><dd>Merges this PR once your tests are passing and conflicts are resolved</dd> <dt>@depfu cancel merge</dt><dd>Cancels automatic merging of this PR</dd> <dt>@depfu close</dt><dd>Closes this PR and deletes the branch</dd> <dt>@depfu reopen</dt><dd>Restores the branch and reopens this PR (if it's closed)</dd> <dt>@depfu pause</dt><dd>Ignores all future updates for this dependency and closes this PR</dd> <dt>@depfu pause [minor|major]</dt><dd>Ignores all future minor/major updates for this dependency and closes this PR</dd> <dt>@depfu resume</dt><dd>Future versions of this dependency will create PRs again (leaves this PR as is)</dd> </dl></blockquote> </details> Co-authored-by: depfu[bot] <23717796+depfu[bot]@users.noreply.github.com> |
||
Adam Wathan
|
39cfcfa427
|
Register migrateImport to ensure it actually runs (#14769)
This PR makes sure the `migrateImport` codemod is properly registered so that it runs as part of the upgrade process. ## Test plan This PR adds a new `v3` playground with an `upgrade` script that you can use to run the upgrade from the local package. When you add a non-prefixed `@import` to the v3 example, the paths are now properly updated with no errors logged: https://github.com/user-attachments/assets/85949bbb-756b-4ee2-8ac0-234fe1b2ca39 --------- Co-authored-by: Adam Wathan <4323180+adamwathan@users.noreply.github.com> Co-authored-by: Philipp Spiess <hello@philippspiess.com> |
||
|
depfu[bot]
|
3f2ff03fc0
|
Update @types/react 18.3.9 → 18.3.11 (patch) (#14756) | ||
philipp-spiess
|
d59f1b3e5d |
Vite: Fix issues when loading files via static asset queries (#14716)
Fixes: #14558 This PR fixes an issue where our Vite plugin would crash when trying to load stylesheets via certain static asset query parameters: ```ts import raw from './style.css?raw' import url from './style.css?url' ``` The proper behavior for our extension is to _not touch these file at all_. The `?raw` identifier should never transform anything and the `?url` one will emit a module which points to the asset URL. However, if that URL is loaded as a stylesheet, another transform hook is called and the file is properly transformed. I verified this in the Vite setup and have added an integration test ensuring these two features work as expected. I've also greatly reduced the complexity of the Vite playground to make it easier to set up examples like this in the future. |
||
|
depfu[bot]
|
84200e2c89
|
Update @types/react-dom 18.3.0 → 18.3.1 (patch) (#14728)
Here is everything you need to know about this update. Please take a good look at what changed and the test results before merging this pull request. ### What changed? #### ✳️ @types/react-dom (18.3.0 → 18.3.1) · [Repo](https://github.com/DefinitelyTyped/DefinitelyTyped) Sorry, we couldn't find anything useful about this release. ---  [Depfu](https://depfu.com) will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with `@depfu rebase`. <details><summary>All Depfu comment commands</summary> <blockquote><dl> <dt>@depfu rebase</dt><dd>Rebases against your default branch and redoes this update</dd> <dt>@depfu recreate</dt><dd>Recreates this PR, overwriting any edits that you've made to it</dd> <dt>@depfu merge</dt><dd>Merges this PR once your tests are passing and conflicts are resolved</dd> <dt>@depfu cancel merge</dt><dd>Cancels automatic merging of this PR</dd> <dt>@depfu close</dt><dd>Closes this PR and deletes the branch</dd> <dt>@depfu reopen</dt><dd>Restores the branch and reopens this PR (if it's closed)</dd> <dt>@depfu pause</dt><dd>Ignores all future updates for this dependency and closes this PR</dd> <dt>@depfu pause [minor|major]</dt><dd>Ignores all future minor/major updates for this dependency and closes this PR</dd> <dt>@depfu resume</dt><dd>Future versions of this dependency will create PRs again (leaves this PR as is)</dd> </dl></blockquote> </details> Co-authored-by: depfu[bot] <23717796+depfu[bot]@users.noreply.github.com> |
||
|
depfu[bot]
|
5179fafdc3
|
Update eslint 8.57.0 → 9.11.1 (major) (#14547)
Here is everything you need to know about this upgrade. Please take a
good look at what changed and the test results before merging this pull
request.
### What changed?
#### ✳️ eslint (8.57.0 → 9.11.1) ·
[Repo](https://github.com/eslint/eslint) ·
[Changelog](https://github.com/eslint/eslint/blob/main/CHANGELOG.md)
<details>
<summary>Release Notes</summary>
<p><em>Too many releases to show here. View the <a
href="https://github.com/eslint/eslint/blob/main/CHANGELOG.md">full
release notes</a>.</em></p>
</details>
<details>
<summary>Commits</summary>
<p><a
href="
|
||
|
depfu[bot]
|
1d1fd46844
|
Update bun 1.1.26 → 1.1.29 (patch) (#14608)
Here is everything you need to know about this update. Please take a good look at what changed and the test results before merging this pull request. ### What changed? #### ✳️ bun (1.1.22 → 1.1.29) · [Repo](https://github.com/oven-sh/bun) Sorry, we couldn't find anything useful about this release. ---  [Depfu](https://depfu.com) will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with `@depfu rebase`. <details><summary>All Depfu comment commands</summary> <blockquote><dl> <dt>@depfu rebase</dt><dd>Rebases against your default branch and redoes this update</dd> <dt>@depfu recreate</dt><dd>Recreates this PR, overwriting any edits that you've made to it</dd> <dt>@depfu merge</dt><dd>Merges this PR once your tests are passing and conflicts are resolved</dd> <dt>@depfu cancel merge</dt><dd>Cancels automatic merging of this PR</dd> <dt>@depfu close</dt><dd>Closes this PR and deletes the branch</dd> <dt>@depfu reopen</dt><dd>Restores the branch and reopens this PR (if it's closed)</dd> <dt>@depfu pause</dt><dd>Ignores all future updates for this dependency and closes this PR</dd> <dt>@depfu pause [minor|major]</dt><dd>Ignores all future minor/major updates for this dependency and closes this PR</dd> <dt>@depfu resume</dt><dd>Future versions of this dependency will create PRs again (leaves this PR as is)</dd> </dl></blockquote> </details> Co-authored-by: depfu[bot] <23717796+depfu[bot]@users.noreply.github.com> |
||
|
depfu[bot]
|
9030879f1b
|
Update @types/react 18.3.3 → 18.3.9 (patch) (#14532)
Here is everything you need to know about this update. Please take a good look at what changed and the test results before merging this pull request. ### What changed? #### ✳️ @types/react (18.3.3 → 18.3.9) · [Repo](https://github.com/DefinitelyTyped/DefinitelyTyped) Sorry, we couldn't find anything useful about this release. ---  [Depfu](https://depfu.com) will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with `@depfu rebase`. <details><summary>All Depfu comment commands</summary> <blockquote><dl> <dt>@depfu rebase</dt><dd>Rebases against your default branch and redoes this update</dd> <dt>@depfu recreate</dt><dd>Recreates this PR, overwriting any edits that you've made to it</dd> <dt>@depfu merge</dt><dd>Merges this PR once your tests are passing and conflicts are resolved</dd> <dt>@depfu cancel merge</dt><dd>Cancels automatic merging of this PR</dd> <dt>@depfu close</dt><dd>Closes this PR and deletes the branch</dd> <dt>@depfu reopen</dt><dd>Restores the branch and reopens this PR (if it's closed)</dd> <dt>@depfu pause</dt><dd>Ignores all future updates for this dependency and closes this PR</dd> <dt>@depfu pause [minor|major]</dt><dd>Ignores all future minor/major updates for this dependency and closes this PR</dd> <dt>@depfu resume</dt><dd>Future versions of this dependency will create PRs again (leaves this PR as is)</dd> </dl></blockquote> </details> Co-authored-by: depfu[bot] <23717796+depfu[bot]@users.noreply.github.com> |
||
|
Philipp Spiess
|
ab8972749c
|
Postcss: Bring back proper type exports (#14256)
Closes #14253 Since we changed the export strategy for the postcss client in #14132, we accidentally no longer generated type exports for this package. This PR adds a type export back. We now use a similar pattern to the `./colors` and `./defaultTheme` exports in the tailwindcss package where we have a separate cjs entrypoint. The changes were validated manually in a playground project that were installing the updated dependencies from tarballs. Here is one example of it working as expected: <img width="750" alt="Screenshot 2024-08-26 at 14 10 07" src="https://github.com/user-attachments/assets/83de15f2-1543-4805-9231-9b8df1636c5e"> |
||
|
Jordan Pittman
|
cc228fbfc3
|
Add support for matching multiple utility definitions for one candidate (#14231)
Currently if a plugin adds a utility called `duration` it will take
precedence over the built-in utilities — or any utilities with the same
name in previously included plugins. However, in v3, we emitted matches
from _all_ plugins where possible.
Take this plugin for example which adds utilities for
`animation-duration` via the `duration-*` class:
```ts
import plugin from 'tailwindcss/plugin'
export default plugin(
function ({ matchUtilities, theme }) {
matchUtilities(
{ duration: (value) => ({ animationDuration: value }) },
{ values: theme("animationDuration") },
)
},
{
theme: {
extend: {
animationDuration: ({ theme }) => ({
...theme("transitionDuration"),
}),
}
},
}
)
```
Before this PR this plugin's `duration` utility would override the
built-in `duration` utility so you'd get this for a class like
`duration-3500`:
```css
.duration-3000 {
animation-duration: 3500ms;
}
```
Now, after this PR, we'll emit rules for `transition-duration`
(Tailwind's built-in `duration-*` utility) and `animation-duration`
(from the above plugin) and you'll get this instead:
```css
.duration-3000 {
transition-duration: 3500ms;
}
.duration-3000 {
animation-duration: 3500ms;
}
```
These are output as separate rules to ensure that they can all be sorted
appropriately against other utilities.
---------
Co-authored-by: Philipp Spiess <hello@philippspiess.com>
|
