@sass/types
1.108.2 · 11 Nov 2026MIT9.5k / weekRepositoryHomepagenpmAtom feed
Upgrading @sass/types From 1.105.2 to 1.106.0
1 release in betweenevery note read
Reading releases, release notes and advisories…
- 0
- changes to make
- 0
- advisories fixed
- 0
- new
- 7
- fixes
Release by release
- Fixed
Don't normalize CSS escapes in statement contexts that can contain interpolation. For example,
@f\6Fois now emitted as written rather than normalized to@foo. - Fixed
Fix a bug where quotes would be removed from attribute selector values that contained backslashes.
- Fixed
Fix invalid source spans that could cause crashes when encountering a syntax error in selectors or media queries that also contain escape sequences.
- Fixed
Fix a bug where the indented syntax parser would crash when parsing a file where the first statement was indented and appeared after the first line.
- Fixed
Fix a bug that could cause crashes when encountering errors or warnings in interpolations that contain patterns like
// */. - Fixed
Potentially breaking bug fix: Fix various cases where using a CSS escape code at the beginning of an identifier would change parsing behavior versus using the character directly.
- Fixed
Potentially breaking bug fix: Don't parse a CSS escape code for U+45 LATIN CAPITAL LETTER E or U+65 LATIN LOWERCASE LETTER E as an exponent in
@keyframespercentage selectors.
- Fixed
4 other lines we could not sort, mostly version bumps
- 1.106.0
Potentially breaking compatibility fix: CSS escape codes whose values are 0, for Unicode surrogates, or greater than the maximum allowed code point are now consistently normalized to U+FFFD REPLACEMENT CHARACTER in expression contexts. Previously, in some cases these were instead normalized to the normalized form of the original escape sequence, which violates the principle that all escape sequences for identical values should be normalized the same way. In other cases, these would simply throw errors.
- 1.106.0
Potentially breaking bug fix: Throw an error for mixins and functions that have rest parameters which are the same as normal parameters. Previously, the positional parameters wouldn't be accessible and calling such a mixin or function with a named argument would crash the compiler.
- 1.106.0
Potentially breaking bug fix: When a number's unit is ambiguous with a numeric exponent, the unit is now serialized as an escape code rather than a literal
eto avoid being interpreted as an exponent by CSS. - 1.106.0
Potentially breaking bug fix: Properly normalize underscores written as CSS escape codes in variable, mixin, and function names.
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.