mirror of
https://github.com/tailwindlabs/tailwindcss.git
synced 2025-12-08 21:36:08 +00:00
6474 Commits
| Author | SHA1 | Message | Date | |
|---|---|---|---|---|
depfu[bot]
|
fee19b2d4e
|
Update bun 1.2.22 → 1.3.0 (minor) (#19144) | ||
Philipp Spiess
|
70f27d50a6
|
Remove Oxide postinstall script (#19149)
This PR effectively reverts #17929. The bug in npm that required it was fixed a couple of months ago and with recent changes to pnpm that requires manually approving all postinstall scripts, this is creating some unnecessary noise. |
||
Jordan Pittman
|
48c274d83e
|
Update Lightning CSS to 1.30.2 (#19143) | ||
|
depfu[bot]
|
e25c1f0594
|
Update eslint 9.36.0 → 9.37.0 (minor) (#19142)
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.36.0 → 9.37.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.37.0">9.37.0</a></h4> <blockquote><h2 dir="auto">Features</h2> <ul dir="auto"> <li> <a href=" |
||
|
depfu[bot]
|
71e1931044
|
Update @napi-rs/wasm-runtime 1.0.5 → 1.0.7 (patch) (#19140)
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? #### ✳️ @napi-rs/wasm-runtime (1.0.5 → 1.0.7) · [Repo](https://github.com/napi-rs/napi-rs) 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> |
||
Benoît Rouleau
|
89cbfc7b2d
|
Add optimize option to @tailwindcss/vite plugin (#19131)
Adds an `optimize` option to the Vite plugin that matches the API and
behavior of the PostCSS plugin.
Supports three formats:
- `optimize: false` - disable optimization
- `optimize: true` - enable optimization with minification
- `optimize: { minify: false }` - enable optimization without
minification
🤖 Generated with [Claude Code](https://claude.ai/code)
---------
Co-authored-by: Claude <noreply@anthropic.com>
Co-authored-by: Jordan Pittman <jordan@cryptica.me>
Co-authored-by: Robin Malfait <malfait.robin@gmail.com>
|
||
Robin Malfait
|
acb27ef9e9
|
Generalize the walk implementation (#19126)
This PR generalizes the `walk` implementations we have. What's important
here is that we currently have multiple `walk` implementations, one for
the AST, one for the `SelectorParser`, one for the `ValueParser`.
Sometimes, we also need to go up the tree in a depth-first manner. For
that, we have `walkDepth` implementations.
The funny thing is, all these implementations are very very similar,
even the kinds of trees are very similar. They are just objects with
`nodes: []` as children.
So this PR introduces a generic `walk` function that can work on all of
these trees.
There are also some situations where you need to go down and back up the
tree. For this reason, we added an `enter` and `exit` phase:
```ts
walk(ast, {
enter(node, ctx) {},
exit(node, ctx) {},
})
```
This means that you don't need to `walk(ast)` and later `walkDepth(ast)`
in case you wanted to do something _after_ visiting all nodes.
The API of these walk functions also slightly changed to fix some
problems we've had before. One is the `replaceWith` function. You could
technically call it multiple times, but that doesn't make sense so
instead you always have to return an explicit `WalkAction`. The
possibilities are:
```ts
// The ones we already had
WalkAction.Continue // Continue walking as normal, the default behavior
WalkAction.Skip // Skip walking the `nodes` of the current node
WalkAction.Stop // Stop the entire walk
// The new ones
WalkAction.Replace(newNode) // Replace the current node, and continue walking the new node(s)
WalkAction.ReplaceSkip(newNode) // Replace the current node, but don't walk the new node(s)
WalkAction.ReplaceStop(newNode) // Replace the current node, but stop the entire walk
```
To make sure that we can walk in both directions, and to make sure we
have proper control over when to walk which nodes, the `walk` function
is implemented in an iterative manner using a stack instead of
recursion.
This also means that a `WalkAction.Stop` or `WalkAction.ReplaceStop`
will immediately stop the walk, without unwinding the entire call stack.
Some notes:
- The CSS AST does have `context` nodes, for this we can build up the
context lazily when we need it. I added a `cssContext(ctx)` that gives
you an enhanced context including the `context` object that you can read
information from.
- The second argument of the `walk` function can still be a normal
function, which is equivalent to `{ enter: fn }`.
Let's also take a look at some numbers. With this new implementation,
each `walk` is roughly ~1.3-1.5x faster than before. If you look at the
memory usage (especially in Bun) we go from `~2.2GB` peak memory usage,
to `~300mb` peak memory usage.
Some benchmarks on small and big trees (M1 Max):
<img width="2062" height="1438" alt="image"
src="https://github.com/user-attachments/assets/5ec8c22a-9de8-4e08-869a-18c0d30eb7e8"
/>
<img width="2062" height="1246" alt="image"
src="https://github.com/user-attachments/assets/e89d4b8e-29ca-4aee-8fd2-b7c043d3bbf4"
/>
We also ran some benchmarks on @thecrypticace's M3 Max:
<img width="1598" height="1452" alt="image"
src="https://github.com/user-attachments/assets/3b06b6fe-2497-4f24-a428-1a0e2af3896a"
/>
In node the memory difference isn't that big, but the performance itself
is still better:
<img width="2034" height="1586" alt="image"
src="https://github.com/user-attachments/assets/ef28ae14-b53e-4912-9621-531f3b02898f"
/>
In summary:
1. Single `walk` implementation for multiple use cases
2. Support for `enter` and `exit` phases
3. New `WalkAction` possibilities for better control
4. Overall better performance
5. ... and lower memory usage
## Test plan
1. All tests still pass (but had to adjust some of the APIs if `walk`
was used inside tests).
2. Added new tests for the `walk` implementation
3. Ran local benchmarks to verify the performance improvements
|
||
|
depfu[bot]
|
fc63ce7fbc
|
Update @vitejs/plugin-react 5.0.3 → 5.0.4 (patch) (#19129)
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 (5.0.3 → 5.0.4) · [Repo](https://github.com/vitejs/vite-plugin-react) · [Changelog](https://github.com/vitejs/vite-plugin-react/blob/main/packages/plugin-react/CHANGELOG.md) <details> <summary>Release Notes</summary> <h4>5.0.4 (from changelog)</h4> <blockquote><h3 dir="auto">Perf: use native refresh wrapper plugin in rolldown-vite (<a href="https://bounce.depfu.com/github.com/vitejs/vite-plugin-react/pull/881">#881</a>)</h3></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> |
||
|
Robin Malfait
|
de6b54c307
|
Fix parsing issue when \t is used in at-rules (#19130)
This PR fixes an issue where an at-rule that used `@name\tparams` didn't properly parse because we didn't properly handle `\t`. ## Test plan 1. Added failing tests 2. Made them pass Fixes: #19127 |
||
|
Robin Malfait
|
22858ac4ae
|
Make TypeScript a bit more happy (#19124)
While working on another PR, I noticed that some files had missing properties and made TypeScript unhappy. Let's make TypeScript happy again... |
||
|
depfu[bot]
|
c7f6303070 | Update semver to version 7.7.3 | ||
|
depfu[bot]
|
28c72314fc
|
Update @types/react 19.1.13 → 19.2.2 (minor) (#19116)
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.1.13 → 19.2.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> |
||
|
Jordan Pittman
|
f945c3d29f
|
Don’t index into strings with the theme(…) function (#19111)
Indexing into a string is only ever going to produce a single character and is almost guaranteed to be a mistake. The legacy keypath notation is meant to traverse objects and arrays — not strings. Fixes #19104 |
||
|
Jordan Pittman
|
2cba8319ce
|
Clone AST nodes used in staticValues (#19110)
These were getting mutated but they were shared instead of being re-created for new candidates. Cloning the nodes fixes this so mutation of the AST nodes doesn’t stick around. Fixes #19108 |
||
|
depfu[bot]
|
249bed0916
|
Update @napi-rs/cli 3.2.0 → 3.3.0 (minor) (#19102)
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? #### ✳️ @napi-rs/cli (3.2.0 → 3.3.0) · [Repo](https://github.com/napi-rs/napi-rs) 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> Co-authored-by: Jordan Pittman <jordan@cryptica.me> |
||
|
Robin Malfait
|
c67c0c54cf
|
Canonicalize dimensions (#19101) | ||
|
depfu[bot]
|
496a1e9362
|
Update @types/react-dom 19.1.9 → 19.2.1 (minor) (#19088)
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.1.9 → 19.2.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> Co-authored-by: Jordan Pittman <jordan@cryptica.me> |
||
|
depfu[bot]
|
53a8d3bc90
|
Update all of react 19.1.1 → 19.2.0 (minor) (#19087)
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.1.1 → 19.2.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.2.0">19.2.0</a></h4> <blockquote><p dir="auto">Below is a list of all new features, APIs, and bug fixes.</p> <p dir="auto">Read the <a href="https://react.dev/blog/2025/10/01/react-19-2">React 19.2 release post</a> for more information.</p> <h2 dir="auto">New React Features</h2> <ul dir="auto"> <li> <a href="https://react.dev/reference/react/Activity"><code class="notranslate"><Activity></code></a>: A new API to hide and restore the UI and internal state of its children.</li> <li> <a href="https://react.dev/reference/react/useEffectEvent"><code class="notranslate">useEffectEvent</code></a> is a React Hook that lets you extract non-reactive logic into an <a href="https://react.dev/learn/separating-events-from-effects#declaring-an-effect-event">Effect Event</a>.</li> <li> <a href="https://react.dev/reference/react/cacheSignal"><code class="notranslate">cacheSignal</code></a> (for RSCs) lets your know when the <code class="notranslate">cache()</code> lifetime is over.</li> <li> <a href="https://react.dev/reference/developer-tooling/react-performance-tracks">React Performance tracks</a> appear on the Performance panel’s timeline in your browser developer tools</li> </ul> <h2 dir="auto">New React DOM Features</h2> <ul dir="auto"> <li>Added resume APIs for partial pre-rendering with Web Streams: <ul dir="auto"> <li> <a href="https://react.dev/reference/react-dom/server/resume"><code class="notranslate">resume</code></a>: to resume a prerender to a stream.</li> <li> <a href="https://react.dev/reference/react-dom/static/resumeAndPrerender"><code class="notranslate">resumeAndPrerender</code></a>: to resume a prerender to HTML.</li> </ul> </li> <li>Added resume APIs for partial pre-rendering with Node Streams: <ul dir="auto"> <li> <a href="https://react.dev/reference/react-dom/server/resumeToPipeableStream"><code class="notranslate">resumeToPipeableStream</code></a>: to resume a prerender to a stream.</li> <li> <a href="https://react.dev/reference/react-dom/static/resumeAndPrerenderToNodeStream"><code class="notranslate">resumeAndPrerenderToNodeStream</code></a>: to resume a prerender to HTML.</li> </ul> </li> <li>Updated <a href="https://react.dev/reference/react-dom/static/prerender"><code class="notranslate">prerender</code></a> APIs to return a <code class="notranslate">postponed</code> state that can be passed to the <code class="notranslate">resume</code> APIs.</li> </ul> <h2 dir="auto">Notable changes</h2> <ul dir="auto"> <li>React DOM now batches suspense boundary reveals, matching the behavior of client side rendering. This change is especially noticeable when animating the reveal of Suspense boundaries e.g. with the upcoming <code class="notranslate"><ViewTransition></code> Component. React will batch as much reveals as possible before the first paint while trying to hit popular first-contentful paint metrics.</li> <li>Add Node Web Streams (<code class="notranslate">prerender</code>, <code class="notranslate">renderToReadableStream</code>) to server-side-rendering APIs for Node.js</li> <li>Use underscore instead of <code class="notranslate">:</code> IDs generated by useId</li> </ul> <h2 dir="auto">All Changes</h2> <h3 dir="auto">React</h3> <ul dir="auto"> <li> <code class="notranslate"><Activity /></code> was developed over many years, starting before <code class="notranslate">ClassComponent.setState</code> (<a href="https://bounce.depfu.com/github.com/acdlite">@acdlite</a> <a href="https://bounce.depfu.com/github.com/sebmarkbage">@sebmarkbage</a> and many others)</li> <li>Stringify context as "SomeContext" instead of "SomeContext.Provider" (<a href="https://bounce.depfu.com/github.com/kassens">@kassens</a> <a href="https://bounce.depfu.com/github.com/facebook/react/pull/33507">#33507</a>)</li> <li>Include stack of cause of React instrumentation errors with <code class="notranslate">%o</code> placeholder (<a href="https://bounce.depfu.com/github.com/eps1lon">@eps1lon</a> <a href="https://bounce.depfu.com/github.com/facebook/react/pull/34198">#34198</a>)</li> <li>Fix infinite <code class="notranslate">useDeferredValue</code> loop in popstate event (<a href="https://bounce.depfu.com/github.com/acdlite">@acdlite</a> <a href="https://bounce.depfu.com/github.com/facebook/react/pull/32821">#32821</a>)</li> <li>Fix a bug when an initial value was passed to <code class="notranslate">useDeferredValue</code> (<a href="https://bounce.depfu.com/github.com/acdlite">@acdlite</a> <a href="https://bounce.depfu.com/github.com/facebook/react/pull/34376">#34376</a>)</li> <li>Fix a crash when submitting forms with Client Actions (<a href="https://bounce.depfu.com/github.com/sebmarkbage">@sebmarkbage</a> <a href="https://bounce.depfu.com/github.com/facebook/react/pull/33055">#33055</a>)</li> <li>Hide/unhide the content of dehydrated suspense boundaries if they resuspend (<a href="https://bounce.depfu.com/github.com/sebmarkbage">@sebmarkbage</a> <a href="https://bounce.depfu.com/github.com/facebook/react/pull/32900">#32900</a>)</li> <li>Avoid stack overflow on wide trees during Hot Reload (<a href="https://bounce.depfu.com/github.com/sophiebits">@sophiebits</a> <a href="https://bounce.depfu.com/github.com/facebook/react/pull/34145">#34145</a>)</li> <li>Improve Owner and Component stacks in various places (<a href="https://bounce.depfu.com/github.com/sebmarkbage">@sebmarkbage</a>, <a href="https://bounce.depfu.com/github.com/eps1lon">@eps1lon</a>: <a href="https://bounce.depfu.com/github.com/facebook/react/pull/33629">#33629</a>, <a href="https://bounce.depfu.com/github.com/facebook/react/pull/33724">#33724</a>, <a href="https://bounce.depfu.com/github.com/facebook/react/pull/32735">#32735</a>, <a href="https://bounce.depfu.com/github.com/facebook/react/pull/33723">#33723</a>)</li> <li>Add <code class="notranslate">cacheSignal</code> (<a href="https://bounce.depfu.com/github.com/sebmarkbage">@sebmarkbage</a> <a href="https://bounce.depfu.com/github.com/facebook/react/pull/33557">#33557</a>)</li> </ul> <h3 dir="auto">React DOM</h3> <ul dir="auto"> <li>Block on Suspensey Fonts during reveal of server-side-rendered content (<a href="https://bounce.depfu.com/github.com/sebmarkbage">@sebmarkbage</a> <a href="https://bounce.depfu.com/github.com/facebook/react/pull/33342">#33342</a>)</li> <li>Use underscore instead of <code class="notranslate">:</code> for IDs generated by <code class="notranslate">useId</code> (<a href="https://bounce.depfu.com/github.com/sebmarkbage">@sebmarkbage</a>, <a href="https://bounce.depfu.com/github.com/eps1lon">@eps1lon</a>: <a href="https://bounce.depfu.com/github.com/facebook/react/pull/32001">#32001</a>, <a href="https://bounce.depfu.com/github.com/facebook/react/pull/33342">#33342</a><a href="https://bounce.depfu.com/github.com/facebook/react/pull/33099">#33099</a>, <a href="https://bounce.depfu.com/github.com/facebook/react/pull/33422">#33422</a>)</li> <li>Stop warning when ARIA 1.3 attributes are used (<a href="https://bounce.depfu.com/github.com/Abdul-Omira">@Abdul-Omira</a> <a href="https://bounce.depfu.com/github.com/facebook/react/pull/34264">#34264</a>)</li> <li>Allow <code class="notranslate">nonce</code> to be used on hoistable styles (<a href="https://bounce.depfu.com/github.com/Andarist">@Andarist</a> <a href="https://bounce.depfu.com/github.com/facebook/react/pull/32461">#32461</a>)</li> <li>Warn for using a React owned node as a Container if it also has text content (<a href="https://bounce.depfu.com/github.com/sebmarkbage">@sebmarkbage</a> <a href="https://bounce.depfu.com/github.com/facebook/react/pull/32774">#32774</a>)</li> <li>s/HTML/text for for error messages if text hydration mismatches (<a href="https://bounce.depfu.com/github.com/rickhanlonii">@rickhanlonii</a> <a href="https://bounce.depfu.com/github.com/facebook/react/pull/32763">#32763</a>)</li> <li>Fix a bug with <code class="notranslate">React.use</code> inside <code class="notranslate">React.lazy</code>-ed Component (<a href="https://bounce.depfu.com/github.com/hi-ogawa">@hi-ogawa</a> <a href="https://bounce.depfu.com/github.com/facebook/react/pull/33941">#33941</a>)</li> <li>Enable the <code class="notranslate">progressiveChunkSize</code> option for server-side-rendering APIs (<a href="https://bounce.depfu.com/github.com/sebmarkbage">@sebmarkbage</a> <a href="https://bounce.depfu.com/github.com/facebook/react/pull/33027">#33027</a>)</li> <li>Fix a bug with deeply nested Suspense inside Suspense fallback when server-side-rendering (<a href="https://bounce.depfu.com/github.com/gnoff">@gnoff</a> <a href="https://bounce.depfu.com/github.com/facebook/react/pull/33467">#33467</a>)</li> <li>Avoid hanging when suspending after aborting while rendering (<a href="https://bounce.depfu.com/github.com/gnoff">@gnoff</a> <a href="https://bounce.depfu.com/github.com/facebook/react/pull/34192">#34192</a>)</li> <li>Add Node Web Streams to server-side-rendering APIs for Node.js (<a href="https://bounce.depfu.com/github.com/sebmarkbage">@sebmarkbage</a> <a href="https://bounce.depfu.com/github.com/facebook/react/pull/33475">#33475</a>)</li> </ul> <h3 dir="auto">React Server Components</h3> <ul dir="auto"> <li>Preload <code class="notranslate"><img></code> and <code class="notranslate"><link></code> using hints before they're rendered (<a href="https://bounce.depfu.com/github.com/sebmarkbage">@sebmarkbage</a> <a href="https://bounce.depfu.com/github.com/facebook/react/pull/34604">#34604</a>)</li> <li>Log error if production elements are rendered during development (<a href="https://bounce.depfu.com/github.com/eps1lon">@eps1lon</a> <a href="https://bounce.depfu.com/github.com/facebook/react/pull/34189">#34189</a>)</li> <li>Fix a bug when returning a Temporary reference (e.g. a Client Reference) from Server Functions (<a href="https://bounce.depfu.com/github.com/sebmarkbage">@sebmarkbage</a> <a href="https://bounce.depfu.com/github.com/facebook/react/pull/34084">#34084</a>, <a href="https://bounce.depfu.com/github.com/denk0403">@denk0403</a> <a href="https://bounce.depfu.com/github.com/facebook/react/pull/33761">#33761</a>)</li> <li>Pass line/column to <code class="notranslate">filterStackFrame</code> (<a href="https://bounce.depfu.com/github.com/eps1lon">@eps1lon</a> <a href="https://bounce.depfu.com/github.com/facebook/react/pull/33707">#33707</a>)</li> <li>Support Async Modules in Turbopack Server References (<a href="https://bounce.depfu.com/github.com/lubieowoce">@lubieowoce</a> <a href="https://bounce.depfu.com/github.com/facebook/react/pull/34531">#34531</a>)</li> <li>Add support for .mjs file extension in Webpack (<a href="https://bounce.depfu.com/github.com/jennyscript">@jennyscript</a> <a href="https://bounce.depfu.com/github.com/facebook/react/pull/33028">#33028</a>)</li> <li>Fix a wrong missing key warning (<a href="https://bounce.depfu.com/github.com/unstubbable">@unstubbable</a> <a href="https://bounce.depfu.com/github.com/facebook/react/pull/34350">#34350</a>)</li> <li>Make console log resolve in predictable order (<a href="https://bounce.depfu.com/github.com/sebmarkbage">@sebmarkbage</a> <a href="https://bounce.depfu.com/github.com/facebook/react/pull/33665">#33665</a>)</li> </ul> <h3 dir="auto">React Reconciler</h3> <ul dir="auto"> <li> <a href="https://bounce.depfu.com/github.com/facebook/react/blob/v19.2.0/packages/react-reconciler/src/ReactFiberReconciler.js#L255-L261">createContainer</a> and <a href="https://bounce.depfu.com/github.com/facebook/react/blob/v19.2.0/packages/react-reconciler/src/ReactFiberReconciler.js#L305-L312">createHydrationContainer</a> had their parameter order adjusted after <code class="notranslate">on*</code> handlers to account for upcoming experimental APIs</li> </ul> <h2 dir="auto">eslint-plugin-react-hooks@6.1.0</h2> <p dir="auto"><strong>Note:</strong> Version 6.0.0 was mistakenly released and immediately deprecated and untagged on npm. This is the first official 6.x major release and includes breaking changes.</p> <ul dir="auto"> <li> <strong>Breaking:</strong> Require Node.js 18 or newer. (<a href="https://bounce.depfu.com/github.com/michaelfaith">@michaelfaith</a> in <a href="https://bounce.depfu.com/github.com/facebook/react/pull/32458">#32458</a>)</li> <li> <strong>Breaking:</strong> Flat config is now the default <code class="notranslate">recommended</code> preset. Legacy config moved to <code class="notranslate">recommended-legacy</code>. (<a href="https://bounce.depfu.com/github.com/michaelfaith">@michaelfaith</a> in <a href="https://bounce.depfu.com/github.com/facebook/react/pull/32457">#32457</a>)</li> <li> <strong>New Violations:</strong> Disallow calling <code class="notranslate">use</code> within try/catch blocks. (<a href="https://bounce.depfu.com/github.com/poteto">@poteto</a> in <a href="https://bounce.depfu.com/github.com/facebook/react/pull/34040">#34040</a>)</li> <li> <strong>New Violations:</strong> Disallow calling <code class="notranslate">useEffectEvent</code> functions in arbitrary closures. (<a href="https://bounce.depfu.com/github.com/jbrown215">@jbrown215</a> in <a href="https://bounce.depfu.com/github.com/facebook/react/pull/33544">#33544</a>)</li> <li>Handle <code class="notranslate">React.useEffect</code> in addition to <code class="notranslate">useEffect</code> in rules-of-hooks. (<a href="https://bounce.depfu.com/github.com/Ayc0">@Ayc0</a> in <a href="https://bounce.depfu.com/github.com/facebook/react/pull/34076">#34076</a>)</li> <li>Added <code class="notranslate">react-hooks</code> settings config option that to accept <code class="notranslate">additionalEffectHooks</code> that are used across exhaustive-deps and rules-of-hooks rules. (<a href="https://bounce.depfu.com/github.com/jbrown215">@jbrown215</a>) in <a href="https://bounce.depfu.com/github.com/facebook/react/pull/34497">#34497</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=" |
||
|
Robin Malfait
|
01d1e98259
|
Canonicalization constant folding and handling zeros (#19095)
The main goal of this PR was to support canonicalization of zero like values. We essentially want to canonicalize `-mt-0` as `mt-0`, but also `mt-[0px]`, `mt-[0rem]`, and other length-like units to just `mt-0`. To do this, we had to handle 2 things: 1. We introduced some more constant folding, including making `0px` and `0rem` fold to `0`. We only do this for length units. We also normalize `-0`, `+0`, `-0.0` and so on to `0`. 2. While pre-computing utilities in our lookup table, we make sure that we prefer `mt-0` over `-mt-0` if both result in the same signature. Moved some of the constant folding logic into its own function and added a bunch of separate tests for it. ## Test plan Added more unit tests where we normalize different zero-like values to `0`. Running the canonicalization logic: ```js designSystem.canonicalizeCandidates([ '-m-0', '-m-[-0px]', '-m-[-0rem]', '-m-[0px]', '-m-[0rem]', 'm-0', 'm-[-0px]', 'm-[-0rem]', 'm-[0px]', 'm-[0rem]', 'm-[calc(var(--spacing)*0)]', 'm-[--spacing(0)]', 'm-[--spacing(0.0)]', 'm-[+0]', 'm-[-0]', '-m-[-0]', '-m-[+0]', ]) // → ['m-0'] ``` --------- Co-authored-by: Jordan Pittman <jordan@cryptica.me> |
||
|
Robin Malfait
|
3aadba7cc1
|
Move modifier of not-*, has-*, and in-* variant to sub variant (#19100)
This PR fixes an issue where a compound variant with a modifier such as `not-group-hover/name:flex` would not generate anything because the `/name` modifier belongs to the `not` variant, and not the compounded `group-hover` variant. This PR is a **workaround** (and definitely not perfect) by special casing the `not`, `has`, and `in` variants such that their modifiers are moved internally to the sub variant as-if the `/name` existed on `group-hover`. We don't do it for other compound variants such as `group` and `peer` because then `group-peer-focus/name:underline` would result in a breaking change: ```diff - .group-peer-focus\\/name\\:flex:is(:where(.group\\/name):is(:where(.peer):focus ~ *) *) + .group-peer-focus\/name\:flex:is(:where(.group):is(:where(.peer\/name):focus ~ *) *) ``` In case the diff is not clear, the name has moved: <img width="1219" height="78" alt="image" src="https://github.com/user-attachments/assets/dce7bc95-9d93-452d-a275-b3891a05a1a4" /> This is also a limited workaround, because if you need multiple modifiers it won't work. I would've loved to special case this _inside_ the `not`, `has`, and `in` code that handles these variants, but we handle the variants in a depth-first way, so by the time you are handling the `not` variant, the sub variant was already handled... In a perfect world, you can use something like `not-group/name-hover` but then it becomes unambiguous because is `name` the name, is `name-hover`? ## Test plan Added a new test that wouldn't generate anything before this fix. Fixes: #15772 |
||
|
Robin Malfait
|
0c14df1a15
|
Fix resolving colors via theme(…) in compat mode with nested objects (#19097)
This PR fixes an issue when loading (nested) colors from a config file
and later referencing it via the `theme(…)` function in CSS.
Given a config like this:
```js
module.exports = {
theme: {
colors: {
foo: 'var(--foo-foo)',
'foo-bar': 'var(--foo-foo-bar)',
},
},
}
```
We internally map this into the design system. The issue here is that
the `foo` and `foo-bar` are overlapping and it behaves more like this:
```js
{
foo: {
DEFAULT: 'var(--foo-foo)',
bar: 'var(--foo-foo-bar)'
},
}
```
So while we can easily resolve `colors.foo-bar`, the `colors.foo` would
result in the object with a `DEFAULT` key. This PR solves that by using
the `DEFAULT` key if we end up with an object that has it.
If you end up resolving an object (`theme(colors)`) then the behavior is
unchanged.
## Test plan
1. Added a test based on the config in the issue (which failed before
this fix).
2. Also simplified the test case after identifying the problem (with the
`DEFAULT` key).
Fixes: #19091
|
||
|
Robin Malfait
|
561983d7e5
|
Suppress warnings when using :deep, :slotted and :global (#19094)
This PR ignores warnings related to `:deep`, `:slotted` and `:global` used by frameworks like Vue (see: https://vuejs.org/api/sfc-css-features#deep-selectors). ## Test plan Used a `:deep()` selector in a test project (Catalyst). ```diff diff --git a/templates/catalyst/src/tailwind.css b/templates/catalyst/src/tailwind.css index 79887e67..2acb749c 100644 --- a/templates/catalyst/src/tailwind.css +++ b/templates/catalyst/src/tailwind.css @@ -9,3 +9,7 @@ --font-sans: Inter, sans-serif; --font-sans--font-feature-settings: 'cv11'; } + +:deep(.foo) { + color: red; +} ``` Before: <img width="1625" height="372" alt="image" src="https://github.com/user-attachments/assets/4b948080-1aeb-41ba-8268-98828da21768" /> After: <img width="717" height="114" alt="image" src="https://github.com/user-attachments/assets/b8668da2-693e-4010-99fb-de3bc4a47bf9" /> Fixes: https://github.com/tailwindlabs/tailwindcss/pull/18918#issuecomment-3384928613 |
||
|
Robin Malfait
|
0c8d881f0e
|
Improve percentage canonicalization (#19072)
This PR improves the canonicalization of percentage values such that `[.1]`, `[.10]`, `[10%]` and `[10.0%]` are all treated as the same value. Right now we're only focusing on percentages. We can likely do this for all numbers, but I'm a little afraid of places where you can have multiple numbers separated by multiple dots (think SVGs). ## Test plan 1. Added more tests to cover the new cases. 2. Tested it in a local test project, where you can see the normalization in action. <img width="1383" height="117" alt="image" src="https://github.com/user-attachments/assets/03d99e3a-4404-437b-b458-58f7e8ce60da" /> |
||
|
Robin Malfait
|
efe084b7e7
|
Improve performance of cloning AST nodes (#19067)
This PR improves the performance of when we need to clone some AST
nodes. We have a few places where we clone `Candidate`, `Variant` and
CSS `AST` nodes.
Right now we use `structuredClone`, which works, but it is a generic
solution. However, we do know the exact structure of these AST nodes, so
we can write specialized clone functions that are much faster.
## Test plan
1. All the tests still pass with this change
2. The performance is better:
```
cloneCandidate - src/candidate.bench.ts > Candidate cloning
1.72x faster than cloneCandidate (spread)
74.03x faster than structuredClone
cloneAstNode() - src/ast.bench.ts > Cloning AST nodes
1.15x faster than cloneAstNode (with spread)
33.54x faster than structuredClone()
```
Ready for review, but should be merged after #19059
|
||
|
Robin Malfait
|
b77971f754
|
Introduce canonicalizeCandidates on the internal Design System (#19059)
This PR introduces a new `canonicalizeCandidates` function on the internal Design System. The big motivation to moving this to the core `tailwindcss` package is that we can use this in various places: - The Raycast extension - The VS Code extension / language server - 3rd party tools that use the Tailwind CSS design system APIs > This PR looks very big, but **I think it's best to go over the changes commit by commit**. Basically all of these steps already existed in the upgrade tool, but are now moved to our core `tailwindcss` package. Here is a list of all the changes: - Added a new `canonicalizeCandidates` function to the design system - Moved various migration steps to the core package. I inlined them in the same file and because of that I noticed a specific pattern (more on this later). - Moved `printCandidate` tests to the `tailwindcss` package - Setup tests for `canonicalizeCandidates` based on the existing tests in the upgrade tool. I noticed that all the migrations followed a specific pattern: 1. Parse the raw candidate into a `Candidate[]` AST 2. In a loop, try to migrate the `Candidate` to a new `Candidate` (this often handled both the `Candidate` and its `Variant[]`) 3. If something changed, print the new `Candidate` back to a string, and pass it to the next migration step. While this makes sense in isolation, we are doing a lot of repeated work by parsing, modifying, and printing the candidate multiple times. This let me to introduce the `big refactor` commit. This changes the steps to: 1. Up front, parse the raw candidate into a `Candidate[]` _once_. 2. Strip the variants and the important marker from the candidate. This means that each migration step only has to deal with the base `utility` and not care about the variants or the important marker. We can re-attach these afterwards. 3. Instead of a `rawCandidate: string`, each migration step receives an actual `Candidate` object (or a `Variant` object). 4. I also split up the migration steps for the `Candidate` and the `Variant[]`. All of this means that there is a lot less work that needs to be done. We can also cache results between migrations. So `[@media_print]:flex` and `[@media_print]:block` will result in `print:flex` and `print:block` respectively, but the `[@media_print]` part is only migrated once across both candidates. One migration step relied on the `postcss-selector-parser` package to parse selectors and attribute selectors. I didn't want to introduce a package just for this, so instead used our own `SelectorParser` in the migration and wrote a small `AttributeSelectorParser` that can parse the attribute selector into a little data structure we can work with instead. If we want, we can split this PR up into smaller pieces, but since the biggest chunk is moving existing code around, I think it's fairly doable to review as long as you go commit by commit. --- With this new API, we can turn: ``` [ 'bg-red-500', 'hover:bg-red-500', '[@media_print]:bg-red-500', 'hover:[@media_print]:bg-red-500', 'bg-red-500/100', 'hover:bg-red-500/100', '[@media_print]:bg-red-500/100', 'hover:[@media_print]:bg-red-500/100', 'bg-[var(--color-red-500)]', 'hover:bg-[var(--color-red-500)]', '[@media_print]:bg-[var(--color-red-500)]', 'hover:[@media_print]:bg-[var(--color-red-500)]', 'bg-[var(--color-red-500)]/100', 'hover:bg-[var(--color-red-500)]/100', '[@media_print]:bg-[var(--color-red-500)]/100', 'hover:[@media_print]:bg-[var(--color-red-500)]/100', 'bg-(--color-red-500)', 'hover:bg-(--color-red-500)', '[@media_print]:bg-(--color-red-500)', 'hover:[@media_print]:bg-(--color-red-500)', 'bg-(--color-red-500)/100', 'hover:bg-(--color-red-500)/100', '[@media_print]:bg-(--color-red-500)/100', 'hover:[@media_print]:bg-(--color-red-500)/100', 'bg-[color:var(--color-red-500)]', 'hover:bg-[color:var(--color-red-500)]', '[@media_print]:bg-[color:var(--color-red-500)]', 'hover:[@media_print]:bg-[color:var(--color-red-500)]', 'bg-[color:var(--color-red-500)]/100', 'hover:bg-[color:var(--color-red-500)]/100', '[@media_print]:bg-[color:var(--color-red-500)]/100', 'hover:[@media_print]:bg-[color:var(--color-red-500)]/100', 'bg-(color:--color-red-500)', 'hover:bg-(color:--color-red-500)', '[@media_print]:bg-(color:--color-red-500)', 'hover:[@media_print]:bg-(color:--color-red-500)', 'bg-(color:--color-red-500)/100', 'hover:bg-(color:--color-red-500)/100', '[@media_print]:bg-(color:--color-red-500)/100', 'hover:[@media_print]:bg-(color:--color-red-500)/100', '[background-color:var(--color-red-500)]', 'hover:[background-color:var(--color-red-500)]', '[@media_print]:[background-color:var(--color-red-500)]', 'hover:[@media_print]:[background-color:var(--color-red-500)]', '[background-color:var(--color-red-500)]/100', 'hover:[background-color:var(--color-red-500)]/100', '[@media_print]:[background-color:var(--color-red-500)]/100', 'hover:[@media_print]:[background-color:var(--color-red-500)]/100' ] ``` Into their canonicalized form: ``` [ 'bg-red-500', 'hover:bg-red-500', 'print:bg-red-500', 'hover:print:bg-red-500' ] ``` The list is also unique, so we won't end up with `bg-red-500 bg-red-500` twice. While the canonicalization itself is fairly fast, we still pay a **~1s** startup cost for some migrations (once, and cached for the entire lifetime of the design system). I would like to keep improving the performance and the kinds of migrations we do, but I think this is a good start. The cost we pay is for: 1. Generating a full list of all possible utilities based on the `getClassList` suggestions API. 2. Generating a full list of all possible variants. The canonicalization step for this list takes **~2.9ms** on my machine. Just for fun, if you use the `getClassList` API for intellisense that generates all the suggestions and their modifiers, you get a list of **263788** classes. If you canonicalize all of these, it takes **~500ms** in total. So roughly **~1.9μs** per candidate. This new API doesn't result in a performance difference for normal Tailwind CSS builds. The other potential concern is file size of the package. The generated `tailwindcss.tgz` file changed like this: ```diff - 684652 bytes (684.65 kB) + 749169 bytes (749.17 kB) ``` So the package increased by ~65 kB which I don't think is the end of the world, but it is important for the `@tailwindcss/browser` build which we don't want to grow unnecessarily. For this reason we remove some of the code for the design system conditionally such that you don't pay this cost in an environment where you will never need this API. The `@tailwindcss/browser` build looks like this: ```shell `dist/index.global.js 255.14 KB` (main) `dist/index.global.js 272.61 KB` (before this change) `dist/index.global.js 252.83 KB` (after this change, even smaller than on `main`) ``` |
||
|
Robin Malfait
|
73628f69f3
|
Fix Safari devtools issues because of nested @supports at-rules without normal rule (#19069)
This PR fixes a weird Safari rendering bug in the devtools. This seems
to be happening when using `@supports`, especially nested `@supports`
at-rules.
The issue is that our color-mix fallback generates declarations directly
in `@supports` at-rules which causes the weird rendering bug in Safari.
Adding this intermediate `&` rule seems to fix the issue.
This is a workaround for a browser bug, but the additional 3 characters
shouldn't be the end of the world.
## Test plan
1. Updated the tests with the new `& { }` intermediate rule
2. Other tests still pass as expected
| Before | After |
| --- | --- |
| <img width="450" height="549" alt="image"
src="https://github.com/user-attachments/assets/4b51fb93-8073-4414-8139-dec75e6bc086"
/> | <img width="448" height="548" alt="image"
src="https://github.com/user-attachments/assets/1016af67-c1eb-43dc-9554-158e7e2264c4"
/> |
Fixes: #19065
[ci-all]
|
||
|
Robin Malfait
|
49948d087e
|
Fix failing integration tests (#19068)
The vite/nuxt integration tests started failing because one of the internal dependencies (`nuxi`) was updated from `3.28.0` to `3.29.0` which includes a newer version of `undici` which in turn relies on `node:sqlite`. `node:sqlite` was added in a newer Node version, and we still use Node v20 in CI. This PR pins `nuxi` to `3.28.0` until we can upgrade our Node version in CI. [ci-all] |
||
|
Robin Malfait
|
86e4b8e636
|
run prettier | ||
|
Philipp Spiess
|
231e17b84a | Change permissions so issue-triage can run for everyone | ||
|
Philipp Spiess
|
4cbdfa6e43 | Issue triage tweaks | ||
|
Philipp Spiess
|
9ef314e786
|
Add agentic workflow issue-triage (#19057)
This PR attempts to set up an automatic issue triaging tool using Claude Code as the agent and GitHub Agentics as the framework: https://githubnext.github.io/gh-aw/start-here/quick-start/ Based on the `safe-outputs` setting, this agent can only label issues or write replies. Let's see how useful that is 🤷 You can't run it locally since it does not have a manual trigger and needs a new github issue instead so my plan is to merge it and then create some super legit issues to see if it works! ## Test plan ``` α dev/tailwindcss (add-workflow-workflows-issue-triage.md-3051) gh aw status Workflow Status Name | Installed | Up-to-date | Status | Time Remaining ------------ | --------- | ---------- | ------- | -------------- issue-triage | Yes | Yes | Unknown | 29d 22h ``` --------- Co-authored-by: Robin Malfait <malfait.robin@gmail.com> |
||
|
depfu[bot]
|
6802c685c9
|
Update globby 14.1.0 → 15.0.0 (major) (#19056)
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? #### ✳️ globby (14.1.0 → 15.0.0) · [Repo](https://github.com/sindresorhus/globby) <details> <summary>Release Notes</summary> <h4><a href="https://github.com/sindresorhus/globby/releases/tag/v15.0.0">15.0.0</a></h4> <blockquote><h3 dir="auto">Breaking</h3> <ul dir="auto"> <li>Require Node.js 20 <a href=" |
||
|
depfu[bot]
|
573f633f13
|
Update eslint 9.35.0 → 9.36.0 (minor) (#19049)
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.35.0 → 9.36.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.36.0">9.36.0</a></h4> <blockquote><h2 dir="auto">Features</h2> <ul dir="auto"> <li> <a href=" |
||
|
Jordan Pittman
|
b67cbcf6cc
|
Prepare v4.1.14 release (#19037)
Co-authored-by: Robin Malfait <malfait.robin@gmail.com>v4.1.14 |
||
|
depfu[bot]
|
d96a48e3c1 | Update all of nextjs to version 15.5.4 | ||
|
depfu[bot]
|
2766a49e28
|
Update tar 7.4.3 → 7.5.1 (minor) (#19035)
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? #### ✳️ tar (7.4.3 → 7.5.1) · [Repo](https://github.com/isaacs/node-tar) · [Changelog](https://github.com/isaacs/node-tar/blob/main/CHANGELOG.md) <details> <summary>Commits</summary> <p><a href=" |
||
|
depfu[bot]
|
5cd49b057b
|
Update @playwright/test 1.55.0 → 1.55.1 (patch) (#19033)
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? #### ✳️ @playwright/test (1.55.0 → 1.55.1) · [Repo](https://github.com/Microsoft/playwright) <details> <summary>Release Notes</summary> <h4><a href="https://github.com/microsoft/playwright/releases/tag/v1.55.1">1.55.1</a></h4> <blockquote><h3 dir="auto">Highlights</h3> <p dir="auto"><a href="https://bounce.depfu.com/github.com/microsoft/playwright/issues/37479">#37479</a> - [Bug]: Upgrade Chromium to 140.0.7339.186.<br> <a href="https://bounce.depfu.com/github.com/microsoft/playwright/issues/37147">#37147</a> - [Regression]: Internal error: step id not found.<br> <a href="https://bounce.depfu.com/github.com/microsoft/playwright/issues/37146">#37146</a> - [Regression]: HTML reporter displays a broken chip link when there are no projects.<br> <a href="https://bounce.depfu.com/github.com/microsoft/playwright/pull/37137">#37137</a> - Revert "fix(a11y): track inert elements as hidden".</p> <h2 dir="auto">Browser Versions</h2> <ul dir="auto"> <li>Chromium 140.0.7339.186</li> <li>Mozilla Firefox 141.0</li> <li>WebKit 26.0</li> </ul> <p dir="auto">This version was also tested against the following stable channels:</p> <ul dir="auto"> <li>Google Chrome 139</li> <li>Microsoft Edge 139</li> </ul></blockquote> <p><em>Does any of this look wrong? <a href="https://depfu.com/packages/npm/@playwright%2Ftest/feedback">Please let us know.</a></em></p> </details> <details> <summary>Commits</summary> <p><a href=" |
||
govizlora
|
47d6a023e3
|
Ensure first class inside className in React is migrated (#19031)
### 1. Handling React className migration The PR fixes an issue when migrating React components to tailwind v4 with the migration tool, that the first class after `className="` is ignored. For example, when migrating ```JSX <div className="shadow"></div> ``` `shadow` will not be migrated to `shadow-sm` . This is because in `is-safe-migration.ts`, it tests the line before candidate with regex `/(?<!:?class)=['"]$/`. This basically skips the migration for anything like `foo="shadow"`, with only exception for Vue (eg. `class="shadow"`). The PR changes the regex from ```regex /(?<!:?class)=['"]$/ ```` to ```regex /(?<!:?class|className)=['"]$/ ``` which essentially adds a new exception specifically for React's `className="shadow"` case. ### 2. Removing redundant rules Besides, I found that several other rules in `CONDITIONAL_TEMPLATE_SYNTAX` being redundant since they are already covered by the rule above, so I removed them. If we prefer the previous explicit approach, I can revert it. ## Test plan <!-- Explain how you tested your changes. Include the exact commands that you used to verify the change works and include screenshots/screen recordings of the update behavior in the browser if applicable. --> Tests added for both the Vue and React classes to prevent false negative cases. --------- Co-authored-by: Jordan Pittman <jordan@cryptica.me> |
||
|
Robin Malfait
|
9d00662e10
|
Show version mismatch when running upgrade tool (#19028)
This PR fixes an issue where sometimes people try to run the upgrade tool, reset the changes and then try again. If this happens, then the `package.json` and/or your lock file will point to the old Tailwind CSS v3 version, but the actual installed version will be v4. This will also cause the upgrade tool to now upgrade from v4 to v4, which is not what most people want if they were trying to upgrade from v3 to v4. This in turn will cause some issues because now we won't try to migrate the config file, or v3-specific classes that also exist in v4 but are only safe to upgrade from v3 to v4. This PR uses `npm ls tailwindcss` to determine the actual installed version. This command already errors if there is a mismatch between the installed version and the version in `package.json` or the lock file. This also happens to work in pnpm and bun projects (added integration tests for these). If for whatever reason we can't determine the expected version, we fall back to the old behavior of just upgrading. In this scenario, the changes introduced in https://github.com/tailwindlabs/tailwindcss/pull/19026 will at least give you a hint of what version was actually installed. ### Test plan 1. Tested it in a v3 project where I performed the following steps: 1. Run the upgrade tool in full (`npx tailwindcss-upgrade`) 2. Reset the changes (`git reset --hard && git clean -df`) 1. Run the upgrade tool again This resulted in the following output: <img width="1059" height="683" alt="image" src="https://github.com/user-attachments/assets/1d2ea2d1-b602-4631-958f-cc21eb8a633f" /> 2. Added some integration tests to make sure this also works in pnpm, bun and normal npm projects. [ci-all] |
||
|
Robin Malfait
|
b497e1eaf3
|
Add Upgrading from Tailwind CSS v… when running upgrade tool (#19026)
This PR adds a bit more information when running the upgrade tool to know what version of Tailwind CSS you're upgrading from. This will help users and maintainers when things go wrong. Will have another PR up soon that errors when the Tailwind CSS version in package.json and node_modules don't match. ### Test plan Ran this one one of our older projects and saw the version logged correctly. <img width="1055" height="363" alt="image" src="https://github.com/user-attachments/assets/5cbf4c52-ea0f-42c8-bd55-5bae2ed511de" /> |
||
|
depfu[bot]
|
f6bb72cf46
|
Update jiti 2.5.1 → 2.6.0 (minor) (#19029)
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? #### ✳️ jiti (2.5.1 → 2.6.0) · [Repo](https://github.com/unjs/jiti) · [Changelog](https://github.com/unjs/jiti/blob/main/CHANGELOG.md) <details> <summary>Release Notes</summary> <h4><a href="https://github.com/unjs/jiti/releases/tag/v2.6.0">2.6.0</a></h4> <blockquote><p dir="auto"><a href="https://bounce.depfu.com/github.com/unjs/jiti/compare/v2.5.1...v2.6.0">compare changes</a></p> <h3 dir="auto">🌟 What is new?</h3> <p dir="auto">This release fixes minor issues, migrates to Rspack for dist, and lazily imports the Babel transformer only when needed, which should noticeably improve startup times.</p> <ul dir="auto"> <li>Install size reduced from <code class="notranslate">2.03MB</code> to <code class="notranslate">1.67MB</code> </li> <li>Loading times improved <code class="notranslate">150ms</code> => <code class="notranslate">22ms</code> (full transform: <code class="notranslate">180ms</code> => <code class="notranslate">115ms</code>)</li> </ul> <h3 dir="auto">🔥 Performance</h3> <ul dir="auto"> <li>Lazy load transformer (<a href="https://bounce.depfu.com/github.com/unjs/jiti/pull/405">#405</a>)</li> </ul> <h3 dir="auto">🩹 Fixes</h3> <ul dir="auto"> <li> <strong>cjs-interop:</strong> Handle function default exports (<a href="https://bounce.depfu.com/github.com/unjs/jiti/pull/396">#396</a>)</li> <li>Always use native require/import for <code class="notranslate">node:</code> specifiers (<a href="https://bounce.depfu.com/github.com/unjs/jiti/pull/392">#392</a>)</li> </ul> <h3 dir="auto">📦 Build</h3> <ul dir="auto"> <li>Migrate to rspack (<a href="https://bounce.depfu.com/github.com/unjs/jiti/pull/404">#404</a>)</li> <li>Updated bundled dependencies (<a href="https://bounce.depfu.com/github.com/unjs/jiti/compare/v2.5.1...v2.6.0#diff-7ae45ad102eab3b6d7e7896acd08c427a9b25b346470d7bc6507b6481575d519">diff</a>)</li> </ul> <h3 dir="auto">✅ Tests</h3> <ul dir="auto"> <li>Update deno and bun native test coverage (<a href="https://bounce.depfu.com/github.com/unjs/jiti/commit/df844f8">df844f8</a>)</li> </ul> <h3 dir="auto">❤️ Contributors</h3> <ul dir="auto"> <li>Pooya Parsa (<a href="https://bounce.depfu.com/github.com/pi0">@pi0</a>)</li> <li>Volodymyr Kolesnykov (<a href="https://bounce.depfu.com/github.com/sjinks">@sjinks</a>)</li> <li>Jungwoo LEE (<a href="https://bounce.depfu.com/github.com/jungwoo3490">@jungwoo3490</a>)</li> </ul></blockquote> <p><em>Does any of this look wrong? <a href="https://depfu.com/packages/npm/jiti/feedback">Please let us know.</a></em></p> </details> <details> <summary>Commits</summary> <p><a href=" |
||
|
depfu[bot]
|
9feefacf81
|
Update bun 1.2.20 → 1.2.22 (patch) (#19007)
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.2.20 → 1.2.22) · [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]
|
0d39788ec9
|
Update @tailwindcss/typography 0.5.16 → 0.5.19 (minor) (#19014)
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? #### ✳️ @tailwindcss/typography (0.5.16 → 0.5.19) · [Repo](https://github.com/tailwindlabs/tailwindcss-typography) · [Changelog](https://github.com/tailwindlabs/tailwindcss-typography/blob/main/CHANGELOG.md) <details> <summary>Release Notes</summary> <h4><a href="https://github.com/tailwindlabs/tailwindcss-typography/releases/tag/v0.5.19">0.5.19</a></h4> <blockquote><h3 dir="auto">Fixed</h3> <ul dir="auto"> <li>Fixed broken color styles (<a href="https://bounce.depfu.com/github.com/tailwindlabs/tailwindcss-typography/pull/405">#405</a>)</li> </ul></blockquote> <h4><a href="https://github.com/tailwindlabs/tailwindcss-typography/releases/tag/v0.5.18">0.5.18</a></h4> <blockquote><h3 dir="auto">Fixed</h3> <ul dir="auto"> <li>Fixed undefined variable error (<a href="https://bounce.depfu.com/github.com/tailwindlabs/tailwindcss-typography/pull/403">#403</a>)</li> </ul></blockquote> <h4><a href="https://github.com/tailwindlabs/tailwindcss-typography/releases/tag/v0.5.17">0.5.17</a></h4> <blockquote><h3 dir="auto">Added</h3> <ul dir="auto"> <li>Add modifiers for description list elements (<a href="https://bounce.depfu.com/github.com/tailwindlabs/tailwindcss-typography/pull/357">#357</a>)</li> <li>Add <code class="notranslate">prose-picture</code> modifier (<a href="https://bounce.depfu.com/github.com/tailwindlabs/tailwindcss-typography/pull/367">#367</a>)</li> </ul> <h3 dir="auto">Fixed</h3> <ul dir="auto"> <li>Include unit in <code class="notranslate">hr</code> border-width value (<a href="https://bounce.depfu.com/github.com/tailwindlabs/tailwindcss-typography/pull/379">#379</a>)</li> <li>Ensure <code class="notranslate"><kbd></code> styles work with Tailwind CSS v4 (<a href="https://bounce.depfu.com/github.com/tailwindlabs/tailwindcss-typography/pull/387">#387</a>)</li> </ul> <h3 dir="auto">Changed</h3> <ul dir="auto"> <li>Remove lodash dependencies (<a href="https://bounce.depfu.com/github.com/tailwindlabs/tailwindcss-typography/pull/402">#402</a>)</li> </ul></blockquote> <p><em>Does any of this look wrong? <a href="https://depfu.com/packages/npm/@tailwindcss%2Ftypography/feedback">Please let us know.</a></em></p> </details> <details> <summary>Commits</summary> <p><a href=" |
||
|
depfu[bot]
|
20f830f687
|
Update prettier-plugin-organize-imports 4.2.0 → 4.3.0 (minor) (#19013)
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? #### ✳️ prettier-plugin-organize-imports (4.2.0 → 4.3.0) · [Repo](https://github.com/simonhaenisch/prettier-plugin-organize-imports) · [Changelog](https://github.com/simonhaenisch/prettier-plugin-organize-imports/blob/master/changelog.md) <details> <summary>Release Notes</summary> <h4><a href="https://github.com/simonhaenisch/prettier-plugin-organize-imports/releases/tag/v4.3.0">4.3.0</a></h4> <blockquote><h2 dir="auto">What's Changed</h2> <ul dir="auto"> <li>feat: allow configuration of <code class="notranslate">organizeImportsTypeOrder</code>(<a href="https://bounce.depfu.com/github.com/simonhaenisch/prettier-plugin-organize-imports/pull/152">#152</a>) - thanks <a href="https://bounce.depfu.com/github.com/goege64">@goege64</a> for your first contribution 🎉</li> </ul> <p dir="auto"><strong>Full Changelog</strong>: <a href="https://bounce.depfu.com/github.com/simonhaenisch/prettier-plugin-organize-imports/compare/v4.2.0...v4.3.0"><tt>v4.2.0...v4.3.0</tt></a></p></blockquote> <p><em>Does any of this look wrong? <a href="https://depfu.com/packages/npm/prettier-plugin-organize-imports/feedback">Please let us know.</a></em></p> </details> <details> <summary>Commits</summary> <p><a href=" |
||
|
depfu[bot]
|
cc8fefc154 | Update magic-string to version 0.30.19 | ||
|
depfu[bot]
|
1f844244cb | Update all of nextjs to version 15.5.2 | ||
|
depfu[bot]
|
210575a6a5
|
Update dedent 1.6.0 → 1.7.0 (minor) (#19010)
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? #### ✳️ dedent (1.6.0 → 1.7.0) · [Repo](https://github.com/dmnd/dedent) · [Changelog](https://github.com/dmnd/dedent/blob/main/CHANGELOG.md) <details> <summary>Release Notes</summary> <h4><a href="https://github.com/dmnd/dedent/releases/tag/v1.7.0">1.7.0</a></h4> <blockquote><h2 dir="auto">What's Changed</h2> <ul dir="auto"> <li>docs: cleaned up README.md badges by <a href="https://bounce.depfu.com/github.com/JoshuaKGoldberg">@JoshuaKGoldberg</a> in <a href="https://bounce.depfu.com/github.com/dmnd/dedent/pull/100">#100</a> </li> <li>feat: add alignValues option by <a href="https://bounce.depfu.com/github.com/PaperStrike">@PaperStrike</a> in <a href="https://bounce.depfu.com/github.com/dmnd/dedent/pull/102">#102</a> </li> <li>1.7.0 by <a href="https://bounce.depfu.com/github.com/JoshuaKGoldberg">@JoshuaKGoldberg</a> in <a href="https://bounce.depfu.com/github.com/dmnd/dedent/pull/103">#103</a> </li> </ul> <h2 dir="auto">New Contributors</h2> <ul dir="auto"> <li> <a href="https://bounce.depfu.com/github.com/PaperStrike">@PaperStrike</a> made their first contribution in <a href="https://bounce.depfu.com/github.com/dmnd/dedent/pull/102">#102</a> </li> </ul> <p dir="auto"><strong>Full Changelog</strong>: <a href="https://bounce.depfu.com/github.com/dmnd/dedent/compare/v1.6.0...v1.7.0"><tt>v1.6.0...v1.7.0</tt></a></p></blockquote> <p><em>Does any of this look wrong? <a href="https://depfu.com/packages/npm/dedent/feedback">Please let us know.</a></em></p> </details> <details> <summary>Commits</summary> <p><a href=" |
||
|
depfu[bot]
|
3a4eb389b6
|
Update eslint 9.33.0 → 9.35.0 (minor) (#19009)
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.33.0 → 9.35.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.35.0">9.35.0</a></h4> <blockquote><h2 dir="auto">Features</h2> <ul dir="auto"> <li> <a href=" |
||
|
depfu[bot]
|
de726339e7
|
Update @types/semver 7.7.0 → 7.7.1 (patch) (#19005)
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/semver (7.7.0 → 7.7.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]
|
d593a2101a
|
Update @types/react 19.1.9 → 19.1.13 (patch) (#19003)
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.1.9 → 19.1.13) · [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> |
