cornhsu-parity 2.3.0 → 2.4.0

package/README.md

@@ -63,11 +63,11 @@ PR comment, updating the same comment rather than adding new ones.
 
 | | |
 |---|---|
-| Releases | 31 on NuGet (v0.1.0 → v2.3.0). Pushing a tag publishes via OIDC Trusted Publishing — zero long-lived keys in the repo |
+| Releases | 33 on NuGet (v0.1.0 → v2.4.0). Pushing a tag publishes via OIDC Trusted Publishing — zero long-lived keys in the repo |
 | Compared properties | Size, padding, spacing, typography, color (CIEDE2000 ΔE), relative position — **absolute coordinates are deliberately excluded** (they are guaranteed false positives in a flexible layout) |
 | Design sources | 4: the Figma API, a rendering snapshot, an image + annotations (pixel sampling — any tool that exports a PNG works), or JSON |
 | Implementation sources | The web (including **shadow DOM, same-origin iframes, and multiple responsive breakpoints**) plus **Electron** (attached to the live window over CDP) |
-| Tests | **1443**, covering the CIEDE2000 reference data set (Sharma), match disambiguation, position false-positive guards, image sampling, and real-browser capture regressions |
+| Tests | **1503**, covering the CIEDE2000 reference data set (Sharma), match disambiguation, position false-positive guards, image sampling, and real-browser capture regressions |
 | Proven in CI | The GitHub Action is validated by **real PRs in an external repo**: blocking the PR, commenting automatically (updating in place), and baseline regression gating |
 | Proven in production | **All 26 pages of cornhsu.com are gated by Parity itself** — dogfooding has already found and fixed three flaky root causes (most recently a scroll-triggered entrance animation; see 0.11.1) |
 
@@ -301,6 +301,12 @@ Only the things that should hold no matter how the layout flows:
     axes are compared.
 - **Padding / spacing**: all four padding edges, and auto-layout `itemSpacing` against the real
   gap between child elements.
+  - A design's padding is often built with a child's `margin` instead (`padding: 0` on the
+    container, `margin: 12px 20px` on what is inside). The page looks the same, so from 2.4 that
+    edge counts as padding + margin of the child nearest it — but only when the sum matches the
+    design and the margin really sits inside the container (a margin that collapses out of a block
+    container leaves no space inside and still reports). When it doesn't match, the report shows
+    the CSS padding as before.
 - **Relative position** (`offsetX`/`offsetY`): for children of freely positioned (non-auto-layout)
   containers, the offset relative to the nearest reliable sibling or parent edge — which is what
   catches "size and color are perfect, but it is in the wrong place." Only reliable edges are used

package/bin/parity.js

@@ -51,10 +51,16 @@ try {
   const manifest = require.resolve(`${target.pkg}/package.json`);
   binary = path.join(path.dirname(manifest), "bin", target.bin);
 } catch {
+  // npm 對選用相依是解析不到、下載不到都不報錯,所以這裡是使用者第一次看到問題的地方。
+  // npx 的安裝放在 npm-cache/_npx/<hash>/,半成品會一直被重用:叫人 npm install 修不到它(2.3.1 實測)。
+  const npxCache = __dirname.match(/^(.*[\\/]_npx[\\/][^\\/]+)[\\/]/)?.[1];
   console.error(
     `cornhsu-parity: the platform package ${target.pkg} is not installed.\n` +
-      `It is an optional dependency, so the install may have skipped it (--no-optional / --omit=optional) or been interrupted.\n` +
-      `Reinstall: npm install cornhsu-parity`
+      `npm skips optional dependencies without an error, so this happens with --no-optional / --omit=optional, ` +
+      `after an interrupted install, or while a new release is still reaching the npm registry.\n` +
+      (npxCache
+        ? `npx cached this incomplete install, so running it again will not help. Delete this folder, then run npx again:\n  ${npxCache}`
+        : `Reinstall: npm install cornhsu-parity`)
   );
   process.exit(EXECUTION_ERROR);
 }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "cornhsu-parity",
-  "version": "2.3.0",
+  "version": "2.4.0",
   "description": "Property-Level Design QA that can gate your CI. Compares real numeric values from your Figma file against the rendered UI and fails the PR when the implementation drifts from the design.",
   "keywords": [
     "figma",
@@ -34,11 +34,11 @@
     "node": ">=20"
   },
   "optionalDependencies": {
-    "@cornhsu/parity-win32-x64": "2.3.0",
-    "@cornhsu/parity-win32-arm64": "2.3.0",
-    "@cornhsu/parity-linux-x64": "2.3.0",
-    "@cornhsu/parity-linux-arm64": "2.3.0",
-    "@cornhsu/parity-darwin-x64": "2.3.0",
-    "@cornhsu/parity-darwin-arm64": "2.3.0"
+    "@cornhsu/parity-win32-x64": "2.4.0",
+    "@cornhsu/parity-win32-arm64": "2.4.0",
+    "@cornhsu/parity-linux-x64": "2.4.0",
+    "@cornhsu/parity-linux-arm64": "2.4.0",
+    "@cornhsu/parity-darwin-x64": "2.4.0",
+    "@cornhsu/parity-darwin-arm64": "2.4.0"
   }
 }