sass
1.108.2 · 11 Nov 2026MIT44.5M / weekRepositorynpmAtom feed
Upgrading sass From 1.17.4 to 1.18.0
1 release in betweenevery note read
Reading releases, release notes and advisories…
- 1
- change to make
- 0
- advisories fixed
- 2
- new
- 3
- fixes
Before you upgrade
Tick each one off as you go- Breaking1.18.0
Release by release
- Breaking
Explicitly require that importers'
canonicalize()methods be able to take paths relative to their outputs as valid inputs. This isn't considered a breaking change because the importer infrastructure already required this in practice. - New
Add a
--no-charsetflag. If this flag is set, Sass will never emit a@charsetdeclaration or a byte-order mark, even if the CSS file contains non-ASCII characters. - New
Add a
charsetoption tocompile(),compileString(),compileAsync()andcompileStringAsync(). If this option is set tofalse, Sass will never emit a@charsetdeclaration or a byte-order mark, even if the CSS file contains non-ASCII characters. - Fixed
Avoid recursively listing directories when finding the canonical name of a file on case-insensitive filesystems.
- Fixed
Fix importing files relative to
package:-imported files. - Fixed
Don't claim that "package:" URLs aren't supported when they actually are.
- Breaking
A whole project to check? Paste its package.json in the dependency check: every deprecated, outdated or vulnerable dependency, with what to upgrade to. Free, no account.