Releases: atlassian-labs/compiled
@compiled/jest@0.10.5
Patch Changes
- a205c08: Fix jest matcher unintentionally kebab-casing css custom properties.
@compiled/babel-plugin@0.29.1
Patch Changes
- 5c04f89: Fix 'as const' expressions causing Compiled to crash at build time
@compiled/webpack-loader@0.13.0
Minor Changes
-
83c47f8: [BREAKING] Add a deterministic sorting to media queries and other at-rules in Compiled. We use a simplified version of what the
sort-css-media-queries
package does - sortingmin-width
andmin-height
from smallest to largest, thenmax-width
andmax-height
from largest to smallest. If ranges or features involvingheight
andwidth
are not present in the at-rule, the at-rule will be sorted lexicographically / alphabetically.Situations you may need to be careful of:
- In situations where two at-rules with the same property apply at the same time, this may break your styles, as the order in which the styles are applied will change. (For example, overlapping
@media
queries) - Because all at-rules will now be sorted lexicographically / alphabetically,
@layer
blocks you pass to Compiled APIs may not be outputted in the same order, causing different CSS than expected.
This is turned on by default. If you do not want your at-rules to be sorted, set
sortAtRules
tofalse
in your configuration:- Webpack users: the
@compiled/webpack-loader
options in your Webpack configuration - Parcel users: your Compiled configuration, e.g.
.compiledcssrc
or similar - Babel users: the
@compiled/babel-plugin-strip-runtime
options in your.babelrc.json
or similar, if you have the@compiled/babel-plugin-strip-runtime
plugin enabled.
- In situations where two at-rules with the same property apply at the same time, this may break your styles, as the order in which the styles are applied will change. (For example, overlapping
Patch Changes
- 4f5865a: Fixes the parsing of custom properties (CSS variables) names in object syntax. The casing is now preserved instead of being converted to kebab-case.
- Updated dependencies [4f5865a]
- Updated dependencies [4f5865a]
- Updated dependencies [83c47f8]
- @compiled/babel-plugin@0.29.0
- @compiled/babel-plugin-strip-runtime@0.29.0
- @compiled/utils@0.11.1
- @compiled/css@0.14.0
@compiled/utils@0.11.1
Patch Changes
- 4f5865a: Fixes the parsing of custom properties (CSS variables) names in object syntax. The casing is now preserved instead of being converted to kebab-case.
@compiled/parcel-transformer@0.15.4
Patch Changes
- 4f5865a: Fixes the parsing of custom properties (CSS variables) names in object syntax. The casing is now preserved instead of being converted to kebab-case.
- Updated dependencies [4f5865a]
- Updated dependencies [4f5865a]
- Updated dependencies [83c47f8]
- @compiled/babel-plugin@0.29.0
- @compiled/babel-plugin-strip-runtime@0.29.0
- @compiled/utils@0.11.1
@compiled/parcel-optimizer@0.4.5
@compiled/parcel-config@0.5.0
Minor Changes
-
83c47f8: [BREAKING] Add a deterministic sorting to media queries and other at-rules in Compiled. We use a simplified version of what the
sort-css-media-queries
package does - sortingmin-width
andmin-height
from smallest to largest, thenmax-width
andmax-height
from largest to smallest. If ranges or features involvingheight
andwidth
are not present in the at-rule, the at-rule will be sorted lexicographically / alphabetically.Situations you may need to be careful of:
- In situations where two at-rules with the same property apply at the same time, this may break your styles, as the order in which the styles are applied will change. (For example, overlapping
@media
queries) - Because all at-rules will now be sorted lexicographically / alphabetically,
@layer
blocks you pass to Compiled APIs may not be outputted in the same order, causing different CSS than expected.
This is turned on by default. If you do not want your at-rules to be sorted, set
sortAtRules
tofalse
in your configuration:- Webpack users: the
@compiled/webpack-loader
options in your Webpack configuration - Parcel users: your Compiled configuration, e.g.
.compiledcssrc
or similar - Babel users: the
@compiled/babel-plugin-strip-runtime
options in your.babelrc.json
or similar, if you have the@compiled/babel-plugin-strip-runtime
plugin enabled.
- In situations where two at-rules with the same property apply at the same time, this may break your styles, as the order in which the styles are applied will change. (For example, overlapping
Patch Changes
- Updated dependencies [4f5865a]
- @compiled/parcel-transformer@0.15.4
- @compiled/parcel-optimizer@0.4.5
@compiled/jest@0.10.4
Patch Changes
- 4f5865a: Fixes the parsing of custom properties (CSS variables) names in object syntax. The casing is now preserved instead of being converted to kebab-case.
@compiled/eslint-plugin@0.13.9
@compiled/css@0.14.0
Minor Changes
-
83c47f8: [BREAKING] Add a deterministic sorting to media queries and other at-rules in Compiled. We use a simplified version of what the
sort-css-media-queries
package does - sortingmin-width
andmin-height
from smallest to largest, thenmax-width
andmax-height
from largest to smallest. If ranges or features involvingheight
andwidth
are not present in the at-rule, the at-rule will be sorted lexicographically / alphabetically.Situations you may need to be careful of:
- In situations where two at-rules with the same property apply at the same time, this may break your styles, as the order in which the styles are applied will change. (For example, overlapping
@media
queries) - Because all at-rules will now be sorted lexicographically / alphabetically,
@layer
blocks you pass to Compiled APIs may not be outputted in the same order, causing different CSS than expected.
This is turned on by default. If you do not want your at-rules to be sorted, set
sortAtRules
tofalse
in your configuration:- Webpack users: the
@compiled/webpack-loader
options in your Webpack configuration - Parcel users: your Compiled configuration, e.g.
.compiledcssrc
or similar - Babel users: the
@compiled/babel-plugin-strip-runtime
options in your.babelrc.json
or similar, if you have the@compiled/babel-plugin-strip-runtime
plugin enabled.
- In situations where two at-rules with the same property apply at the same time, this may break your styles, as the order in which the styles are applied will change. (For example, overlapping