design.md

In @google/design.md@0.3.0, serializeTailwindV4() already appends one trailing newline, but the CLI uses console.log(), which adds another. Fix the exporter by replacing console.log(output) with process.stdout.write(output) for css-tailwind export output. Until a release containing the fix is available, normalize the generated file after export:

./node_modules/.bin/designmd export --format css-tailwind DESIGN.md \
  | perl -0pe 's/\n+\z/\n/' > out.css

Verify the file ends with exactly one newline:

python3 -c "from pathlib import Path; b=Path('out.css').read_bytes(); print(len(b)-len(b.rstrip(b'\\n')))"

The expected result is 1. This prevents strict whitespace checks such as git diff --check from failing on checked-in generated CSS.

Use the css-vars export format:

npx @google/design.md export --format css-vars DESIGN.md > design.tokens.css

This generates a :root block containing CSS custom properties, for example:

:root {
  --color-primary: #1A1C1E;
  --spacing-md: 16px;
}

To add a namespace prefix to every variable, use --prefix:

npx @google/design.md export --format css-vars --prefix ds DESIGN.md > design.tokens.css

Dark-theme and media-query variants are not included in the initial implementation; support was added in PR #109.

A regular computer uses bits that are either 1 (on) or 0 (off). A quantum computer uses qubits, which can exist in a combined state called superposition until the result is measured. This lets quantum computers explore many possibilities at once for certain complex calculations, though they are not simply faster versions of ordinary computers.

This crash occurs in @google/design.md@0.2.0 when a spacing value in DESIGN.md is a YAML non-string value, such as unit: 8. Upgrade to v0.3.0, which includes the runtime type-guard fix. As a workaround, quote all dimension values:

spacing:
  unit: "8"
  "1": "4px"

Use unit: "8px" instead of unit: 8 or unit: 8px without quotes.

Upgrade to v0.4.0, where primitive types are rendered from spec-config.yaml. If applying the change manually, add a types section, for example:

types:
  Color:
    description: "A color value is any valid CSS color string."
    formats:
      - "Hex: #RGB, #RGBA, #RRGGBB, #RRGGBBAA"
      - "Named colors: red, cornflowerblue, transparent"
      - "Functional: rgb(), rgba(), hsl(), hsla(), hwb()"
      - "Wide-gamut: oklch(), oklab(), lch(), lab()"
      - "Mixing: color-mix(in srgb, ...)"
    note: "All color values are internally converted to sRGB for WCAG contrast checking."
  Dimension:
    description: "A dimension value is a string with a unit suffix."
    units: [px, em, rem]

Then remove the static Color and Dimension prose from spec.mdx and update the spec generator to iterate over types in spec-config.yaml, the same way it renders typography_properties. Run the spec-config and spec-generator tests to verify the output.