Skip to content

Releases: arvindrk/extract-design-system

v0.1.9

03 Apr 16:45

Choose a tag to compare

0.1.9

This patch release improves package trust signals and repository hygiene without changing the CLI's extraction behavior or output format.

Highlights

  • Added a CI workflow for push and pull request validation
  • Added contributor-facing project docs:
    • CONTRIBUTING.md
    • CODE_OF_CONDUCT.md
    • SECURITY.md
  • Added GitHub issue templates for bug reports and feature requests
  • Added a pull request template for more consistent contributions
  • Improved README.md with:
    • a CI badge
    • a quick start section
    • clearer community and support links
  • Improved npm discoverability with additional package keywords
  • Expanded metadata tests to validate key package trust fields

Why this release

This release is focused on improving project health, maintainability, and public package quality signals, especially for package registries and evaluators that consider documentation, CI, and community standards.

Impact

  • No breaking changes
  • No API changes
  • No expected changes to CLI behavior
  • No changes to generated token file structure

Verification

Validated with:

  • npm run typecheck
  • npm test
  • npm run build
  • npm pack --dry-run

All passed successfully.

v0.1.8

01 Apr 02:51

Choose a tag to compare

#v0.1.8

Strengthen test coverage

v0.1.7

01 Apr 02:43
906db15

Choose a tag to compare

v0.1.7

This release improves extraction reliability and output quality, while clarifying the security model around analyzing third-party websites.

What's improved

  • The CLI now rejects malformed URLs and unsupported non-HTTP(S) URLs earlier.
  • dembrandt output parsing is more robust when stdout includes debug noise before the JSON payload.
  • Normalization now filters blank values more consistently across colors, typography, spacing, radius, and shadows.
  • README and skill docs now more clearly frame extracted website data as untrusted input that should be reviewed before broader use.
  • Test coverage was expanded across CLI flows, normalization behavior, and extractor edge cases.

Notes

  • No breaking changes were identified in this release.
  • This is primarily a reliability and documentation hardening release.