Skip to content

Add support for new Tailwind CSS v4.0.0-beta.9 features #1117

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 10 commits into from
Jan 21, 2025

Conversation

thecrypticace
Copy link
Contributor

@thecrypticace thecrypticace commented Jan 7, 2025

  • Add support for @reference (alias for @import "…" reference)
  • Add support for --value()
    • Completions (functional @utility context only)
    • Warning when used in non-functional utility context
    • Syntax highlighting
  • Add support for --modifier()
    • Completions (functional @utility context only)
    • Warning when used in non-functional utility context
    • Syntax highlighting
  • Suggestions inside --value() and --modifier()
    • Theme keys
      • Initial version: Same suggestions as @theme { … }
      • Final version: Compute theme key prefixes and suggest these
        • Ignore nested theme keys (-- separated)
    • Bare value data types
    • Arbitrary value data types
  • Add support for --spacing()
    • Completions (this maybe doesn't make sense — it just takes a number, variable, or just whatever)
    • Syntax highlighting
  • Add support for --theme()
    • Completions
    • Syntax highlighting
  • Add theme() function deprecation warning (v4 only)
    • When using modern variable syntax offer quick fix to --theme(…)

Copy link
Member

@philipp-spiess philipp-spiess left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

thank youuu

@thecrypticace thecrypticace changed the title Add support for @reference Add support for new Tailwind CSS v4.0.0-beta.9 features Jan 9, 2025
@thecrypticace thecrypticace marked this pull request as draft January 9, 2025 16:54
@thecrypticace thecrypticace force-pushed the feat/v4-add-at-reference-support branch from cdda0cb to a1c6dbf Compare January 10, 2025 19:10
@thecrypticace thecrypticace force-pushed the feat/v4-add-at-reference-support branch from fc1dc14 to 73b734d Compare January 21, 2025 14:59
@thecrypticace thecrypticace marked this pull request as ready for review January 21, 2025 15:02
@thecrypticace thecrypticace force-pushed the feat/v4-add-at-reference-support branch from 73b734d to 1b737fb Compare January 21, 2025 16:31
@thecrypticace
Copy link
Contributor Author

While not everything is checked off I'm going to go ahead and merge this to get the basic stuff in. We can improve the DX around the new features in another release.

@thecrypticace thecrypticace merged commit 15c0b84 into main Jan 21, 2025
@thecrypticace thecrypticace deleted the feat/v4-add-at-reference-support branch January 21, 2025 16:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants