Releases: tailwindlabs/tailwindcss-intellisense
Releases · tailwindlabs/tailwindcss-intellisense
v0.14.4
- Ensure hover information for
theme(…)
and other functions are shown when used in@media
queries (#1172) - Treat
<script lang=“tsx”>
as containing JSX (#1175) - Add support for
static
theme option (#1176) - Add details about theme options when hovering (#1176)
- Fix parsing of
@custom-variant
shorthand in Tailwind CSS language mode (#1183) - Make sure custom regexes apply in Vue
<script>
blocks (#1177) - Fix suggestion of utilities with slashes in them in v4 (#1182)
- Assume 16px font size for
1rem
in media queries (#1190) - Show warning when loading a config in v3 fails (#1191)
- Better handle really long class lists in attributes and custom regexes (#1192)
- Add support for Astro’s template literal attributes (#1193)
- Match custom class regex in Vue templates (#1194)
- Support directory imports in plugins for
index.{ts,cts,mts}
(#1198)
v0.14.3
- Allow v4.0 projects not installed with npm to use IntelliSense (#1157)
- Ignore preprocessor files when looking for v4 configs (#1159)
- Allow language service to be used in native ESM environments (#1122)
- Don't create v4 projects for CSS files that don't look like v4 configs #1164
- Support property and variable completions inside
@utility
(#1165) - Support style-rule like completions inside
@custom-variant
(#1165) - Support style-rule like completions inside
@variant
(#1165) - Make sure
@slot
isn't considered an unknown at-rule (#1165) - Fix equivalent calculation when using prefixes in v4 (#1166)
- Fix use of
tailwindCSS.experimental.configFile
option when using the bundled version of v4 (#1167) - Recursively resolve values from the theme (#1168)
- Handle theme keys containing escaped commas (#1168)
- Show colors for utilities when they point to CSS variables contained in the theme (#1168)
v0.14.2
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)