@cocso-ui/react 1.0.1 → 1.1.0

package/dist/esm/token/color.mjs

@@ -1,4 +1,21 @@
-/** Cocso design system color token map keyed by semantic name. */
+/**
+ * Cocso design system colors, as CSS `var()` references.
+ *
+ * Two kinds live here, and they behave differently when the theme changes:
+ *
+ * - **Semantic tokens** — `textPrimary`, `surfaceSecondary`, `interactivePrimary`,
+ *   `feedbackDangerText`, and so on. `theme-dark.css` redefines these, so they
+ *   follow the active theme.
+ * - **Ramp values** — `primary600`, `neutral400`, `danger600`, and the rest of
+ *   the numbered scale. `theme-dark.css` deliberately leaves the raw scale
+ *   alone, so these render identically in both themes.
+ *
+ * Both are reached as `colors.X`, so nothing at the call site says which kind
+ * you picked. Use a semantic token for anything that has to stay legible when
+ * the theme changes: a ramp value used as a text color keeps its lightness
+ * while the surface behind it flips, and sinks into the background of the theme
+ * it was not chosen for.
+ */
 const colors = {
   transparent: "var(--cocso-color-transparent)",
   white: "var(--cocso-color-white)",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@cocso-ui/react",
-  "version": "1.0.1",
+  "version": "1.1.0",
   "repository": {
     "type": "git",
     "url": "git+https://github.com/cocso/cocso-ui.git",
@@ -34,7 +34,7 @@
     "sonner": "^2.0.7",
     "tailwind-merge": "^3.5.0",
     "ts-pattern": "^5.9.0",
-    "@cocso-ui/react-icons": "^1.0.0"
+    "@cocso-ui/react-icons": "^1.0.1"
   },
   "devDependencies": {
     "@babel/preset-react": "^7.28.5",
@@ -61,7 +61,7 @@
   },
   "peerDependencies": {
     "react": "^19.1.1",
-    "@cocso-ui/css": "^1.0.1"
+    "@cocso-ui/css": "^1.2.0"
   },
   "publishConfig": {
     "access": "public"