Releases: glenn2223/vscode-live-sass-compiler
Releases · glenn2223/vscode-live-sass-compiler
v5.0.0-rc.2
v5.0.0-rc.1
5.0.0-rc.1 - 2021-04-01
Breaking changes
- Not dependant on
ritwickdey.LiveServer
as 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
showOutputWindow
setting, 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
orError
- The default is now
Warning
- Changes to
autoprefix
settings (#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 expansion
glob patterns (#27)- This is because the underlying glob pattern matching has moved from
minimatch
topicomatch
. 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[].savePath
must start with a path separator but not end in oneincludeItems
must start with a path separator and end in either.sass
or.scss
(for performance purposes)forceBaseDirectory
must start with a path separator but not end in one
Changed
- Now using
fdir
withpicomatch
instead ofglob
andminimatch
- Speed improvements, the most significant of which will be on larger projects
- Greater support for glob patterns
Added
-
When
autoprefix
is true we will search for either:- a
.browserlistsrc
file or, "browserslist": [ string[] ]
in apackage.json
file
(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[].savePathSegmentKeys
setting would allow non string values in the array - Fixed: the
excludeList
setting would allow non string values in the array - Fixed: the
includeItems
setting would allow non string values in the array - Fixed: the
autoprefix
setting would allow non string values in the array - Fixed: some setting descriptions have been updated for better clarity/readability
Updated
autoprefixer
from10.2.4
to10.2.5
- Fixed
:
support in@supports
- Fixed
postcss
from8.2.4
to8.2.9
- Small fixes (nothing user facing)
sass
from1.32.5
to1.32.8
- Allow
@forward...with
to take arguments that have a!default
flag 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)
Note: to release this on the marketplace I had to repackage with v5.0.0 - all documentation now and for each rc will continue as rc release. I'm hoping that by removing the preview
from the package.json it will overwrite the previous version 🤞
v4.4.1
4.4.1 - 2021-01-31
Fixed
- Fixed:
forceBaseDirectory
has full support in multi-root workspaces - Fixed: the path in
forceBaseDirectory
is 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 patern matches in settings show user friendly messages rather than "does not match pattern"
v4.4.0
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) )
- New feature: The status bar
Error
andSuccess
messages can be clicked which will open the Output Window #25
Updates
autoprefixer
from10.2.1
to10.2.4
- Small bug fixes (nothing user facing)
- Various dev-dependancy 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:
compileCurrentSass
shows wrong message on fail- When you run
compileCurrentSass
and it would fail (for whatever reason) it would cause the output to showSuccess
rather thanError
(just the output was wrong, nothing else)
- When you run
- Fix: Status bar inconsistancies 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)
v4.3.4
4.3.4 - 2021-01-21
Fixed
- Fixed #18: On launch there is no output, nor any
Live SASS Compile
ouput selection, when the settingwatchOnLaunch
istrue
- Fixed: Autoprefixer warning saying
undefined
for file path whengenerateMap
isfalse
- 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
sass
from1.32.4
to1.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 behavior of Ruby Sass and LibSass.
- Others: see sass release notes
v4.3.3
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
v4.3.2
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
sass
from1.30.0
to1.32.4
- Various changes, see their changelog
autoprefixer
from10.1.0
to10.2.1
- Fixed transition-property warnings (by @Sheraff).
- Other, non-facing changes
eslint
from7.16.0
to7.17.0
ts-loader
from8.0.12
to8.0.14
postcss
from8.2.1
to8.2.4
vscode-test
from1.4.0
to1.4.1
webpack
from5.11.0
to5.14.0
webpack-cli
from4.2.0
to4.3.0
v4.3.1
v4.3.0
v4.2.0
4.2.0 - 2020-12-22
Added
- New debugging items
- Two settings:
liveSass.command.debugInclusion
to check that a current file will be included based on your settingsliveSass.command.debugFileList
for 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
Changelog
See the full changelog here.