Changelog
All notable changes to this project will be documented in this file.
Unreleased
Breaking Changes
- We have moved to the quicker
sass-embedded. Closes #327
This uses the latest compiler, but drops these settings:liveSassCompile.settings.formats[].linefeedliveSassCompile.settings.formats[].indentTypeliveSassCompile.settings.formats[].indentWidth
Note: these 3 would’ve been dropped for SASS 2.0 anywayliveSassCompile.settings.useNewCompiler
- Those who historically used
useNewCompilerwill find that source contents are no longer included inline by default.
To restore the old behaviour, setgenerateMapIncludeSourcestotrue. - Requires VS Code v1.95 or later
Added
- New
formats[].generateMapIncludeSourcessetting allows you to decide on map output on a format basis. By default, they aren’t included
TheliveSassCompile.settings.generateMapIncludeSourcesis applied if the formats setting isnull(its default).
Changed
- Switched from
sass@1.89.2tosass-embedded@1.89.2- as mentioned above - Start-up optimisation for when compiling is done upon launch (in larger projects)
Updated
picomatchto4.0.3Changelog- Various dev dependency updates (nothing user facing)
Other
- Fixed broken tests and added added several new tests
- Added test badge to README & changed badge formats
- Added funding link to README &
package.json - Code formatting and linting
6.1.4 - 2025-07-24
Fixed
- Silence legacy API warnings (N/A to those using the
useNewCompilersetting). Closes #405
Changes
publish.ymlnow uses the latest action releases and also adds the VSIX to releases
6.1.3 - 2025-07-21
Updated
sassto1.89.2Changelogfdirto6.4.6Changelogpostcssto8.5.6Changelogautoprefixerto10.4.21Changelog- Various dev dependency updates (nothing user facing)
6.1.2 - 2023-11-22
Fixed
- Fix for a network file-resolution bug introduced in v6.1.1. Closes #322
Updated
sassto1.69.5Changelogfdirto6.1.1Changelogpicomatchto3.0.1Changelogpostcssto8.4.31Changelogautoprefixerto10.4.16Changelog- Various dev dependency updates (nothing user facing)
6.1.1 - 2023-08-18
Changes
- Updated sass to v1.66.0 to revert breaking change
“Drop support for the additional CSS calculations defined in CSS Values and Units 4. Custom Sass functions whose names overlapped with these new CSS functions were being parsed as CSS calculations instead, causing an unintentional breaking change outside our normal compatibility policy for CSS compatibility changes”
Updated
sassto1.66.0Changelogfdirto6.1.0Changelogpostcssto8.4.28Changelogautoprefixerto10.4.15Changelog- Various dev dependency updates (nothing user facing)
6.1.0 - 2023-08-12
Added
- New
formats[].generateMapsetting allows you to decide on map output on a format basis
TheliveSassCompile.settings.generateMapis applied if this setting isnull(its default).
Changes
formats[].extensionNamenow allows any string ending with.csswithout throwing a warning.- Tweaks to docs, reflecting the settings changes and correcting outdated info too
Updated
sassto1.65.1Changelogfdirto6.0.2Changelogpostcssto8.4.27Changelog- Various dev dependency updates (nothing user facing)
6.0.6 - 2023-07-21
Fixed
- Corrected some setting types to stop warnings for valid values
Changes
- Updated docs to remove typos and references to dead settings and outdated info
Updated
sassto1.62.1Changelogpostcssto8.4.26Changelog- Various dev dependency updates (nothing user facing)
6.0.5 - 2023-04-09
Fixed
- Fix for a
formats[].savePathbug introduced in 6.0.4
Updated
sassto1.61.0Changelog- Various dev dependency updates (nothing user facing)
6.0.4 - 2023-03-28
Fixed
formats[].savePathno longer throws a warning for the valid path/- Closes #282
Updated
sassto1.60.0Changelogautoprefixerto10.4.14Changelog- Various dev dependency updates (nothing user facing)
6.0.3 - 2023-02-24
Fixed
- Using the new compiler (
liveSassCompile.settings.useNewCompiler) outputs source maps correctly - Closes #276
Updated
sassto1.58.3Changelog- Various dev dependency updates (nothing user facing)
6.0.2 - 2023-02-09
Fixed
- Prevent
picomatcherror - Closes #267
6.0.1 - 2023-02-09
Changed
- Corrected information about the new
liveSassCompile.settings.useNewCompilersetting - Updated the docs: fixed a link and also corrected references to the new minimum VS Code version (1.74)
- Tweaked some code to make it slightly more performant when processing many workspaces or many files
Updated
fdirto6.0.1Changelog
6.0.0 - 2023-02-07
Breaking changes
- The following deprecated settings have been removed:
liveSassCompile.settings.formats[].savePathSegmentKeysliveSassCompile.settings.formats[].savePathReplaceSegmentsWith- Note: other deprecated settings will remain in place to maintain backwards compatibility, or until SASS2.0
- Requires VS Code v1.74 or later
Added
- New
liveSassCompile.settings.useNewCompilersetting. Try the new, more performant, SASS compiler - go on, kick the tyres on this new entry point. Note:lineFeed,indentTypeandindentWidthdo not work in this new compiler (and never will [ref])
Fixed
debugFileListcommand now correctly includes the files that fall under the excluded and partial patterns- All node module paths are now resolved correctly (when utilising the
~/[node module name]/file_pathfeature) - Any output (
Informationor higher) is saved in the output window. It still only pops up depending on your setting.
This is to match the original extension.
Updated
autoprefixerto10.4.13Changelogfdirto5.3.0Changelogpostcssto8.4.21Changelogsassto1.58.0Changelog- Various dev dependency updates (nothing user facing)
Changes
- Document changes to reflect the new and removed Settings
- Switched from webpack to rollup for a more optimised package
5.5.1 - 2022-07-11
Fixed
- Can now create required output directories when using
savePathReplacementPairs- Closes: #200
5.5.0 - 2022-07-09
Added
liveSassCompile.settings.formats[].savePathReplacementPairs- Closes #189- You can now apply
savePathand then key replacement (savePathReplacementPairs) to get to your desired save location - Closes #184, #187,
Deprecated
- The new method for replacing segments in the save path is
savePathReplacementPairsliveSassCompile.settings.formats[].savePathSegmentKeysliveSassCompile.settings.formats[].savePathReplaceSegmentsWith
- When SASS v2 is released these settings will be removed, adding deprecation warning now so it can be implemented sooner
liveSassCompile.settings.formats[].linefeedliveSassCompile.settings.formats[].indentTypeliveSassCompile.settings.formats[].indentWidth
Fixed
- Stopped output if not watching and working on a single SASS file
- The status bar now only updates once when working on many files. This means that the result shows the overall outcome, rather than the status of the last file
Updated
sassfrom1.51.10to1.53.0- Preserve location of trailing loud comments (
/* ... */) instead of pushing the comment to the next line - Add support for calling
var()with an empty second argument, such asvar(--side, ) - Fix a bug where
meta.load-css()would sometimes resolve relative URLs incorrectly when called from a mixin using the legacy JS API - Other changes (nothing user facing)
- Preserve location of trailing loud comments (
- Various dev dependency updates (nothing user facing)
5.4.0 - 2022-05-19
Added
- New
liveSassCompile.settings.rootIsWorkspacesetting- Treat a leading slash in imports as relative to the workspace, not the drive root
- New
liveSassCompile.settings.showAnnouncementssetting- Toggle whether or not to show announcements when a new version is installed
- Reference a node module with a leading tilde
~- Instead of trailing back to your node modules folder you can now reference one directly with
~myModuleor~/myModule
- Instead of trailing back to your node modules folder you can now reference one directly with
Changes
- When running the
liveSass.command.createIssuecommand, the issue title reflects whether a known error occurred or not - Details the under the bonnet workings - Closes #176
- Simplified read me
- Documented new settings
- Added our open source commitment
Updated
autoprefixerfrom10.4.4to10.4.7- Fixed
print-color-adjustsupport - Other changes (nothing user facing)
- Fixed
postcssfrom8.4.12to8.4.14- Other changes (nothing user facing)
sassfrom1.49.10to1.51.0@extendnow treats:where()the same as:is()- Potentially breaking change: Change the order of maps returned by
map.deep-merge()to match those returned bymap.merge(). All keys that appeared in the first map will now be listed first in the same order they appeared in that map, followed by any new keys added from the second map. - Other changes (nothing user facing)
- Various dev dependency updates (nothing user facing)
5.3.1 - 2022-03-31
Updated
autoprefixerfrom10.4.2to10.4.4- Other changes (nothing user facing)
postcssfrom8.4.5to8.4.12- Various changes (nothing user facing)
sassfrom1.49.8to1.49.10- Quiet deps mode now silences compiler warnings in mixins and functions that are defined in dependencies even if they’re invoked from application stylesheets.
- In expanded mode, Sass will now emit colors using
rgb(),rbga(),hsl(), andhsla()function notation if they were defined using the corresponding notation. As per our browser support policy, this change was only done once 95% of browsers were confirmed to support this output format, and so is not considered a breaking change.
Note that this output format is intended for human readability and not for interoperability with other tools. As always, Sass targets the CSS specification, and any tool that consumes Sass’s output should parse all colors that are supported by the CSS spec. - Fix a bug in which a color written using the four- or eight-digit hex format could be emitted as a hex color rather than a format with higher browser compatibility.
- Calculations are no longer simplified within supports declarations
- Various changes (nothing user facing)
- Various dev dependency updates (nothing user facing)
Other
- Tweaked the publish action to allow easier publishing
5.3.0 - 2022-03-13
Fixed
- Stopped outputting a workspace warning when saving a none SASS file - Closes #160
Added
- Made changes for easier migration from the original extension - Closes #159
- Re-added
showOutputWindowas a deprecated setting. Then whenfalseis provided it only outputs atWarningand above - Allowed
nullin theautoprefixersetting. This works the same as providingfalse
- Re-added
Other
- Document changes to reflect the changes made in this release
- Showed correct message for disabling autoprefix setting (was
null, supposed to befalse)
5.2.0 - 2022-02-21
Added
@warnand@debuglines, as well as other SASS warnings, are now shown in the output window - Closes #89- You can now specify the files/folders to treat as partials using the new
liveSassCompile.settings.partialsListsetting - Closes #143
Changes
- Updated docs to reflect new setting and also included previous changes in the FAQ
- Further logging in a function at
Tracelevel
Fixed
- Stopped returning false negatives when checking if a file should trigger compilation thanks to a bump to
fdir- Closes #145 - Use actual saved file rather that finding active file (helps with Live Share compatibility) - Partial fix for #151
- Workspace loop numbering outputs the correct figure
- Update broken reference link in settings documentation - thanks @dawidmachon
- Source maps would add duplicates, mostly with incorrect paths - Fixes #135
- Extension checks are no longer case sensitive (i.e.
.Sasswill now match) - Fixes #137 - Valid save paths in the
liveSassCompile.settings.formatssetting no longer throws a warning - Fixes #139 - No longer outputs error if the css generated is an empty string - Fixes #140
Updated
autoprefixerfrom10.3.7to10.4.2- Added
:autofillsupport - Fixed
::file-selector-buttondata - Fixed missed
-webkit-prefix forwidth: stretch
- Added
fdirfrom5.1.0to5.2.0- Fixed a critical issue with async crawling that caused the crawler to return early
- Other changes (nothing user facing)
picomatchfrom2.3.0to2.3.1- Fixes bug when a pattern containing an expression after the closing parenthesis (
/!(*.d).{ts,tsx}) was incorrectly converted to regexp - Other changes (nothing user facing)
- Fixes bug when a pattern containing an expression after the closing parenthesis (
postcssfrom8.3.9to8.4.5- Various changes (nothing user facing)
sassfrom1.37.5to1.49.8- Potentially breaking bug fix: Change the default value of the
separatorparameter fornew SassArgumentList()to','rather thannull. This matches the API specification. - Potentially breaking bug fix: Properly parse custom properties in
@supportsconditions. Note that this means that SassScript expressions on the right-hand side of custom property@supportsqueries now need to be interpolated, as per https://sass-lang.com/d/css-vars. - Potentially breaking bug fix: Fix a bug where
inspect()was not properly printing nested, empty, bracketed lists. - In expanded mode, emit characters in Unicode private-use areas as escape sequences rather than literal characters.
- Fix a bug where quotes would be omitted for an attribute selector whose value was a single backslash.
- Properly consider numbers that begin with
.as “plain CSS” for the purposes of parsing plain-CSSmin()andmax()functions. - Allow
ifto be used as an unquoted string. - Properly parse backslash escapes within
url()expressions. - Fix a couple bugs where
@extends could be marked as unsatisfied when multiple identical@extends extended selectors across@userules. - Add a
charsetoption that controls whether or not Sass emits a@charset/BOM for non-ASCII stylesheets. min()andmax()expressions are once again parsed as calculations as long as they contain only syntax that’s allowed in calculation expressions. To avoid the backwards-compatibility issues that were present in 1.40.0, they now allow unitless numbers to be mixed with numbers with units just like the globalmin()andmax()functions. Similarly,+and-operations withinmin()andmax()functions allow unitless numbers to be mixed with numbers with units.- Fix a bug where Sass variables and function calls in calculations weren’t being resolved correctly if there was a parenthesized interpolation elsewhere in the file.
- Add support for the
loggeroption. This takes an object that can definewarnordebugmethods to add custom handling for messages emitted by the Sass compiler. See the JS API docs for details. Please note: this will now print warnings for any divisions using/, please use the newmath.div(100, 20)function orcalc(100 / 20) - Improve the error message when the default namespace of a
@userule is not a valid identifier. - Improve performance
- Fix a bug where calculations with different operators were incorrectly considered equal.
- Properly parse attribute selectors with empty namespaces.
- Various changes (nothing user facing)
- Potentially breaking bug fix: Change the default value of the
- Various dev dependency updates (nothing user facing)
5.1.1 - 2021-10-11
Fixed
- Implemented strict checks to reduce chances of unhandled errors - Closes #128
Updated
postcssfrom8.3.6to8.3.9- Replaced
colorettewithpicocolors - Other changes (nothing user facing)
- Replaced
autoprefixerfrom10.3.1to10.3.7- Fixed
::file-selector-buttonsupport - Fixed
stretchvalue in latest Firefox - Reduced package size
- Replaced
colorettewithpicocolors - Other changes (nothing user facing)
- Fixed
- Various dev dependency updates (nothing user facing)
5.1.0 - 2021-08-06
Fixed
- The UI description for
showOutputWindowOnwas stating the default isWarningwhen, in fact, it isInformation - File searching is no longer case sensitive - it is still accent sensitive
- Stopped outputting
Watching...twice when compilation happens on watching - A single file - that is a window without a workspace - would error and not compile
Change detected - {DateTime}is now output whenshowOutputOnis set to"Information". This better reflects the functionality of the original extension
Added
- New settings to support all other SASS output formatting options - Closes #82
The new settings are:liveSassCompile.settings.formats.linefeed- control the line terminator usedliveSassCompile.settings.formats.indentType- control whether indents are spaces or tabsliveSassCompile.settings.formats.indentWidth- control the width of the indentation
- New commands to change the
showOutputOnfrom the command pallete - Closes #63
Having these commands in the pallete also means that key combos can be set for each
The new commands are:liveSass.command.showOutputOn.traceliveSass.command.showOutputOn.debugliveSass.command.showOutputOn.informationliveSass.command.showOutputOn.warningliveSass.command.showOutputOn.errorliveSass.command.showOutputOn.none
Changes
- Added more and adjusted some logging messages (primarily to
Tracelevels) - A lot of documentation tweaks
- Some linting tweaks (nothing user facing)
Updated
sassfrom1.32.12to1.37.5- Potentially breaking bug fix: Properly throw an error for Unicode ranges that have too many
?s after hexadecimal digits, such asU+12345?? - Potentially breaking bug fix: Fixed a bug where certain local variable declarations nested within multiple
@ifstatements would incorrectly override a global variable. It’s unlikely that any real stylesheets were relying on this bug, but if so they can simply add!globalto the variable declaration to preserve the old behaviour - Fix an edge case where
@extendwouldn’t affect a selector within a pseudo-selector such as:is()that itself extended other selectors - Fix a couple bugs that could prevent some members from being found in certain files that use a mix of imports and the module system.
- Fix incorrect recommendation for migrating division expressions that reference namespace variables.
- Potentially breaking bug fix: Null values in
@useand@forwardconfigurations no longer override the!defaultvariable, matching the behaviour of the equivalent code using@import. - Use the proper parameter names in error messages about
string.slice - Deprecate the use of
/for division. The newmath.div()function should be used instead. See this page for details. - Add a
list.slash()function that returns a slash-separated list. - Potentially breaking bug fix: The heuristics around when potentially slash-separated numbers are converted to slash-free numbers—for example, when
1/2will be printed as0.5rather than1/2—have been slightly expanded. Previously, a number would be made slash-free if it was passed as an argument to a user-defined function, but not to a built-in function. Now it will be made slash-free in both cases. This is a behavioural change, but it’s unlikely to affect any real-world stylesheets. :is()now behaves identically to:matches().- Fix a bug where non-integer numbers that were very close to integer values would be incorrectly formatted in CSS.
- Fix a bug where very small number and very large negative numbers would be incorrectly formatted in CSS.
- Fix the URL for the
@-moz-documentdeprecation message. - Fix a bug with
@forloops nested inside property declarations.` - Fix a couple bugs that could prevent some members from being found in certain files that use a mix of imports and the module system.
- Fix incorrect recommendation for migrating division expressions that reference namespace variables
- Fix a bug where the quiet dependency flag didn’t silence warnings in some stylesheets loaded using
@import - Other changes (nothing user facing)
- Potentially breaking bug fix: Properly throw an error for Unicode ranges that have too many
autoprefixerfrom10.2.5to10.3.1- Added
::file-selector-buttonsupport - Fixed adding wrong prefixes to
content - Fixed “no prefixes needed” warning
- Added
postcssfrom8.2.14to8.3.6- Fixed column in
missed semicolonerror - Source map performance improvements
- Fixed broken AST detection
- Other changes (nothing user facing)
- Fixed column in
fdirfrom5.0.0to5.1.0- Performance & memory usage has also been greatly improved due to the many internal refactoring
- Other changes (nothing user facing)
picomatchfrom2.2.3to2.3.0- Fixes bug where file names with two dots were not being matched consistently with negation
extglobscontaining a star
- Fixes bug where file names with two dots were not being matched consistently with negation
- Various dev dependency updates (nothing user facing)
5.0.4 - 2021-06-22
Security
- Bumped
glob-parentto5.1.2- eliminate ReDoS
5.0.3 - 2021-05-05
Changes
- The default for
liveSassCompile.settings.showOutputWindowOnis nowInformation - Updated the documentation to match the above change - and also sorted a couple of typos
- Removed reference to live reload in
package.json
Updated
postcssfrom8.2.10to8.2.14- Fixed ReDoS vulnerabilities in source map parsing
- Other small changes (nothing user facing)
sassfrom1.32.11to1.32.12- Fix a bug that disallowed more than one module from extending the same selector from a module if that selector itself extended a selector from another upstream module.
- Various dev dependency updates (nothing user facing)
5.0.2 - 2021-04-19
Updated
picomatchfrom10.2.4to10.2.5- Do not skip pattern separator for square brackets
- Other small changes (nothing user facing)
postcssfrom8.2.9to8.2.10- Fixed ReDoS vulnerabilities in source map parsing
- Other small changes (nothing user facing)
sassfrom1.32.8to1.32.11- Small changes (nothing user facing)
- Various dev dependency updates (nothing user facing)
5.0.1 - 2021-04-07
Fixed
- Bump to stop installation issues caused by original RC uploads (#54)
Changes
- No extension changes
5.0.0 - 2021-04-06
Breaking changes
- Not dependant on
ritwickdey.LiveServeras there was no actual code dependencies in the extension (#23). If you require the Live Server extension, it can still be installed from here - Changes to the
showOutputWindowsetting, now calledshowOutputWindowOn(#26)- The system now acts as more of a logger rather than a mass of information
- Accepted values are now
Trace,Debug,Information,Warning,ErrororNone - The default is now
Warning
- Changes to
autoprefixsettings (#41)- The default is now
defaults(as per Autoprefixer recommendations) - The setting no longer accepts
string[] OR null, but astring[] OR boolean- Rather than
null, you now usefalse
- Rather than
- The default is now
- No longer supporting
brace expansionglob patterns (#27)- This is because the underlying glob pattern matching has moved from
minimatchtopicomatch. A full feature comparison can be found here
- This is because the underlying glob pattern matching has moved from
- Only works on VS Code v1.52 and newer (#34)
- Settings have been updated for continuity and to better aid extension performance (#30)
formats[].savePathmust start with a path separator but not end in oneincludeItemsmust start with a path separator and end in either.sassor.scss(for performance purposes)forceBaseDirectorymust start with a path separator but not end in one
Added
-
When
autoprefixis true we will search for either:- a
.browserlistsrcfile or, "browserslist": [ string[] ]in apackage.jsonfile
(This allows you to use the same setting across your solution, rather than duplicating content)
- a
- Increased range of glob pattern support
- Full support for
extglobs - Added support for
posix brackets - Added support for
regex syntax - Full comparison can be found here
- Full support for
- When a change is detected the initial output now includes a date and time stamp - See this comment on #26
Fixed
- Fixed: the
formats[].savePathSegmentKeyssetting would allow non string values in the array - Fixed: the
excludeListsetting would allow non string values in the array - Fixed: the
includeItemssetting would allow non string values in the array - Fixed: the
autoprefixsetting would allow non string values in the array - Fixed: some setting descriptions have been updated for better clarity/readability
- Error catching no longer fails when the error is with finding SASS files. Instead, this fact is highlighted
Updated
autoprefixerfrom10.2.4to10.2.5- Fixed
:support in@supports
- Fixed
postcssfrom8.2.4to8.2.9- Small fixes (nothing user facing)
sassfrom1.32.5to1.32.8- Allow
@forward...withto take arguments that have a!defaultflag without a trailing comma. - Improve the performance of unitless and single-unit numbers.
- Other small changes (nothing user facing)
- Allow
- Various dev dependency updates (nothing user facing)
Changed
- Now using
fdirwithpicomatchinstead ofglobandminimatch- Speed improvements, the most significant of which will be on larger projects
- Greater support for glob patterns
- A lot of documentation tweaks
4.4.1 - 2021-01-31
Fixed
- Fixed:
forceBaseDirectoryhas full support in multi-root workspaces - Fixed: the path in
forceBaseDirectoryis now checked to see if it exists. If not a user friendly message is displayed in the output - Fixed: an error when checking files would still compile what it could. This would hide the error message from the user
- Incorrect pattern matches in settings show user friendly messages rather than “does not match pattern”
4.4.0 - 2021-01-31
Added
- New setting:
liveSassCompile.settings.forceBaseDirectory#25- A new setting that can help performance in large projects with few Sass/Scss files.
Note: multi-root workspace with different folder structures can not use this efficiently (See setting note & VS Code Feature Request (:+1: it) )Fixed in v4.4.1
- New feature: The status bar
ErrorandSuccessmessages can be clicked which will open the Output Window #25
Updates
autoprefixerfrom10.2.1to10.2.4- Small bug fixes (nothing user facing)
- Various dev-dependency updates
Fixed
- Part fix: Slow file handling #22. Full fix in v5 as some small breaking changes
- The glob pattern matcher is causing bottlenecks, reducing load calls with small patch. However moving away from glob is the end-game (which will be happening in v5)
- Fix:
compileCurrentSassshows wrong message on fail- When you run
compileCurrentSassand it would fail (for whatever reason) it would cause the output to showSuccessrather thanError(just the output was wrong, nothing else)
- When you run
- Fix: Status bar inconsistencies during display changes
- When command bar is changing between visuals it was possible to cause the status and the shown message to be out of sync (due to clicks while setTimeouts are pending), the setup also meant you couldn’t sync them again (unless you did a manual compile command)
4.3.4 - 2021-01-21
Fixed
- Fixed #18: On launch there is no output, nor any
Live SASS Compileoutput selection, when the settingwatchOnLaunchistrue - Fixed: Autoprefixer warning saying
undefinedfor file path whengenerateMapisfalse - Fixed: Autoprefixer
grid: "autoplace"was forced- If this feature is wanted then add
/* autoprefixer grid: autoplace */to the start of your file
- If this feature is wanted then add
Updates
sassfrom1.32.4to1.32.5- Potentially breaking bug fix: When using @for with numbers that have units, the iteration variable now matches the unit of the initial number. This matches the behaviour of Ruby Sass and LibSass.
- Others: see sass release notes
4.3.3 - 2021-01-18
Fixed
- Fixed #15: No longer outputs absolute path in map file and map link in CSS output
- Reinstated feature of partial files being checked for exclusion
- Autoprefixer map lines now relate to actual SASS files rather than the CSS file generated
- When there’s an include list, a non partial file that’s not “included” would still be processed
- Now gets the correct list of included partial files
4.3.2 - 2021-01-15
Fixed
- Now handle errors caused by incorrect autoprefixer browser queries
- Corrected output for unhandled errors that get output when running “Report an issue” from the command
liveSass.command.createIssue
Updates
sassfrom1.30.0to1.32.4- Various changes, see their changelog
autoprefixerfrom10.1.0to10.2.1- Fixed transition-property warnings (by @Sheraff).
- Other, non-facing changes
eslintfrom7.16.0to7.17.0ts-loaderfrom8.0.12to8.0.14postcssfrom8.2.1to8.2.4vscode-testfrom1.4.0to1.4.1webpackfrom5.11.0to5.14.0webpack-clifrom4.2.0to4.3.0
4.3.1 - 2021-01-09
Fixed
- Fixed #10: Partial SASS files not triggering compilation of all files
- Correction of output when running
liveSass.command.debugInclusionand the file is excluded
4.3.0 - 2021-01-06
Added
- Support for workspaces with multiple folders
Changed
- Out of preview!
- Small optimisation to some underlying async operations
Other
- Small bit of general tidying, adjustment to README, new dev dependency for @.types/glob
4.2.0 - 2020-12-22
Added
- New debugging items
- Two settings:
liveSass.command.debugInclusionto check that a current file will be included based on your settingsliveSass.command.debugFileListfor a more in-depth look under the hood of the files included and excluded. Which can assist when logging issues
- New item in the FAQ for extra help with glob patterns and reporting files not being compiled
- Two settings:
Changed
- Update the returned message from Autoprefixer warnings. They now better reflect that it’s a warning not an error and include file information
- Updated some dependencies:
- autoprefixer: v10.1.0
- glob: 7.1.6
- postcss: 8.2.1
- Also updated some dev dependencies (not effecting the extension itself)
Other
- Moved to eslinting, prettified the Typescript files
4.1.0 - 2020-12-20
Added
- New setting
liveSassCompile.settings.compileOnWatch- When
trueit will automatically compile all Sass files when watching is started. Default value istrue
- When
Changed
- Updated the issue report command text from
Create an 'Unexpected Error' issuetoReport an issueto simplify and be more inline with the normality. - Now using webpack to minify and speed up the extension
Other
- Doc changes/general tidy up, updated
.vscodeignore, update license, update.gitignore
4.0.0 - 2020-12-20
Breaking changes
- Output options are now only
expandedandcompressed - Only works on VS Code v1.50 and over
Fixed
- Changed from
libsasstosass(more up to date release)- Fixes: many issues + performance improvement
- Map line numbers are correct after
autoprefixeris applied
Added
- Replace segments in the save path: added two new settings under
liveSassCompile.settings.formatssavePathSegmentKeys- A list of segments to be replacedsavePathReplaceSegmentsWith- The replacement value
- New setting
liveSassCompile.settings.watchOnLaunch- When
trueit will automatically start watching your.sassor.scssfiles on launch. Default value isfalse
- When
- New logging mechanism
- Errors are logged in a workspace folder
- New command to help log issues for unhandled errors
liveSass.command.createIssue
| Version | Date | Changelog |
|---|---|---|
| 3.0.0 | 11.07.2018 | – Fixes: [#39, #40, #78] Upgrade sass.js library that included fixes for 8 digit Hex code & grid name. |
| 2.2.1 | 29.06.2018 | – [Fixes #77] Rebuild the package |
| 2.2.0 | 29.06.2018 | – [Fixes #76] (That was library issue. Sass.js is downgraded to v0.10.8) |
| 2.1.0 | 28.06.2018 | – [Fixes #73] Change detection of Partial Sass was missing in v2.0.0 |
| 2.0.0 | 27.06.2018 | – Fixes #6 #62 – Include Path Fixes – Grid Autoprefix – Autoprefix is now on by default |
| 1.3.0 | 19.02.2018 | – [NEW #41] - added ability to suppress the output window - Status bar button colour change based on Success and error.[Thanks a lot to Brandon Baker for submitting the PR ] |
| 1.2.0 | 21.12.17 | – [New Features #26] savePath setting updated. You can now specify savePath location relative to your Sass files. See Settings section for more details [Thanks Marius] – [Bug Fixed #25] No more extra new line in generated CSS. [Thanks Shahril Amri] –[Bug Fixed #33] Now Firefox is recognizing source SCSS file. [Thanks Felix] |
| 1.1.0 | 01.11.17 | – [NEW #19] Support for autoprefix in generated CSS. (see settings section for more) [Thanks a lot to boyum for submitting the PR #22] – [Bug fixed #20] : Fixed liveSassCompile.settings.includeItems settings. [Thanks Hoàng Nam] |
| 1.0.1 | 10.10.17 | – [Fixes #17] Default value savePath from new settings (.formats) is revised. If you don’t set any value it will generate CSS at the same location of sass/scss as it was before. (See settings section for more details) [Thanks 2289034325 & Ibsenleo for the feedback] |
| 1.0.0 | 10.10.17 | – [New Features/settings #10] Support for multiple extensionName, formats & save locations . [Thanks to Trinh Xuan Manh for the suggestion and a Special Thanks to Ibsenleo for the PR #16.] –NOTE : Due to enable this feature, the liveSassCompile.settings.format, .savePath, .extensionName settings are dropped. [See settings section for the new setting.] |
| 0.5.1 | 23.09.17 | – [Bug Fixed #12] Sass files from excluded list was compiled on individual savings. [Thanks Braedin Jared] |
| 0.5.0 | 25.08.17 | – [New Settings] liveSassCompile.settings.generateMap : Set it as false if you don’t want .map file for compiled CSS. Default is true. [#9 Thanks Mark Hewitt for the PR]. |
| 0.4.0 | 21.08.17 | – [Renamed] liveSassCompile.settings.excludeFolders is renamed to liveSassCompile.settings.excludeList. – [Fixed] You can set glob pattern to exclude files through liveSassCompile.settings.excludeList settings. You can also use negative glob pattern.[For More details, follow settings section] – [New Settings #8 ] liveSassCompile.settings.includeItems : This setting is useful when you deals with only few of sass files. Only mentioned Sass files will be included. NOTE: No need to include partial sass files. [Thanks PatrickPahlke]. |
| 0.3.4 | 15.08.17 | [Fixed #7] Duplicate Output. [Thanks Tomekk-hnm]. |
| 0.3.3 | 01.08.17 | [#5] Critical Fix Update for Linux & macOS. (Thanks a lot to Shea Fitzek). |
| 0.3.2 | 01.08.17 | [Hot Fix] CSS & map link was broken. |
| 0.3.1 | 30.07.17 | – Ordering of Output log is fixed. NOTE : Lot of code (almost full code) is changed as I’ve refactored the source code. So, if anything is broken (Hopefully NOT :D ), feel free to open a issue request on GitHub. I’m happy to resolve the bugs. |
| 0.3.0 | 29.07.17 | – This update does not include any new feature or major fix but a big fix in source code setup. I was facing a big configuration issue between TypeScript and non-NPM third-party library since I released the extension - even I was not able to debug extension directly from TypeScript codes. Finally I am able to fix it. (I promise, more updates are coming soon…). – Status bar text (at watching mode) has been changed. –Package size reduced to more than 50%. |
| 0.2.2 | 25.07.17 | New Command added for one time Sass/Scss compilation. - Press F1 or ctrl+shift+p and enter Compile Sass - Without Watch Mode. |
| 0.2.1 | 21.07.17 | [#4] Critical Bug Fixed update. [Thanks Cassio Cabral]. |
| 0.2.0 | 20.07.17 | [#3] New settings added to exclude specific folders from workspace. All Sass/Scss files inside the folders will be ignored. [Thanks Cassio Cabral for the suggestion]. |
| 0.1.2 | 19.07.17 | Small Fix (Rename) update. |
| 0.1.1 | 14.07.17 | Fixed #2 - Partial Sass/Sass files are not compiling in watching mode. (Thanks again, Kerry Smyth :p) |
| 0.1.0 | 13.07.17 | Feature Added #1 - Now the extension will also generate Linker Address Map (.map) files in the same directory of .css (Thanks, Kerry Smyth). |
| 0.0.5 | 11.07.17 | liveSassCompile.settings.extensionName settings added. |
| 0.0.4 | 11.07.17 | Icon updated. |
| 0.0.3 | 11.07.17 | Fix update for Linux environment. |
| 0.0.2 | 11.07.17 | Small description updated. |
| 0.0.1 | 11.07.17 | Initial Preview Release with following key features. – Live SASS & SCSS Compile. – Customizable file location of exported CSS. – Customizable exported CSS Style ( expanded, compact, compressed, nested.)– Quick Status bar control. – Live Reload to browser ( Live Server extension dependency). |