Releases: tailwindlabs/tailwindcss-intellisense
v0.3.0
General
- Added support for string values in Tailwind's
importantoption (#96) - Removed all unnecessary logs (#91)
- Added support for components in addition to utilities (#67)
- Added description to custom variant completion items where possible
- Config parsing errors are now displayed in the VS Code UI
- Class names from
@tailwind baseare now included (by default@tailwind basedoes not include any class names but plugins may contribute them) - Color swatches can now be displayed for rules with multiple properties and/or colors with variable alpha (#113)
- Added
tailwindCSS.includeLanguagessetting:This setting allows you to add additional language support. The key of each entry is the new language ID and the value is any one of the extensions built-in languages, depending on how you want the new language to be treated (e.g.{ "tailwindCSS.includeLanguages": { "plaintext": "html" } }html,css, orjavascript)
HTML
- Added built-in support for
liquid,aspnetcorerazor,mustache,HTML (EEx),html-eex,gohtml,GoHTML, andhbslanguages - Added syntax definition to embedded stylesheets in HTML files
CSS
- Added built-in support for
sugarsslanguage - Added
theme(andconfig) helper hovers - Added
@applyclass name hovers - Added directive completion items with links to documentation
- Added
@tailwindcompletion items (preflight/base,utilities,components,screens) with links to documentation - Helper completion items that contain the
.character will now insert square brackets when selected @applycompletion list now excludes class names that are not compatible- Added CSS syntax highlighting in
.vuefiles (#15)
JS(X)
v0.3.0-alpha.3
- Added
sugarss,typescript,gohtml,GoHTMLto built-in languages @applycompletion list now excludes class names that are not compatible- Class names from
@tailwind baseare now included (by default@tailwind basedoes not include any class names but in theory plugins can contribute them) - Improved completion triggers, in particular for template interpolations
- Added syntax definition to embedded stylesheets in HTML files
v0.3.0-alpha.2
-
Added built-in support for
mustache,HTML (EEx), andhtml-eexlanguages -
Color swatches can now be displayed for rules with multiple properties and/or colors with variable alpha (#113)
-
Fixed display of rules with multiple values for a single property
-
Added
tailwindCSS.includeLanguagessetting:{ "tailwindCSS.includeLanguages": { "plaintext": "html" } }This setting allows you to add additional language support. The key of each entry is the new language ID and the value is any one of the extensions built-in languages, depending on how you want the new language to be treated (e.g.
html,css,javascriptetc.) -
Fixed fsevents not being used on macOS (#112)
v0.3.0-alpha.1
It's been a long time coming (sorry!) but the extension has had a bit of a restructure, which has fixed some bugs, enabled some new features, and laid the groundwork for some really cool upcoming features.
I'm dropping an initial pre-release here for brave people to try out, and I will be looking to release a new version of the extension after a bit more testing. To install go to the Extensions panel in VS Code and click on the "three-dot" button. From there, select Install from VSIX... and select the vscode-tailwindcss-0.3.0-alpha.1.vsix file
I appreciate anyone taking the time to try this out and provide feedback. I have a bit more free time at the moment to spend on the extension, and I want to make it as good as it can be!
Please be aware that as usual the extension will only activate if you have a Tailwind config file (
**/{tailwind,tailwind.config,tailwind-config,.tailwindrc}.js) somewhere in your workspace and have thetailwindcsspackage installed
General
- Added support for string values in Tailwind's
importantoption (#96) - Removed all unnecessary logs (#91)
- Added support for components in addition to utilities (#67)
- Added CSS syntax highlighting in
.vuefiles (#15) - Added
liquid,aspnetcorerazor, andhbslanguages - Added description to custom variant completion items where possible
- Config parsing errors are now displayed in the VS Code UI
CSS
- Added
theme(andconfig) helper hovers - Added
@applyclass name hovers - Added directive completion items with links to documentation
- Added
@tailwindcompletion items (preflight/base,utilities,components,screens) with links to documentation - Fixed
@screencompletion item order - Helper completion items that contain the
.character will now insert square brackets when selected