Permalink
Comparing changes
Choose two branches to see what’s changed or to start a new pull request.
If you need to, you can also or
learn more about diff comparisons.
Open a pull request
Create a new pull request by comparing changes across two branches. If you need to, you can also .
Learn more about diff comparisons here.
...
- 10 commits
- 42 files changed
- 5 contributors
Commits on Mar 20, 2025
-
Revert "Temporarily revert changes to `@utility"
This reverts commit 1aab04c.
Commits on Mar 21, 2025
-
Fix class extraction followed by
(in Pug (#17320)This PR fixes an issue where a class shorthand in Pug followed by a `(` is not properly extracted. ```html <template lang="pug"> .text-sky-600.bg-neutral-900(title="A tooltip") This div has an HTML attribute. </template> ``` The `text-sky-600` is extracted, but the `bg-neutral-900` is not. Fixes: #17313 # Test plan 1. Added test to cover this case 2. Existing tests pass (after a few small adjustments due to _more_ extracted candidates, but definitely not _less_) 3. Verified against the original issue (top is before, bottom is this PR) <img width="1307" alt="image" src="https://github.com/user-attachments/assets/68a0529f-63ad-477d-a342-e3f91c5a1690" /> We had this exact same bug in Slim (#17278). Since Pug, Slim and Haml are the only pre processors we have right now with this dot-separated class notation I also double checked the Haml pre-processor if this is an issue or not (and it's already covered there). <img width="1263" alt="image" src="https://github.com/user-attachments/assets/c658168b-d124-46c9-9ec0-9697151a57bf" />
Commits on Mar 24, 2025
-
-
This change was added in #17320 which was not released yet, see commit order on `main`: https://github.com/tailwindlabs/tailwindcss/commits/main/
-
Vite: Emit build dependencies on partial rebuilds (#17347)
Closes #17339 This PR fixes an issue that caused changes to `@import`-ed CSS files to no longer rebuild the stylesheet after a change was made to a template file. The change in the template file causes a fast-path in the Vite plugin now after changes in 4.0.8: _partial rebuilds_. For that branch we do not need to re-evaluate your input CSS since we know only the candidate list changed. However, we still need to emit all build dependencies as via `addWatchFile(…)`, otherwise Vite will not correctly register updates for these dependencies anymore. ## Test plan - Updated the kitchen-sink Vite update tests to ensure that an `@import`-ed CSS file can be updated even after a partial rebuild. - Ensure this works in our Vite playground
-
Pre process
Slimtemplates embedded in Ruby files (#17336)This PR fixes an issue where embedded Slim templates inside of Ruby files are not pre processed because we pre process based on a file extension. This PR also handles embedded SLIM templates using the following syntax: ```rb slim_template <<~SLIM .flex .flex-1 h1 Hello World .flex-1 p This is a test SLIM ``` ~~As far as I can tell, this is only a Slim template thing and not a Haml template thing but I could be wrong here. See: https://viewcomponent.org/guide/templates.html#interpolations~~ The ViewComponent package handles anything that looks like `{lang}_template`, so the lang here will be used as the pre processing language for now. Fixes: #17334 # Test plan 1. Added test for this 2. Existing tests pass 3. Made sure that the snippet from the issue works as expected: Added an example where we have a `slim_template` and a `svelte_template` to prove that it embeds based on the language. I also added a `html_template` with Svelte syntax to really make sure that that _doesn't_ work. <img width="1816" alt="image" src="https://github.com/user-attachments/assets/35564a32-9c46-4b51-bb1f-e02f4ffe8b01" /> -
Add Input & Output check to CLI (#17311)
Throw an error if the input and output file for the CLI are identical. --------- Co-authored-by: Philipp Spiess <hello@philippspiess.com> Co-authored-by: Robin Malfait <malfait.robin@gmail.com>
3 people authoredMar 24, 2025 -
Extract keyframe name when followed by comma (#17352)
Fixes #17332 This PR ensures that keyframes are emitted even when they are referenced following a comma, e.g.: ```css @theme { --animate-test: 500ms both fade-in, 1000ms linear 500ms spin infinite; /* ^ */ @Keyframes fade-in { from { opacity: 0%; } to { opacity: 100%; } } } ``` ## Test plan Added a unit test to capture the issue from #17332
Commits on Mar 25, 2025
-
Add
::-webkit-details-markerpseudo tomarkervariant (#17362)See #17360 This PR updates the `marker` variant to also target the marker present in `<summary>` elements in WebKit browsers. Chromium uses `::marker` and is therefore already covered. --------- Co-authored-by: Philipp Spiess <hello@philippspiess.com>
-
Prepare v4.0.16 release (#17372)
Prepare the 4.0.16 release. ~~Also added a commit to mark the `--value('…')` and `--modifier('…')` with literals strings as an experimental feature (aka not shipped in this PR). But we can revert that commit if we still want to ship it in 4.0.16 instead of 4.1.~~ --------- Co-authored-by: Philipp Spiess <hello@philippspiess.com>
There are no files selected for viewing
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.