Releases: tailwindlabs/tailwindcss-intellisense
Releases · tailwindlabs/tailwindcss-intellisense
v0.14.1
v0.14.0
- Don't break when importing missing CSS files (#1106)
- Resolve CSS imports as relative first (#1106)
- Add TypeScript config path support in v4 CSS files (#1106)
- Add support for
@custom-variant
(#1127) - Add variant suggestions to
@variant
(#1127) - Don't suggest at-rules when nested that cannot be used in a nested context (#1127)
- Make sure completions work when using prefixes in v4 (#1129)
- Add support for
@reference
(#1117) - Add support for
--theme(…)
,--utility(…)
, and--modifier(…)
(#1117) - Add basic completions for
--utility(…)
and--modifier(…)
(#1117)
v0.12.18
v0.12.17
v0.12.16
v0.12.15
v0.12.14
- Add suggestions for theme options (#1083)
- Add suggestions when using
@source "…"
andsource(…)
(#1083) - Show brace expansion when hovering
@source
(#1083) - Highlight
source(…)
,theme(…)
, andprefix(…)
when used with@import "…"
(#1083) - Highlight
@tailwind utilities source(…)
(#1083) - Show document links when using
source(…)
(#1083) - Ensure language server starts as needed (#1083)
- Don't show syntax errors when using
source(…)
,theme(…)
, orprefix(…)
with@import "…"
(#1083) - Don't show warning when using
@tailwind utilities source(…)
(#1083) - Don't suggest TypeScript declaration files for
@config
,@plugin
, and@source
(#1083) - Don't link Windows-style paths in
@source
,@config
, and@plugin
(#1083) - Warn on invalid uses of
source(…)
,@source
,@config
, and@plugin
(#1083) - Warn when a v4 project uses an old
@tailwind
directive (#1083)
v0.12.13
- Fix display of color swatches using new v4 oklch color palette (#1073)
- Properly validate
theme(…)
function paths in v4 (#1074) - Support loading TypeScript configs and plugins in v4 projects (#1076)
- Show colors for logical border properties (#1075)
- Show all potential class conflicts in v4 projects (#1077)
- Lookup variables in the CSS theme (#1082)
- Auto-switch CSS files to tailwindcss language in valid projects (#1087)