@sass/types
1.108.2 · 11 Nov 2026MIT9.5k / weekRepositoryHomepagenpmAtom feed
Upgrading @sass/types From 1.94.3 to 1.95.0
1 release in betweenevery note read
Reading releases, release notes and advisories…
- 1
- change to make
- 0
- advisories fixed
- 1
- new
- 0
- fixes
Before you upgrade
Tick each one off as you go- Deprecated1.95.0
Release by release
- Deprecated
The old Sass
if()syntax is now deprecated. Users are encouraged to migrate to the new CSS syntax.if($condition, $if-true, $if-false)can be changed toif(sass($condition): $if-true; else: $if-false). - New
Add support for the [CSS-style
if()function]. In addition to supporting the plain CSS syntax, this also supports asass()query that takes a Sass expression that evaluates totrueorfalseat preprocessing time depending on whether the Sass value is truthy. If there are no plain-CSS queries, the function will return the first value whose query returns true during preprocessing. For example,if(sass(false): 1; sass(true): 2; else: 3)returns2.
- Deprecated
2 other lines we could not sort, mostly version bumps
- 1.95.0
Plain-CSS
if()functions are now considered "special numbers", meaning that they can be used in place of arguments to CSS color functions. - 1.95.0
Plain-CSS
if()functions andattr()functions are now considered "special variable strings" (likevar()), meaning they can now be used in place of multiple arguments or syntax fragments in various CSS functions.
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.