tokens-bruecke 3.13.1 → 3.14.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 +6 -0
- package/README.md +1 -1
- package/package.json +2 -2
package/CHANGELOG.md
CHANGED
|
@@ -1,3 +1,9 @@
|
|
|
1
|
+
## [3.13.1](https://github.com/tokens-bruecke/figma-plugin/compare/v3.13.0...v3.13.1) (2026-10-02)
|
|
2
|
+
|
|
3
|
+
### Bug Fixes
|
|
4
|
+
|
|
5
|
+
- **cli:** read FONT_STYLE on number variables as FONT_WEIGHT ([#96](https://github.com/tokens-bruecke/figma-plugin/issues/96)) ([18a260d](https://github.com/tokens-bruecke/figma-plugin/commit/18a260d9dcd8725b32d58b4f1ee7c9964f9e1c87))
|
|
6
|
+
|
|
1
7
|
## [3.13.0](https://github.com/tokens-bruecke/figma-plugin/compare/v3.12.2...v3.13.0) (2026-10-02)
|
|
2
8
|
|
|
3
9
|
### Features
|
package/README.md
CHANGED
|
@@ -1112,7 +1112,7 @@ The `alpha` is the opacity Figma applies on top of the referenced color. If the
|
|
|
1112
1112
|
Figma has exposed these variables to plugins in two shapes so far: current runtimes (the Figma web app, and what `setValueForMode` accepts) use `{ "color": <alias or rgba>, "opacity": <0..100 or alias> }`, while Figma Desktop 126.x returned a `COMPOSE_COLOR` expression. The export reads both. The import writes the current shape and falls back to the expression for runtimes that only accept that one.
|
|
1113
1113
|
|
|
1114
1114
|
> [!WARNING]
|
|
1115
|
-
>
|
|
1115
|
+
> Older Figma clients, including Figma Desktop 126.x, can read these variables but refuse to write them in either shape ("Composed color variable values are not supported"). Figma has since enabled writing them through the Plugin API ([figma/plugin-typings#375](https://github.com/figma/plugin-typings/issues/375)), so update Figma if the import skips them. On an outdated client the plugin leaves those values untouched, reports how many were skipped and asks you to update Figma. Other tokens in the same import are not affected.
|
|
1116
1116
|
|
|
1117
1117
|
> [!NOTE]
|
|
1118
1118
|
> Figma is still changing how these values are exposed to plugins. If a color variable comes back in a shape the plugin does not recognise, the export leaves that variable out and logs a `[tokens-bruecke] Skipped variable …` warning with the raw value to the Figma console (`Plugins → Development → Open console`) instead of failing. Please paste that warning into [#91](https://github.com/tokens-bruecke/figma-plugin/issues/91).
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "tokens-bruecke",
|
|
3
|
-
"version": "3.
|
|
3
|
+
"version": "3.14.0",
|
|
4
4
|
"license": "MIT",
|
|
5
5
|
"repository": {
|
|
6
6
|
"type": "git",
|
|
@@ -58,7 +58,7 @@
|
|
|
58
58
|
"@codemirror/search": "^6.7.1",
|
|
59
59
|
"@codemirror/state": "^6.7.1",
|
|
60
60
|
"@codemirror/view": "^6.43.6",
|
|
61
|
-
"@figma/plugin-typings": "^1.
|
|
61
|
+
"@figma/plugin-typings": "^1.140.0",
|
|
62
62
|
"@figma/rest-api-spec": "^0.25.0",
|
|
63
63
|
"@lezer/highlight": "^1.2.3",
|
|
64
64
|
"@octokit/core": "^5.0.0",
|