v5.2.0-rc.1
Pre-release
Pre-release
5.2.0-rc.1 - 2022-01-25
Added
@warn
and@debug
lines, 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.partialsList
setting - Closes #143
Changes
- Updated docs to reflect new setting and also included previous changes in the FAQ
- Further logging in a function at
Trace
level
Fixed
- Stopped returning false negatives when checking if a file should trigger compilation thanks to a bump to
fdir
- Closes #145- Awaiting confirmation of fix
- 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.
.Sass
will now match) - Fixes #137 - Valid save paths in the
liveSassCompile.settings.formats
setting no longer throws a warning - Fixes #139 - No longer outputs error if the css generated is an empty string - Fixes #140
Updated
autoprefixer
from10.3.7
to10.4.2
- Added
:autofill
support - Fixed
::file-selector-button
data - Fixed missed
-webkit-
prefix forwidth: stretch
- Added
fdir
from5.1.0
to5.2.0
- Fixed a critical issue with async crawling that caused the crawler to return early
- Other changes (nothing user facing)
picomatch
from2.3.0
to2.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 (
postcss
from8.3.9
to8.4.5
- Various changes (nothing user facing)
sass
from1.37.5
to1.49.0
- Potentially breaking bug fix: Change the default value of the
separator
parameter fornew SassArgumentList()
to','
rather thannull
. This matches the API specification. - Potentially breaking bug fix: Properly parse custom properties in
@supports
conditions. Note that this means that SassScript expressions on the right-hand side of custom property@supports
queries 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
if
to be used as an unquoted string. - Properly parse backslash escapes within
url()
expressions. - Fix a couple bugs where
@extend
s could be marked as unsatisfied when multiple identical@extend
s extended selectors across@use
rules. - Add a
charset
option 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
logger
option. This takes an object that can definewarn
ordebug
methods 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
@use
rule 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)