@sass/types
1.108.2 · 11 Nov 2026MIT9.5k / weekRepositoryHomepagenpmAtom feed
Upgrading @sass/types From 1.98.0 to 1.99.0
1 release in betweenevery note read
Reading releases, release notes and advisories…
- 3
- changes to make
- 0
- advisories fixed
- 1
- new
- 0
- fixes
Before you upgrade
Tick each one off as you go- Deprecated1.99.0
- Deprecated1.99.0
- Deprecated1.99.0
Release by release
- Deprecated
User-defined functions named
EXPRESSION,URL, andELEMENT, those that begin with-and end with-ELEMENT, as well as the same names with some lowercase letters are now deprecated, These are names conflict with plain CSS functions that have special syntax. - Deprecated
In a future release, calls to functions whose names begin with
-and end with-expressionand-urlwill no longer have special parsing. For now, these calls are deprecated if their behavior will change in the future. - Deprecated
Calls to functions whose names begin with
-and end with-progid:...are deprecated. - New
Add support for parent selectors (
&) at the root of the document. These are emitted as-is in the CSS output, where they're interpreted as [the scoping root].
- Deprecated
2 other lines we could not sort, mostly version bumps
- 1.99.0
User-defined functions named
calcorclampare no longer forbidden. If such a function exists without a namespace in the current module, it will be used instead of the built-incalc()orclamp()function. - 1.99.0
User-defined functions whose names begin with
-and end with-expression,-url,-and,-or, or-notare no longer forbidden. These were originally intended to match vendor prefixes, but in practice no vendor prefixes for these functions ever existed in real browsers.
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.