feat: foundational infrastructure for CSS Custom Properties export#20
feat: foundational infrastructure for CSS Custom Properties export#20cryptodiscolab wants to merge 1 commit into
Conversation
|
Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA). View this failed invocation of the CLA check for more information. For the most up to date status, view the checks section at the bottom of the pull request. |
|
@google-cla check |
|
Thank you @cryptodiscolab! I'm gonna get to all these here soon. Sorry for the delay. |
Closes #54. The existing `design.md` bin entry produces a `node_modules/.bin/design.md` shim file on Windows. Because the basename ends in `.md`, Windows command resolution short-circuits to the Markdown file association before iterating PATHEXT, so PowerShell opens the shim in the user's Markdown editor (VS Code by default) instead of executing it. Add a `designmd` alias bin that resolves to the same entrypoint. The dot-free name lets the npm CMD/PowerShell shims resolve cleanly via PATHEXT on Windows while leaving the original `design.md` bin in place for posix users and existing scripts. * `packages/cli/package.json`: add the alias to the bin map. * `README.md`: add a "Windows tip" callout under CLI Installation explaining when to reach for the alias. * `packages/cli/scripts/check-package.ts`: new check #5c verifies the bin map exposes at least one dot-free alias so future package edits don't silently regress this. Pre-existing failure #20 (`CLI spec command failed to load spec.md`) reproduces on `main@8ecd464` with my changes stashed (23 pass / 1 fail); adding 5c yields 24 pass / 1 fail, with no other deltas. Co-authored-by: d 🔹 <258577966+voidborne-d@users.noreply.github.com>
|
@cryptodiscolab We are working on a larger grouping and themes import that affects this feature. The CLA isn't signed and this will be a big conflict here soon so I'm closing. Thank you for the time and effort. In the future please feel free to raise an issue first and tag me to so we can coordinate on the contribution. |
2 participants
Technical Proposal: CSS Custom Properties Exporter for design.md
This proposal introduces a robust, dependency-free utility to bridge the gap between
design.mdspecifications and frontend implementation by exporting design tokens directly into CSS Custom Properties.💡 Rationale
While
design.mdsuccessfully centralizes visual identity in a machine-readable format, frontend engineers still face manual labor when mapping these tokens to CSS. To fulfill the promise of "Design-as-Code," we require a formal automation layer that transforms YAML-defined tokens into standard web variables (--custom-properties).This implementation addresses Issue #15 by providing a portable Node.js exporter.
🛠️ Implementation Overview
Key Features
fs,path) to ensure compatibility across all environments.:rootscope with valid CSS syntax.Usage Pattern
Authored by the Senior Engineering Leadership at Crypto Disco DailyApp.