v0.14.7

• LSP: Declare capability for handling workspace folder change notifications (#1223)
• Don't throw when resolving paths containing a # character (#1225)
• Show @theme in symbol list in CSS language mode (#1227)
• Don't show syntax error when * appear inside —value(…) and --modifier(…) (#1226)
• Don't show syntax error for theme namespaces inside @theme (#1226)

v0.14.6

• Fix detection when project contains stylesheets that import the "main" stylesheet (#1218)

v0.14.5

• Show light color swatch from light-dark() functions (#1199)
• Ignore comments when matching class attributes (#1202)
• Show source diagnostics when imports contain a layer (#1204)
• Only detect project roots in v4 when using certain CSS features (#1205)
• Update Tailwind CSS v4 version to v4.0.6 (#1207)
• Fix parsing of @custom-variant block syntax containg declarations and/or @slot (#1212)
• Fix display of custom at-rules in symbol listing (#1212)

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

• Don't suggest --font-size-* theme keys in v4.0 (#1150)
• Fix detection of Tailwind CSS version when using Yarn PnP (#1151)
• Add support for v4.x insiders builds (#1123)

v0.14.1

• Fix detection of TypeScript config paths on Windows (#1130)

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

• Stop auto-switching CSS files to the Tailwind CSS language mode (#1116)
• Reload v4 design system when dependencies change (#1119)

Note: The language server now follows the same versioning scheme as the VSCode extension

v0.12.17

• Show theme values in comments in later v4 betas (#1092)