|
| 1 | +## 1.97.1 |
| 2 | + |
| 3 | +* Fix a bug with the new CSS-style `if()` syntax where values would be evaluated |
| 4 | + even if their conditions didn't match. |
| 5 | + |
| 6 | +## 1.97.0 |
| 7 | + |
| 8 | +* Add support for the `display-p3-linear` color space. |
| 9 | + |
| 10 | +## 1.96.0 |
| 11 | + |
| 12 | +* Allow numbers with complex units (more than one numerator unit or more than |
| 13 | + zero denominator units) to be emitted to CSS. These are now emitted as |
| 14 | + `calc()` expressions, which now support complex units in plain CSS. |
| 15 | + |
| 16 | +## 1.95.1 |
| 17 | + |
| 18 | +* No user-visible changes. |
| 19 | + |
| 20 | +## 1.95.0 |
| 21 | + |
| 22 | +* Add support for the [CSS-style `if()` function]. In addition to supporting the |
| 23 | + plain CSS syntax, this also supports a `sass()` query that takes a Sass |
| 24 | + expression that evaluates to `true` or `false` at preprocessing time depending |
| 25 | + on whether the Sass value is truthy. If there are no plain-CSS queries, the |
| 26 | + function will return the first value whose query returns true during |
| 27 | + preprocessing. For example, `if(sass(false): 1; sass(true): 2; else: 3)` |
| 28 | + returns `2`. |
| 29 | + |
| 30 | + [CSS-style `if()` function]: https://developer.mozilla.org/en-US/docs/Web/CSS/Reference/Values/if |
| 31 | + |
| 32 | +* The old Sass `if()` syntax is now deprecated. Users are encouraged to migrate |
| 33 | + to the new CSS syntax. `if($condition, $if-true, $if-false)` can be changed to |
| 34 | + `if(sass($condition): $if-true; else: $if-false)`. |
| 35 | + |
| 36 | + See [the Sass website](https://sass-lang.com/d/if-function) for details. |
| 37 | + |
| 38 | +* Plain-CSS `if()` functions are now considered "special numbers", meaning that |
| 39 | + they can be used in place of arguments to CSS color functions. |
| 40 | + |
| 41 | +* Plain-CSS `if()` functions and `attr()` functions are now considered "special |
| 42 | + variable strings" (like `var()`), meaning they can now be used in place of |
| 43 | + multiple arguments or syntax fragments in various CSS functions. |
| 44 | + |
| 45 | +## 1.94.3 |
| 46 | + |
| 47 | +* Fix the span reported for standalone `%` expressions followed by whitespace. |
| 48 | + |
| 49 | +## 1.94.2 |
| 50 | + |
| 51 | +### Command-Line Interface |
| 52 | + |
| 53 | +* Using `--fatal-deprecation <version>` no longer emits warnings about |
| 54 | + deprecations that are obsolete. |
| 55 | + |
| 56 | +### Dart API |
| 57 | + |
| 58 | +* `Deprecation.forVersion` now excludes obsolete deprecations from the set it |
| 59 | + returns. |
| 60 | + |
| 61 | +### JS API |
| 62 | + |
| 63 | +* Excludes obsolete deprecations from `fatalDeprecations` when a `Version` is |
| 64 | + passed. |
| 65 | + |
| 66 | +### Node.js Embedded Host |
| 67 | + |
| 68 | +* Fix a bug where a variable could be used before it was initialized during |
| 69 | + async compilation. |
| 70 | + |
| 71 | +## 1.94.1 |
| 72 | + |
| 73 | +* No user-visible changes. |
| 74 | + |
| 75 | +## 1.94.0 |
| 76 | + |
| 77 | +* **Potentially breaking compatibility fix:** `@function` rules whose names |
| 78 | + begin with `--` are now parsed as unknown at-rules to support the plain CSS |
| 79 | + `@function` rule. Within this rule, the `result` property is parsed as raw |
| 80 | + CSS just like custom properties. |
| 81 | + |
| 82 | +* **Potentially breaking compatibility fix:** `@mixin` rules whose names begin |
| 83 | + with `--` are now errors. These are not yet parsed as unknown at-rules because |
| 84 | + no browser currently supports CSS mixins. |
| 85 | + |
| 86 | +## 1.93.3 |
| 87 | + |
| 88 | +* Fix a performance regression that was introduced in 1.92.0. |
| 89 | + |
| 90 | +## 1.93.2 |
| 91 | + |
| 92 | +* No user-visible changes. |
| 93 | + |
| 94 | +### JavaScript API |
| 95 | + |
| 96 | +* Fix another error in the release process for `@sass/types`. |
| 97 | + |
| 98 | +## 1.93.1 |
| 99 | + |
| 100 | +* No user-visible changes. |
| 101 | + |
| 102 | +### JavaScript API |
| 103 | + |
| 104 | +* Fix an error in the release process for `@sass/types`. |
| 105 | + |
| 106 | +## 1.93.0 |
| 107 | + |
| 108 | +* Fix a crash when a style rule contains a nested `@import`, and the loaded file |
| 109 | + `@use`s a user-defined module as well as `@include`s a top-level mixin which |
| 110 | + emits top-level declarations. |
| 111 | + |
| 112 | +### JavaScript API |
| 113 | + |
| 114 | +* Release a `@sass/types` package which contains the type annotations used by |
| 115 | + both the `sass` and `sass-embedded` package without any additional code or |
| 116 | + dependencies. |
| 117 | + |
| 118 | +## 1.92.1 |
| 119 | + |
| 120 | +* Fix a bug where variable definitions from one imported, forwarded module |
| 121 | + would not be passed as implicit configuration to a later imported, forwarded |
| 122 | + module. |
| 123 | + |
| 124 | +## 1.92.0 |
| 125 | + |
| 126 | +* **Breaking change:** Emit declarations, childless at-rules, and comments in |
| 127 | + the order they appear in the source even when they're interleaved with nested |
| 128 | + rules. This obsoletes the `mixed-decls` deprecation. |
| 129 | + |
| 130 | +* **Breaking change:** The function name `type()` is now fully reserved for the |
| 131 | + plain CSS function. This means that `@function` definitions with the name |
| 132 | + `type` will produce errors, while function calls will be parsed as special |
| 133 | + function strings. |
| 134 | + |
| 135 | +* Configuring private variables using `@use ... with`, `@forward ... with`, and |
| 136 | + `meta.load-css(..., $with: ...)` is now deprecated. Private variables were |
| 137 | + always intended to be fully encapsulated within the module that defines them, |
| 138 | + and this helps enforce that encapsulation. |
| 139 | + |
| 140 | +* Fix a bug where `@extend` rules loaded through a mixture of `@import` and |
| 141 | + `@use` rules could fail to apply correctly. |
| 142 | + |
| 143 | +### Command-Line Interface |
| 144 | + |
| 145 | +* In `--watch` mode, delete the source map when the associated source file is |
| 146 | + deleted. |
| 147 | + |
1 | 148 | ## 1.91.0 |
2 | 149 |
|
3 | 150 | * **Potentially breaking change:** `meta.inspect()` (as well as other systems |
|
0 commit comments