@ethlete/components 1.0.0-next.19 → 1.0.0-next.20
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/CHANGELOG.md +29 -0
- package/fesm2022/ethlete-components.mjs +118 -112
- package/fesm2022/ethlete-components.mjs.map +1 -1
- package/package.json +1 -1
- package/types/ethlete-components.d.ts +12 -12
package/CHANGELOG.md
CHANGED
|
@@ -1,5 +1,34 @@
|
|
|
1
1
|
# Changelog
|
|
2
2
|
|
|
3
|
+
## 1.0.0-next.20
|
|
4
|
+
|
|
5
|
+
### Major Changes
|
|
6
|
+
|
|
7
|
+
- [`44adcac`](https://github.com/ethlete-io/ethdk/commit/44adcac94d7e0f56742e02901221c6e04da7df47) Thanks [@TomTomB](https://github.com/TomTomB)! - Rename past-tense outputs to the present tense, matching native DOM event naming (enforced by the new `ethlete/prefer-present-tense-output` lint rule):
|
|
8
|
+
- `etMenuItem` (and `et-menu-item` / `et-menu-checkbox-item` / `et-menu-radio-item`): `activated` → `activate`
|
|
9
|
+
- `etDropzone` / `et-dropzone`: `filesRejected` → `filesReject`, `uploadSucceeded` → `uploadSucceed`, `uploadFailed` → `uploadFail`
|
|
10
|
+
- `et-grid-item`: `removed` → `remove`
|
|
11
|
+
|
|
12
|
+
Update the corresponding template bindings, e.g. `(activated)` → `(activate)`, `(uploadSucceeded)` → `(uploadSucceed)`, `(removed)` → `(remove)`.
|
|
13
|
+
|
|
14
|
+
### Minor Changes
|
|
15
|
+
|
|
16
|
+
- [#3018](https://github.com/ethlete-io/ethdk/pull/3018) [`e8f9bcd`](https://github.com/ethlete-io/ethdk/commit/e8f9bcd65b40724b266aff8949951649afafea36) Thanks [@github-actions](https://github.com/apps/github-actions)! - Move all component styles into the `components` CSS cascade layer (`@layer components`).
|
|
17
|
+
|
|
18
|
+
Component CSS was previously injected unlayered, which meant it beat Tailwind
|
|
19
|
+
utility classes (in `@layer utilities`) regardless of specificity — forcing
|
|
20
|
+
consumers to reach for `!important` (e.g. `flex!`) to override layout, spacing or
|
|
21
|
+
sizing on components. Because layer precedence is resolved before specificity,
|
|
22
|
+
`:where()` could not fix this.
|
|
23
|
+
|
|
24
|
+
Now that component rules live in `@layer components` (which Tailwind v4 orders
|
|
25
|
+
before `utilities`), a plain utility class overrides component styles without
|
|
26
|
+
`!important`. This is a behavior change: any consumer rule that is unlayered or
|
|
27
|
+
in a later layer now wins over component styles by default. Apps using the
|
|
28
|
+
default Tailwind v4 layer order (`theme, base, components, utilities`) get the
|
|
29
|
+
fix automatically; apps that customize layer order should ensure `components`
|
|
30
|
+
sorts before their utilities.
|
|
31
|
+
|
|
3
32
|
## 1.0.0-next.19
|
|
4
33
|
|
|
5
34
|
### Patch Changes
|