Tailwind CSS v4 #450
Merged
Tailwind CSS v4 #450
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
🦋 Changeset detectedLatest commit: 672e5c2 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
Contributor
built with Refined Cloudflare Pages Action⚡ Cloudflare Pages Deployment
|
commit: |
… `hsl()` (as variable now includes the color function)
…city` or `color-mix()` depending on the usage
…gray gradient issue due to TW4's use of `color-mix()` details: https://bsky.app/profile/techniq.dev/post/3lk6qr6e5b22t
techniq
added a commit
that referenced
this pull request
Mar 12, 2025
* Initial migration to Tailwind 4 (and layerstack/svelte-ux @next) * Format project * Update all the non-transparent CSS variables to remove the hard coded `hsl()` (as variable now includes the color function) * fix(LinearGradient): Handle `tw-gradient-[from|to]` no longer inheriting * Cleanup * fix(Spline): Pass `fillOpacity` prop (instead of `fill-opacity`) to support Canvas * Update semi-transparent CSS variable usage to use `opacity`, `fillOpacity` or `color-mix()` depending on the usage * Add changeset * Use `1%` instead of `0%` opacity for gradient examples to workaround gray gradient issue due to TW4's use of `color-mix()` details: https://bsky.app/profile/techniq.dev/post/3lk6qr6e5b22t * Refine getting started * Restore prose heading styling (size/bold/margin) * fix: Support `opacity` prop/style when Canvas rendered for all primatives * docs(LineChart): Fix "Gradient threshold" highlight and tooltip color
techniq
added a commit
that referenced
this pull request
Apr 23, 2025
* Initial migration to Tailwind 4 (and layerstack/svelte-ux @next) * Format project * Update all the non-transparent CSS variables to remove the hard coded `hsl()` (as variable now includes the color function) * fix(LinearGradient): Handle `tw-gradient-[from|to]` no longer inheriting * Cleanup * fix(Spline): Pass `fillOpacity` prop (instead of `fill-opacity`) to support Canvas * Update semi-transparent CSS variable usage to use `opacity`, `fillOpacity` or `color-mix()` depending on the usage * Add changeset * Use `1%` instead of `0%` opacity for gradient examples to workaround gray gradient issue due to TW4's use of `color-mix()` details: https://bsky.app/profile/techniq.dev/post/3lk6qr6e5b22t * Refine getting started * Restore prose heading styling (size/bold/margin) * fix: Support `opacity` prop/style when Canvas rendered for all primatives * docs(LineChart): Fix "Gradient threshold" highlight and tooltip color
techniq
added a commit
that referenced
this pull request
Apr 23, 2025
* Initial migration to Tailwind 4 (and layerstack/svelte-ux @next) * Format project * Update all the non-transparent CSS variables to remove the hard coded `hsl()` (as variable now includes the color function) * fix(LinearGradient): Handle `tw-gradient-[from|to]` no longer inheriting * Cleanup * fix(Spline): Pass `fillOpacity` prop (instead of `fill-opacity`) to support Canvas * Update semi-transparent CSS variable usage to use `opacity`, `fillOpacity` or `color-mix()` depending on the usage * Add changeset * Use `1%` instead of `0%` opacity for gradient examples to workaround gray gradient issue due to TW4's use of `color-mix()` details: https://bsky.app/profile/techniq.dev/post/3lk6qr6e5b22t * Refine getting started * Restore prose heading styling (size/bold/margin) * fix: Support `opacity` prop/style when Canvas rendered for all primatives * docs(LineChart): Fix "Gradient threshold" highlight and tooltip color
Closed
This was referenced Dec 27, 2025
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Resolves #388