tokens-bruecke 3.19.0 → 3.20.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 +16 -5
- package/bin/cli.js +1 -1
- package/llms.txt +7 -5
- package/package.json +1 -1
- package/skills/tokens-bruecke/SKILL.md +19 -7
package/CHANGELOG.md
CHANGED
|
@@ -1,3 +1,15 @@
|
|
|
1
|
+
## [3.19.0](https://github.com/tokens-bruecke/figma-plugin/compare/v3.18.0...v3.19.0) (2026-10-14)
|
|
2
|
+
|
|
3
|
+
### Features
|
|
4
|
+
|
|
5
|
+
- export FONT_FAMILY-scoped string variables as fontFamily tokens ([78f5d2b](https://github.com/tokens-bruecke/figma-plugin/commit/78f5d2bc37e785b9e64cab3384516e9d27c136e2)), closes [#118](https://github.com/tokens-bruecke/figma-plugin/issues/118)
|
|
6
|
+
|
|
7
|
+
### Bug Fixes
|
|
8
|
+
|
|
9
|
+
- **cli:** export REST layout grids like the plugin does ([dda46ff](https://github.com/tokens-bruecke/figma-plugin/commit/dda46ffc8b077b9bcf443887f7dd9005d68f5353))
|
|
10
|
+
- **import:** default font scopes only on new variables ([0ae37ed](https://github.com/tokens-bruecke/figma-plugin/commit/0ae37ed626c1308b5f9c96ac2c8cb114a1fee646))
|
|
11
|
+
- preserve exact font weight in text styles ([4a63036](https://github.com/tokens-bruecke/figma-plugin/commit/4a63036cfbb4664775c862d9bd6756aea8d5fd75))
|
|
12
|
+
|
|
1
13
|
## [3.18.0](https://github.com/tokens-bruecke/figma-plugin/compare/v3.17.1...v3.18.0) (2026-10-09)
|
|
2
14
|
|
|
3
15
|
### Bug Fixes
|
package/README.md
CHANGED
|
@@ -40,6 +40,7 @@ TokensBruecke exports Figma variables and styles as design tokens JSON compatibl
|
|
|
40
40
|
- [Options](#options)
|
|
41
41
|
- [Snapshot input](#snapshot-input)
|
|
42
42
|
- [CLI Configuration File](#cli-configuration-file)
|
|
43
|
+
- [Update notice](#update-notice)
|
|
43
44
|
- [For AI agents](#for-ai-agents)
|
|
44
45
|
- [Agentic usage without the REST API](#agentic-usage-without-the-rest-api)
|
|
45
46
|
- [Use as a library](#use-as-a-library)
|
|
@@ -646,6 +647,16 @@ Save this JSON file and pass it to the CLI using the `--config` option. A JSON s
|
|
|
646
647
|
|
|
647
648
|
Each style type in `includedStyles` is merged with its default, so `"text": { "isIncluded": true }` is enough: the group keeps its default name (`Typography-styles`) and the other style types stay excluded.
|
|
648
649
|
|
|
650
|
+
### Update notice
|
|
651
|
+
|
|
652
|
+
The CLI checks npm at most once a day for a newer version. When there is one, it prints a single line to stderr after the export, even with `--quiet`:
|
|
653
|
+
|
|
654
|
+
```
|
|
655
|
+
ℹ️ tokens-bruecke 3.20.0 is available (you ran 3.19.0). Use the latest version with: npx tokens-bruecke@latest
|
|
656
|
+
```
|
|
657
|
+
|
|
658
|
+
It only asks npm for the version number — no tokens, file keys or config are sent — and it never installs anything. The check runs alongside the export with a 1.5s timeout, says nothing when offline, and caches the result in `~/.cache/tokens-bruecke` (or `$XDG_CACHE_HOME`). It is skipped when `CI` is set; set `TOKENS_BRUECKE_NO_UPDATE_CHECK=1` or `NO_UPDATE_NOTIFIER=1` to turn it off elsewhere.
|
|
659
|
+
|
|
649
660
|
### For AI agents
|
|
650
661
|
|
|
651
662
|
This repository and the npm package ship agent-friendly docs:
|
|
@@ -655,7 +666,7 @@ This repository and the npm package ship agent-friendly docs:
|
|
|
655
666
|
- [schemas/cli-options.schema.json](schemas/cli-options.schema.json) — machine-readable config schema
|
|
656
667
|
- [schemas/tokens-snapshot.schema.json](schemas/tokens-snapshot.schema.json) — machine-readable input schema for `--input`
|
|
657
668
|
|
|
658
|
-
For scripted/agent usage prefer `--stdout --quiet` (pure JSON on stdout, logs on stderr) and pass tokens via environment variables.
|
|
669
|
+
For scripted/agent usage prefer `--stdout --quiet` (pure JSON on stdout, logs on stderr) and pass tokens via environment variables. Run it as `npx tokens-bruecke@latest` so the agent always gets the newest release: plain `npx tokens-bruecke` can reuse an old cached copy. See [Update notice](#update-notice).
|
|
659
670
|
|
|
660
671
|
#### Agentic usage without the REST API
|
|
661
672
|
|
|
@@ -666,7 +677,7 @@ If your agent can run code inside Figma — a Figma agent, an MCP server with `e
|
|
|
666
677
|
| Figma Enterprise plan | Required | Not required |
|
|
667
678
|
| Personal access / OAuth token | Required | Not required |
|
|
668
679
|
| File must be published / shared with the token | Yes | No — works on whatever file is open |
|
|
669
|
-
| Network calls
|
|
680
|
+
| Network calls to Figma | Several per export | None |
|
|
670
681
|
|
|
671
682
|
The agent's job is only to dump data; the CLI still owns every transform, so aliases, modes, scopes and DTCG formatting behave exactly as they do in REST mode.
|
|
672
683
|
|
|
@@ -721,13 +732,13 @@ Text, effect and grid styles follow the same pattern — see [schemas/tokens-sna
|
|
|
721
732
|
|
|
722
733
|
```bash
|
|
723
734
|
# From a file the agent wrote
|
|
724
|
-
npx tokens-bruecke --input snapshot.json --output tokens.json
|
|
735
|
+
npx tokens-bruecke@latest --input snapshot.json --output tokens.json
|
|
725
736
|
|
|
726
737
|
# Or straight from stdin, no temp file
|
|
727
|
-
my-figma-agent dump-tokens | npx tokens-bruecke --input - --stdout --quiet > tokens.json
|
|
738
|
+
my-figma-agent dump-tokens | npx tokens-bruecke@latest --input - --stdout --quiet > tokens.json
|
|
728
739
|
|
|
729
740
|
# All the usual options still apply
|
|
730
|
-
npx tokens-bruecke --input snapshot.json --config config.json --split-by-mode --output ./tokens
|
|
741
|
+
npx tokens-bruecke@latest --input snapshot.json --config config.json --split-by-mode --output ./tokens
|
|
731
742
|
```
|
|
732
743
|
|
|
733
744
|
Snapshot mode ignores `FIGMA_API_KEY` / `FIGMA_FILE_KEY`, so a token exported in the environment won't get in the way. Passing `--api-key`, `--oauth-token` or `--file-key` explicitly alongside `--input` is rejected as a conflict.
|