|
61 | 61 | }
|
62 | 62 | ```
|
63 | 63 |
|
| 64 | +* Add support for the new `@container` CSS rule ([#2127](https://github.com/evanw/esbuild/pull/2127)) |
| 65 | + |
| 66 | + This release adds support for [`@container`](https://drafts.csswg.org/css-contain-3/#container-rule) in CSS files. This means esbuild will now pretty-print and minify these rules better since it now better understands the internal structure of these rules: |
| 67 | + |
| 68 | + ```css |
| 69 | + /* Original code */ |
| 70 | + @container (width <= 150px) { |
| 71 | + #inner { |
| 72 | + color: yellow; |
| 73 | + } |
| 74 | + } |
| 75 | + |
| 76 | + /* Old output (with --minify) */ |
| 77 | + @container (width <= 150px){#inner {color: yellow;}} |
| 78 | + |
| 79 | + /* New output (with --minify) */ |
| 80 | + @container (width <= 150px){#inner{color:#ff0}} |
| 81 | + ``` |
| 82 | + |
| 83 | + This was contributed by [@yisibl](https://github.com/yisibl). |
| 84 | + |
64 | 85 | ## 0.14.30
|
65 | 86 |
|
66 | 87 | * Change the context of TypeScript parameter decorators ([#2147](https://github.com/evanw/esbuild/issues/2147))
|
|
508 | 529 |
|
509 | 530 | * Remove simplified statement-level literal expressions ([#2063](https://github.com/evanw/esbuild/issues/2063))
|
510 | 531 |
|
511 |
| - With this release, esbuild now removes simplified statement-level expressions if the simplified result is a literal expression even when minification is disabled. Previously this was only done when minification is enabled. This change was only made because some people are bothered by seeing top-level literal expressions. This change has no effect on code behavior. |
| 532 | + With this release, esbuild now removes simplified statement-level expressions if the simplified result is a literal expression even when minification is disabled. Previously this was only done when minification is enabled. This change was only made because some people are bothered by seeing top-level literal expressions. This change has no effect on code behavior. |
512 | 533 |
|
513 | 534 | * Ignore `.d.ts` rules in `paths` in `tsconfig.json` files ([#2074](https://github.com/evanw/esbuild/issues/2074), [#2075](https://github.com/evanw/esbuild/pull/2075))
|
514 | 535 |
|
@@ -5452,7 +5473,7 @@ In addition to the breaking changes above, the following features are also inclu
|
5452 | 5473 |
|
5453 | 5474 | * Fix some obscure TypeScript type parsing edge cases
|
5454 | 5475 |
|
5455 |
| - In TypeScript, type parameters come after a type and are placed in angle brackets like `Foo<T>`. However, certain built-in types do not accept type parameters including primitive types such as `number`. This means `if (x as number < 1) {}` is not a syntax error while `if (x as Foo < 1) {}` is a syntax error. This release changes TypeScript type parsing to allow type parameters in a more restricted set of situations, which should hopefully better resolve these type parsing ambiguities. |
| 5476 | + In TypeScript, type parameters come after a type and are placed in angle brackets like `Foo<T>`. However, certain built-in types do not accept type parameters including primitive types such as `number`. This means `if (x as number < 1) {}` is not a syntax error while `if (x as Foo < 1) {}` is a syntax error. This release changes TypeScript type parsing to allow type parameters in a more restricted set of situations, which should hopefully better resolve these type parsing ambiguities. |
5456 | 5477 |
|
5457 | 5478 | ## 0.10.2
|
5458 | 5479 |
|
|
0 commit comments