@ai-matrx/design-system 0.5.2 → 0.6.0
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 +39 -1
- package/dist/index.cjs +26 -2
- package/dist/index.cjs.map +1 -1
- package/dist/index.d.cts +2 -2
- package/dist/index.d.ts +2 -2
- package/dist/index.js +26 -2
- package/dist/index.js.map +1 -1
- package/dist/styles.css +11 -0
- package/package.json +1 -1
package/dist/styles.css
CHANGED
|
@@ -23,6 +23,17 @@
|
|
|
23
23
|
@layer matrx-design-system-tokens, matrx-design-system;
|
|
24
24
|
@import "tailwindcss";
|
|
25
25
|
|
|
26
|
+
THAT STATEMENT IS NOT WHAT PROTECTS A HOST'S BRAND — say so plainly, because
|
|
27
|
+
the wrong belief is load-bearing. Verified on built output in every consumer
|
|
28
|
+
on 2026-09-07: the declaration does NOT survive Tailwind v4's build (the only
|
|
29
|
+
layer statement emitted into matrx-extend's stylesheet is `@layer
|
|
30
|
+
components;`). What actually guarantees a host wins is that HOST TOKENS ARE
|
|
31
|
+
DECLARED UNLAYERED, and unlayered beats layered regardless of specificity —
|
|
32
|
+
proven by byte offset (workflow-studio: this package's `--success` at 2249,
|
|
33
|
+
inside the layer; the host's `--success` at 143177, unlayered). The
|
|
34
|
+
declaration is still worth writing: it fixes the order BETWEEN this
|
|
35
|
+
package's two layers. It is simply not the mechanism a host is relying on.
|
|
36
|
+
|
|
26
37
|
Rules that must beat utilities (the scroll-fade mask, the mobile-sheet
|
|
27
38
|
density restatement) are UNLAYERED on purpose, matching how they were
|
|
28
39
|
authored in matrx-frontend's globals.css. Unlayered CSS beats every layered
|
package/package.json
CHANGED