@omkarux/vela 0.5.0 → 0.7.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/CHANGELOG.md +12 -0
- package/README.md +6 -0
- package/package.json +5 -1
package/CHANGELOG.md
CHANGED
|
@@ -3,6 +3,18 @@
|
|
|
3
3
|
All notable changes to this project are documented here.
|
|
4
4
|
This project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
|
|
5
5
|
|
|
6
|
+
## [0.6.0] — 2026-09-11
|
|
7
|
+
|
|
8
|
+
### Added
|
|
9
|
+
- **Spec → Figma description sync.** `npm run guidelines:figma` compiles each component spec's
|
|
10
|
+
intent, code call, Figma-property→prop mapping, hard rules and source paths into that component
|
|
11
|
+
set's Figma description, so a spec edit lands in Inspect the same way a token edit does. Same
|
|
12
|
+
generated-script route as tokens; idempotent by page + name. What it deliberately does not do:
|
|
13
|
+
add or change variants — a spec that adds a prop is design work in Figma and code both.
|
|
14
|
+
- A test asserts every spec keeps the sections the sync compiles (Props with a `tsx` example,
|
|
15
|
+
Hard constraints, Figma mapping naming its page, Anti-patterns), so a spec that drifts in shape
|
|
16
|
+
fails the build rather than silently producing a thinner description.
|
|
17
|
+
|
|
6
18
|
## [0.5.0] — 2026-09-10
|
|
7
19
|
|
|
8
20
|
### Added
|
package/README.md
CHANGED
|
@@ -111,8 +111,14 @@ generated from it:
|
|
|
111
111
|
npm run tokens # → src/styles/tokens.light.css + tokens.dark.body.css
|
|
112
112
|
npm run tokens:figma # → a Plugin API script that creates-or-updates every Figma variable
|
|
113
113
|
npm run tokens:check # fails if the CSS was hand-edited instead of the JSON (runs in CI)
|
|
114
|
+
npm run guidelines:figma # → a script that writes each spec's summary into its Figma description
|
|
114
115
|
```
|
|
115
116
|
|
|
117
|
+
The component specs in `guidelines/` follow the same rule: edit the markdown, and the package,
|
|
118
|
+
the agent docs and the Figma descriptions follow. The one thing no script can do is add a
|
|
119
|
+
variant — a spec that gains a prop is built in Figma and in code, by people, which is what the
|
|
120
|
+
API review is for.
|
|
121
|
+
|
|
116
122
|
Figma's REST API only lets Enterprise plans write variables, so the Figma half is a generated
|
|
117
123
|
script run inside the file (through the Figma MCP or the Scripter plugin). It looks each variable
|
|
118
124
|
up by collection and name, so re-running never duplicates: the first run against the live library
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@omkarux/vela",
|
|
3
|
-
"version": "0.
|
|
3
|
+
"version": "0.7.0",
|
|
4
4
|
"description": "A token-first design system: framework-agnostic tokens and component specs with a React implementation. Two-layer color architecture, separate severity and risk taxonomies, light and dark theming, WCAG AA asserted in CI, zero runtime dependencies.",
|
|
5
5
|
"type": "module",
|
|
6
6
|
"license": "MIT",
|
|
@@ -41,6 +41,10 @@
|
|
|
41
41
|
"clean": "rm -rf dist",
|
|
42
42
|
"tokens": "node scripts/build-tokens.mjs",
|
|
43
43
|
"tokens:figma": "node scripts/sync-figma.mjs",
|
|
44
|
+
"tokens:figma:read": "node scripts/figma-drift.mjs --read",
|
|
45
|
+
"tokens:figma:check": "node scripts/figma-drift.mjs",
|
|
46
|
+
"guidelines:figma": "node scripts/sync-figma-descriptions.mjs",
|
|
47
|
+
"figma:build": "node scripts/figma/build-components.mjs",
|
|
44
48
|
"tokens:check": "node scripts/build-tokens.mjs && git diff --exit-code -- src/styles/tokens.light.css src/styles/tokens.dark.body.css",
|
|
45
49
|
"build": "npm run clean && npm run tokens && npm run build:js && npm run build:css",
|
|
46
50
|
"build:js": "vite build",
|