Releases: tailwindlabs/tailwindcss-intellisense
Releases · tailwindlabs/tailwindcss-intellisense
v0.5.2
v0.5.1
v0.4.3
v0.4.2
- Add color decorators for classes and CSS helper functions.
This can be configured with the newtailwindCSS.colorDecorators
setting. - Fix incorrect
cssConflict
warnings. (#136) - Fix completion triggers for "computed" class attributes.
- Disable
invalidApply
lint rule whenapplyComplexClasses
experimental flag is enabled. - Show all classes in
@apply
completion list whenapplyComplexClasses
experimental flag is enabled.
v0.4.1
- Fixed
cssConflict
lint rule when classes apply the same properties but have different scopes (#134) - Fixed JS error when providing diagnostics in the case that IntelliSense is not enabled (#133)
- Fixed config finder incorrectly determining that no config file can be found (#130)
- Fixed class name completion tree when config is a symlink
v0.4.0
- Added linting and quick fixes for both CSS and markup 🚀
- Updated module resolution for compatibility with pnpm (#128)
- The extension now ignores the
purge
option when extracting class names (#131) - Fixed hover offsets for class names which appear after interpolations
v0.3.1
v0.3.0
General
- Added support for string values in Tailwind's
important
option (#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 base
are now included (by default@tailwind base
does 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.includeLanguages
setting: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
, andhbs
languages - Added syntax definition to embedded stylesheets in HTML files
CSS
- Added built-in support for
sugarss
language - Added
theme
(andconfig
) helper hovers - Added
@apply
class name hovers - Added directive completion items with links to documentation
- Added
@tailwind
completion items (preflight
/base
,utilities
,components
,screens
) with links to documentation - Helper completion items that contain the
.
character will now insert square brackets when selected @apply
completion list now excludes class names that are not compatible- Added CSS syntax highlighting in
.vue
files (#15)
JS(X)
v0.3.0-alpha.3
- Added
sugarss
,typescript
,gohtml
,GoHTML
to built-in languages @apply
completion list now excludes class names that are not compatible- Class names from
@tailwind base
are now included (by default@tailwind base
does 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-eex
languages -
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.includeLanguages
setting:{ "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
,javascript
etc.) -
Fixed fsevents not being used on macOS (#112)