- Move
tailwind.extension.json
to 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
ManualJIT
build option (#78)
- Support for
!
modifier (#76)
- Fix inaccurate color preview locations in
.css
files content.transform
causes 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
.jsx
files - Downgrade
System.Text.Json
to6.0.10
to match .NET Framework compatibility (#70)
- Correct
.vsixmanifest
assembly versions to prevent version mismatch (#70) - Actually include all DLLs in output
- Include all
System.Text.Json
dependencies in the extension to prevent an error (#70)
blocklist
andcorePlugins
support (#69)- Explicitly include
Microsoft.Bcl.AsyncInterfaces
DLL in extension to prevent an error (#68)
- Incorrect IntelliSense order for non-color, non-spacing classes (i.e.
opacity-5
would appear betweenopacity-40
andopacity-50
)
- Quick info descriptions for non-spacing, non-color arbitrary classes (#66)
- Fixed an exception which could occur when no
theme
is present in the configuration file - Fixed an error which occurred when using
export default
instead ofmodule.exports
extend
values 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
.js
file not in solution - Fixed an error:
addDefaults
function 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)
!important
should be sorted to the end of the@apply
list (#63)
- Setting to specify files affected by
OnSave
build option (#61) - Class sorting should respect newlines
System cannot find the path specified
error (#59)@("")
pattern in Razor could affect quick info popup description
- More detailed
cssConflict
error message to show which class takes precedence (#55) sm
,md
,lg
,xl
,2xl
breakpoints are now properly sorted- Update assembly version to reflect extension version (#56)
- Automatically add
tailwind.config.js
andtailwind.extension.json
to project (#52)
- Fix an
ArgumentOutOfRangeException
when backspacing quotation marks in<div class="..."></div>
(related to #54)
- Upgrade
System.Text.Json
to8.0.4
- Reverted removal of
OnSave
build option (#50)
- Removed
OnSave
build option (redundant due to Tailwind JIT) - Added
Manual
build option, triggered by Ctrl + 1 followed by Ctrl + 2 (#49)
- Configuration files can be
.cjs
and.mjs
files (#44) - Add manual file sorting (#45)
- Set
package.json
file path (#47)
- Sort current file does not work (#48)
- Fixed an exception which could occur when triggering IntelliSense on
@tailwind
directives
- Fix extra apostrophe being appended to class names (#42)
- Fix spontaneous
COMException
which 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
peer
andpeer-*
- Class sorting in
.html
,.ascx
,.aspx
,.razor
,.cshtml
,.css
,.tcss
files (#29)
- Fixed an edge case exception which could occur when parsing
.razor
files - Fixed an exception which could occur when backspacing in
.css
files - 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-node
dependency no longer required for.ts
files
- Certain class descriptions missing (i.e.
max-w-md
)
- Support for arm64 (#37)
- Support for standalone Tailwind CSS CLI
- Certain
theme.colors
attributes would not appear in IntelliSense
- Adds support for
.ts
files as configuration files
- Fixed a
System.IO.FileNotFoundException
which 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.json
file preferences would be ignored (#32)
- Fixed an exception which could occur when typing in
css
files
- 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)
theme
values 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
.tcss
files (#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.js
files 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
CssClass
in ASP.NET Web Forms controls (#20) - Full description support for
fontSize
- Fixed a bug where custom descriptions would sometimes fail to appear
- Support for
prefix
values (#19) - Added description support for
fontFamily
anddropShadow
(fontSize
not 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
px
values for non-spacingrem
values
- IntelliSense now scrolls correctly when filtering (i.e. typing
border-b
will now prioritizeborder-b
instead 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.js
when 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.json
could 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-60
will now displaybackdrop-hue-rotate-60
- Null reference exception would occur when IntelliSense triggered (#8)
- Build settings are now updated when
tailwind.extension.json
is 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
px
values 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.colors
andtheme.extend.colors
- Spacing values (i.e. padding, margin) now ordered correctly
- Support for Web Forms files (.aspx, .ascx, .master) (#6)
package.json
script 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
npx
build 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 --watch
process would fail to terminate
- Fixed an error which would sometimes occur when switching between projects