Tags: spiderneo/vscode-live-sass-compiler
Tags
v4.4.1 PR glenn2223#29 from glenn2223 ## 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 - PR glenn2223#28 from glenn2223 ## 4.4.0 - 2021-01-31 ### Added - New setting: `liveSassCompile.settings.forceBaseDirectory` glenn2223#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](https://github.com/glenn2223/vscode-live-sass-compiler/blob/1d043a0541008dfa2b53c492f6a76dce4e3d9909/docs/settings.md) & [VS Code Feature Request](microsoft/vscode#115482) (:+1: it) ) - New feature: The status bar `Error` and `Success` messages can be clicked which will open the Output Window glenn2223#25 ### Updates - `autoprefixer` from `10.2.1` to `10.2.4` - Small bug fixes (nothing user facing) - Various dev-dependancy updates ### Fixed - Part fix: Slow file handling glenn2223#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 show `Success` rather than `Error` (just the output was wrong, nothing else) - 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 - PR glenn2223#20 from glenn2223 ## 4.3.4 - 2021-01-21 ### Fixed - Fixed [glenn2223#18](glenn2223#18): On launch there is no output, nor any `Live SASS Compile` ouput selection, when the setting `watchOnLaunch` is `true` - Fixed: Autoprefixer warning saying `undefined` for file path when `generateMap` is `false` - Fixed: Autoprefixer `grid: "autoplace"` was forced - If [this feature](https://github.com/postcss/autoprefixer#does-autoprefixer-polyfill-grid-layout-for-ie) is wanted then add `/* autoprefixer grid: autoplace */` to the start of your file ### Updates - `sass` from `1.32.4` to `1.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](https://github.com/sass/dart-sass/releases/tag/1.32.5)
v4.3.3 - PR glenn2223#16 from glenn2223 ## 4.3.3 - 2021-01-18 ### Fixed - Fixed [glenn2223#15](glenn2223#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
Merge pull request glenn2223#7 from glenn2223/ahead v4.2.0 prep and sass change prep
PreviousNext