guard-my-design-system 1.3.4 → 1.3.5

package/README.md

@@ -36,7 +36,9 @@ it updates that same comment. It never adds more comments:
 ## What it catches
 
 - **A hard-coded colour where a token exists.** The finding names the token:
-  `var(--blue-500)`, not just a hex code.
+  `var(--blue-500)`, not just a hex code. This works across colour notations:
+  a hex stray is matched to an hsl or oklch token, including shadcn's
+  bare-triplet variables.
 - **A spacing value your codebase has never used**, with the nearest existing
   step named.
 - **A border radius, font size or shadow your system does not declare**, with

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "guard-my-design-system",
-  "version": "1.3.4",
+  "version": "1.3.5",
   "description": "Your design system dies one pull request at a time. This makes sure it doesn't. A guard that judges only the lines a change adds, against the system the repo already has, and names the on-system value the author probably meant.",
   "type": "module",
   "bin": {
@@ -11,7 +11,7 @@
     "src/"
   ],
   "dependencies": {
-    "roast-my-design-system": "5.7.2"
+    "roast-my-design-system": "5.10.2"
   },
   "keywords": [
     "design-system",

package/src/judge.mjs

@@ -90,7 +90,10 @@ export function judge(added, system) {
   // "use var(--blue-500)", not "go hunt this hex": name a value when the
   // system defines it as a custom property.
   const named = (value) => {
-    const n = system.tokenNames?.[value];
+    // shadcn-style tokens are defined as bare triplets (--primary: 222.2 47.4%
+    // 11.2%) but normalised to hsl(...); try the unwrapped form too.
+    const n = system.tokenNames?.[value]
+      ?? system.tokenNames?.[value.replace(/^hsla?\((.*)\)$/i, '$1')];
     return n ? `var(${n}), ${value}` : value;
   };
   const faceCounts = new Map();