- Add support for v4.2
- Fix missing
caret-*andplaceholder-*classes - Fix automatic updater
- Remove unnecessary DLLs
- Fix missing utilities for custom colors from plugins (#133)
- Fix performance and reliability issues with initial
@pluginsupport (#133) - Fix missing descriptions for plugin classes
- Fix incorrect CSS syntax in quick info tooltips
- Allow
{after@pluginin addition to;
- Re-add support for legacy JavaScript plugins in v4 projects (#133)
- Revert
-cremoval from 1.12.6 - Improve verbose build logs to include working directory
- Fix the space before
!importantbeing removed when sorting classes (#132)
- Fix incorrect result when tabbing through completion menu when a modifier and class are added in the same session
- Fix additional
tailwind.extension.jsonfile being added to solution root
- Run build processes in the directory of the input file, not of the configuration file (affects v3 only) --> remove use of
-cto let Tailwind find the correct config file (#131) - Use closest configuration file instead of default configuration file when a file is not explicitly included in a configuration file
- Moved additional solution startup code to the background to improve performance
- Fix incorrect display of
Set up Tailwind CSScommand in Solution Explorer context menu when Tailwind is already installed correctly - Solution startup performance optimizations (#130)
- Fix
tailwind.extension.jsonbeing deleted in v3 projects (#129) - Fix some parsing errors in JS Tailwind plugins
- Fix missing description tooltips for completions when using prefixes in v3 projects
- Fix
PSSecurityExceptionby runningnpx @tailwindcss/cliwith-ExecutionPolicy Unrestrictedif powershell has a security restriction (#120, #125, see also npm/cli#7280) - If a project uses the Tailwind standalone CLI, find the version of that instead of trying to find a local/global npm tailwind installation
- Fix missing color tooltips for
rgbwith commas - Fix incorrect color description if changing its value in a configuration file
- Fix Tailwind CSS updating with npm even if a standalone CLI is configured
- Make razor class sorting respect indents and newlines (based on token count, not character count)
- Add completions for certain missing classes (
max-w-{fraction},min-w-{fraction},mask-{...}-{from|to}-{number or percent})
- Add completion support for
@themevariables - Fix missing descriptions for classes using arbitrary values containing spacing units (i.e.
font-[inherit]!containsin)
- Fix potential NREs when updating Tailwind on project load (#119)
- Add missing
bg-gradient-to-*classes - Properly sort
group-,peer-, breakpoints after all other variants in v3 projects - Fix incorrect detection of configuration files if they contain a newline before
@import "tailwindcss" - Fix certain descriptions not showing up for custom classes
- Add description support for
--text-*--line-height,--text-*--font-weight, and--text-*--letter-spacing
- Show powershell build command in build output when verbose build is toggled
- Show
Set up Tailwind CSScommand in the Solution Explorer context menu when no installation is found (either locally or globally) and no valid standalone CLI configuration is provided, regardless of whether configuration files have already been defined viatailwind.extension.json - Fix an error which could occur when unloading and reloading projects while having a file open
- Fix error "
Identifier 'configuration' has already been declaredin parser.js" (#117)
- Fix razor parsing regex to correctly match
bg-(--var)Tailwind classes - Fix razor parsing regex to correctly match complex classes like
text-@(error ? "red-700" : "green-900")
- Add missing utilities for all color classes: (
{utility}-inherit,{utility}-current,{utility}-transparent) - Put variable values/comments directly after they are referenced in class descriptions
- Prevent all classes from generating (though hidden) in the completion menu when using a modifier on
text-and bg gradient classes - Fix descriptions being truncated when there is more css after a closing brace
- Add support for breakpoints and containers
- Fix razor parsing for functions with the ternary conditional operator (#116)
- Fix razor parsing for functions with string parameters (i.e.
@Foo("bar")) - Properly handle
@@or@("@")escaping in razor, for classes like@@sm:bg-red-500 - Fix an error in v3 projects with a configuration file with no
contentproperty - Fix
.tsfile support for v3 projects
- Handle v4 prefixes that go in the very beginning, separated with a colon
- Bug fixes for classes with the important modifier
- Properly handle arbitrary classes with parenthesis (i.e.
border-x-(--my-var))
- Add Ctrl+1, Ctrl+1 shortcut for default build
- Allow for build
--minifyto be specified on a per-file basis (#115)
- Support blobs for
@source - Fix incorrect configuration file parsing if
@sourcecontained a pattern like/*.razor - Add support for prefixes
- Support
!importantfor v4+ projects (!modifier is at the end, not the beginning) - Fix a
NullReferenceExceptionwhich could occur when having custom classes added - Fix sorting order for classes like
border-2
- Restart build if Tailwind build process runs out of memory (#113)
- Fix missing color previews on cultures that do not use
.as a decimal separator (#104)
- Fix an error which could occur on Visual Studio startup, when no project is open
- Fix an error which could occur when resetting configuration files after deleting/renaming the existing one
- Fix incorrect color previews on cultures that do not use
.as a decimal separator (#104)
OnSaveoverride build should not create an infinite amount of processes- Fix missing descriptions for some numeric classes in projects using v4.1+
- Null blocklist should not cause errors (#104)
- Candidate fix for #104
- Class sorting should respect indents on new lines
- Add certain missing utility classes
- Simplify
tailwind.extension.jsonby removingConfigurationFiles.IsDefaultandConfigurationFiles.ApplicableLocations. The extension now directly parses configuration files to find applicable locations (specified incontentor with@source) - Add blocklist support for v4.1 (
@source not inline(...)) - Fix handling of
color-*andcolor-___-*in@utilitydeclarations - Add Tailwind v4.1 support
- Fix incorrect descriptions for classes like
drop-shadow-{color}andshadow-{color} - Fix inefficient caching of color icons when showing completion menu
- Fix an error which could occur when typing a class with opacity modifier without a color (i.e.
text-/) - Use
powershellinstead ofcmdwhen building with--watch(#111)
- Add a quick info message and Tailwind logos to Tailwind css directives to mitigate confusion with error tags (#105)
- Major version update message should show major version, not minor version
- Handle
@importstatements with additional parameters (#85) - Remove
int/float/byte.Parse()calls to avoid format string errors (#102) - Singleton command filters for completion controllers (#107)
- Reload files referenced through
@configand@import(#85) - Correct class descriptions for ambiguous arbitrary classes (i.e.
text-[10px]) (#108) - Add IntelliSense for missing css directives (
@utility,@custom-variant, etc.)
- Fix an error when using
var(...)in--color-...theme settings (#102) - Handle
@importand@config - Add support for
@utilityand@custom-variant - Color adornments should show up for arbitrary classes with variables (i.e.
text-(--color-blue-100)) - Arbitrary classes with a non-hex, three-digit value show color adornments (i.e. for
rotate-[100]) - Adds modifier support for
bg-conic,bg-linear,bg-radial,text-<size>(i.e.bg-conic/oklch,text-sm/snug)
- Add missing classes (
bg-conic-*,-underline-offset-*, etc.) - Fix incorrect description formatting of
container - Configuration class support for
--color-*and--breakpoint-*
- Fixed a NRE with empty CSS files (#101)
- Fixed errors with completion filters and incorrect string formats (#102)
- Optimize completion efficiency by lazy-loading descriptions
- Added missing descriptions and color adornments for classes like
border-x-amber-50
- Added Tailwind v4 support (#85)
- Updated IntelliSense
- New utilities and variants
- Support for new () syntax (i.e.
bg-green-(--variable))
- Updated build (i.e. use
@tailwindcss/cliinstead) - Updated tooltips for spacing classes and other number/percentage classes
- Parsing support for css files (partial)
- Legacy JS configuration files
- Fixed incorrect sorting for non-spacing numeric classes, color classes with modifiers (i.e.
bg-green-50/50), and forgroup-andpeer-variants
Upcoming --> 1.10.x:
- Plugin /
@importsupport - CSS tailwind directive and theme variable IntelliSense and linting support
- Modifier classes: (/oklch, /srgb for bg-linear, font-size/ for line height)
- Use wanted version instead of latest version when checking for updates
.jsxand.tsxsupport now works again (#98)- Configuration loading should be initialized after project settings have loaded (#97)
- Fix incorrect
.jsxand.tsxcompletion suggestions
- Use existing build processes when running in JIT mode to prevent 100% RAM usage (#84)
- Search through project to find
node_modulesforNODE_PATHwhen parsing configuration files (#87) - Prevent empty configuration files from being generated (#95)
- Automatic updates should consider project
tailwindcssversion, not dependency versions
- Fixed a NRE when setting up Tailwind (#93)
- Adds an option to set up Tailwind using a global installation
- Added multiple project support (#84)
- Fixed a bug which could occur when class contexts are near the end of the file
- Fixed an error which could occur when using
@tailwindcss/container-queries(#90) - Properly apply custom color definitions (i.e.
backgroundColor) when sorting classes
- Added modifier descriptions for quick info tooltips
- Fixed missing support in open folder contexts (#35)
- Show all classes in an empty context (i.e.
class="bg-green-900 |", where|represents the cursor) for a smoother IntelliSense experience - 'Set up and install Tailwind CSS' context menu command now searches for an existing Tailwind configuration file before downloading Tailwind
- Expanded configuration file support to
tailwind.config.{js,cjs,mjs,ts,cts,mts}(#35) - Better modifier descriptions for completion tooltips, excluding screen sizes
- Fixed a NRE which could occur when no configuration file is set
- Fixed a false error when linting CSS patterns similar to
@media screen and (max-width: 768px) { - Classes with overriden colors (i.e.
backgroundColor) should not have color adornments or be considered in linting
- Improved description tooltip for completions
- Fix an error when parsing configuration files with global packages (#87, #89)
- Change
tailwind.extension.jsonto serialize to a human-readable format with default values for all properties - Fixes an error which occurs when removing a configuration file
- Add JSON
$schematotailwind.extension.json(#88)
- Fix a crash which could occur when typing a
\in a class context - Fix corrupt syntax when using libraries like Alpine JS (#86)
- Fix exceptions which could occur when using custom regexes
- Project-based custom regexes (via
tailwind.extension.json), instead of a global definition; checkGetting-Started.mdfor more details
- Move
tailwind.extension.jsonto the root of the project containing the Tailwind configuration file (#81)
- Rewrite class context logic to use regexes to parse files
- Add custom class name completion contexts with custom regexes (#79)
- Add verbose build option (#82)
- Colors would not show up in IntelliSense when using a prefix (#80)
- Use relative pathing when building Tailwind CSS (#82)
- Clarify build type descriptions and add
ManualJITbuild option (#78)
- Support for
!modifier (#76)
- Fix inaccurate color preview locations in
.cssfiles content.transformcauses a crash (#77)
- Add option to turn off color preview in extension settings
- Linter doesn't highlight conflicting classes with colors and spacing
- Legacy ASP.NET Razor editor performance improvements and bug fixes (#72)
- Color preview should work for classes with variants (
hover:,focus:, etc.) (#74)
- Add color preview for color classes (#74)
- Support for IntelliSense in Razor variable declarations (#73)
- Class sorting did not work for
.jsxfiles - Downgrade
System.Text.Jsonto6.0.10to match .NET Framework compatibility (#70)
- Correct
.vsixmanifestassembly versions to prevent version mismatch (#70) - Actually include all DLLs in output
- Include all
System.Text.Jsondependencies in the extension to prevent an error (#70)
blocklistandcorePluginssupport (#69)- Explicitly include
Microsoft.Bcl.AsyncInterfacesDLL in extension to prevent an error (#68)
- Incorrect IntelliSense order for non-color, non-spacing classes (i.e.
opacity-5would appear betweenopacity-40andopacity-50)
- Quick info descriptions for non-spacing, non-color arbitrary classes (#66)
- Fixed an exception which could occur when no
themeis present in the configuration file - Fixed an error which occurred when using
export defaultinstead ofmodule.exports extendvalues should not be overridden when a plugin is defined (#67)- Fixed an error which occurred when reloading the configuration file before other extension components are loaded
- More accurately differentiate between hex values and rgb values in class descriptions
has-[]modifier should now be sorted to the correct spot- Fixed unreliable descriptions for classes using spacing
- Modify incorrect sorting order (#67)
- Added definitions for classes defined in plugins or with custom values (i.e.
min-w-[10px]andbg-[#abcdef]) (#66)
- Null reference exception when opening a
.jsfile not in solution - Fixed an error:
addDefaultsfunction not defined when parsing configuration files with plugins (#65)
- Modified color hint in IntelliSense menu to reflect actual color in some cases (#64)
- Ability to add multiple input/output css files (#46)
- Slight performance boost on solution startup
- Fixed a bug where the update status message does not accurately reflect the newest version
- Removed many status progress bars and animations to reduce clutter
- Referencing
theme()values which internally requirecolors(i.e.({ colors }) => ...) would result in incomplete IntelliSense (#57) - Nested theme values may not be parsed correctly (#62)
!importantshould be sorted to the end of the@applylist (#63)
- Setting to specify files affected by
OnSavebuild option (#61) - Class sorting should respect newlines
System cannot find the path specifiederror (#59)@("")pattern in Razor could affect quick info popup description
- More detailed
cssConflicterror message to show which class takes precedence (#55) sm,md,lg,xl,2xlbreakpoints are now properly sorted- Update assembly version to reflect extension version (#56)
- Automatically add
tailwind.config.jsandtailwind.extension.jsonto project (#52)
- Fix an
ArgumentOutOfRangeExceptionwhen backspacing quotation marks in<div class="..."></div>(related to #54)
- Upgrade
System.Text.Jsonto8.0.4
- Reverted removal of
OnSavebuild option (#50)
- Removed
OnSavebuild option (redundant due to Tailwind JIT) - Added
Manualbuild option, triggered by Ctrl + 1 followed by Ctrl + 2 (#49)
- Configuration files can be
.cjsand.mjsfiles (#44) - Add manual file sorting (#45)
- Set
package.jsonfile path (#47)
- Sort current file does not work (#48)
- Fixed an exception which could occur when triggering IntelliSense on
@tailwinddirectives
- Fix extra apostrophe being appended to class names (#42)
- Fix spontaneous
COMExceptionwhich could occur when opening a project
- Razor order persisted on class sort (i.e.
class="text-gray-100 p-4 @Css"would be sorted toclass="p-4 text-gray-100 @Css") (#40)
- Format broken when sorting classes with Alpine JS, Vue, etc. (#39)
- Added support for
peerandpeer-* - Class sorting in
.html,.ascx,.aspx,.razor,.cshtml,.css,.tcssfiles (#29)
- Fixed an edge case exception which could occur when parsing
.razorfiles - Fixed an exception which could occur when backspacing in
.cssfiles - Fixed an error which could occur when opening a Git compare window
- IntelliSense no longer triggered when backspacing whitespace
- IntelliSense no longer triggered on paste
ts-nodedependency no longer required for.tsfiles
- Certain class descriptions missing (i.e.
max-w-md)
- Support for arm64 (#37)
- Support for standalone Tailwind CSS CLI
- Certain
theme.colorsattributes would not appear in IntelliSense
- Adds support for
.tsfiles as configuration files
- Fixed a
System.IO.FileNotFoundExceptionwhich could occur in rare cases (#31) - Linting, completions, and quick info now work in Razor files when
@is used within class attributes
- Fixed a bug where the
tailwind.extension.jsonfile preferences would be ignored (#32)
- Fixed an exception which could occur when typing in
cssfiles
- Linting support in all related files (#28)
- Error list support
- Linter configuration settings
- Fixed an exception which could occur when Set up Tailwind CSS (#31)
themevalues would sometimes be ignored in configuration files- Fixed a bug where certain classes would still appear despite being overriden
- Added an option in settings to minify builds by default
- Updated IntelliSense to support Tailwind v3.4
- Fixed errors which would occur when using ES modules (#24)
- Fixed an exception which could occur when referencing plugins using
import(#24)
- IntelliSense support for plugins (#24)
- Default IntelliSense may still show up in some cases (#30)
- Added IntelliSense support for
.tcssfiles (#27)
- Using ctrl + space in the middle of a class will now display relevant completions for the entire class
- Fixed an exception which would occur when using
plugins(#26)
- Ability to create minified output css files
- New build option: build once when entire project is built
tailwind.config.jsfiles will automatically be found when opening an existing project (#22)
- Renamed certain menu items to better reflect their purpose (#23)
- Performance improvements when typing
/for transparency variants
- Support for
({ theme })in configuration files
- Minor performance fixes for transparency IntelliSense
- Support for
CssClassin ASP.NET Web Forms controls (#20) - Full description support for
fontSize
- Fixed a bug where custom descriptions would sometimes fail to appear
- Support for
prefixvalues (#19) - Added description support for
fontFamilyanddropShadow(fontSizenot supported)
- Added extra guard clauses for QuickInfo tooltips (#17)
- Moved entire package initialization to be executed on a background thread (performance issues cited in #17)
- Fixed QuickInfo tooltips showing more than 1 description (#17)
- QuickInfo tooltips would not show up with
whitespace-...variants - Fixed an issue where backspacing from the end of a class would not show other completions
- Added
pxvalues for non-spacingremvalues
- IntelliSense now scrolls correctly when filtering (i.e. typing
border-bwill now prioritizeborder-binstead ofborder-blue-*)
- IntelliSense did not show any modifiers (i.e.
active:,focus:) in certain cases - Fixed an exception which would occur when hovering over Tailwind classes before the project was loaded
- Build process would build to default file when adding a new project (related to #14)
- Re-written configuration file parser to support referencing other files (i.e. using
require('tailwindcss/defaultTheme')to reference the default theme) - Added hover tooltips for Tailwind classes
- Error loading
tailwind.config.jswhen certain properties are used (#16)
- Changed Tailwind update check to be asynchronous to prevent UI locking
- Classes would not show up consistently with IntelliSense (#14)
- Spacing mapper now works when local culture uses commas instead of dots (#15)
- Fixed an issue where
tailwind.extension.jsoncould not be found when multiple projects are loaded
- Added null checks where errors could occur (#14)
- Exceptions fixed when IntelliSense triggered with certain configuration files (#8)
- Completions no longer show up in a non-Tailwind project
- IntelliSense now shows up with Blazor components using a
Class=""parameter instead ofclass=""(#12) - Improved IntelliSense filtering: for example, typing
hue-60will now displaybackdrop-hue-rotate-60
- Null reference exception would occur when IntelliSense triggered (#8)
- Build settings are now updated when
tailwind.extension.jsonis directly modified (#11)
- Fixed incorrect descriptions for negative spacing values
- CSS output file becomes null when file does not exist (#11)
- Build menu in an open folder context would not show up (moved toggle to solution explorer folder node)
- Added
pxvalues for spacing in completion descriptions (#9)
- Fixed an exception which would occur with specific configuration files (#8)
- Fixed a bug where custom colors would not show up in IntelliSense
- CSS descriptions for each class (#7)
- Added support for missing configuration values
- rgb() values now supported within
theme.colorsandtheme.extend.colors - Spacing values (i.e. padding, margin) now ordered correctly
- Support for Web Forms files (.aspx, .ascx, .master) (#6)
package.jsonscript would sometimes not update correctly
- IntelliSense shows up if you backspace or type at the end of a class
- Added colons to the end of each modifier for clarity
- Removed modifiers showing up before each completion
- Support for
max-{breakpoint}: - Support for group and all group modifiers
- Fixed a bug where configuration values would not update
- Fixed an error which would occur when backspacing in empty CSS files
- Fixed a bug where completions would not show up
- Support for most configuration specifications
- Added ability to override the default build process or supplement it with a package.json script (#5)
- Added arbitrary completions for all those that support it
- Tailwind completions would persist when switching to another project, even if it does not have Tailwind enabled
- Minor bug fix: wrong method being unsubscribed in
TailwindBuildProcess(#3) - Fixed an issue where the status bar loading animation would continue to play
- Added missing classes
- Better IntelliSense color sorting (#1)
- Contains IntelliSense filtering instead of starts with (#1)
- Status bar and output pane now shows more information on build (time taken, time when built)
- Fixed a bug where CSS completion would not commit
- IntelliSense transparency support for colors (i.e.
bg-green-700/50) - New build option - On Save: runs an
npxbuild command on each file save; can be used if default build option is not reliable
- Fixed more classes which were not previously showing up in IntelliSense
- Fixed certain incorrect/missing classes in IntelliSense
- Build would start in projects with no Tailwind configuration
- Fixed an issue where the
npx tailwind --watchprocess would fail to terminate
- Fixed an error which would sometimes occur when switching between projects