tokens-bruecke 3.12.2 → 3.13.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 CHANGED
@@ -1,3 +1,10 @@
1
+ ## [3.12.2](https://github.com/tokens-bruecke/figma-plugin/compare/v3.12.0...v3.12.2) (2026-09-17)
2
+
3
+ ### Bug Fixes
4
+
5
+ - **color:** support the { color, opacity } shape of composed colors ([d486243](https://github.com/tokens-bruecke/figma-plugin/commit/d486243d62e1ea3ea960e77056bdc1c95e7dd770)), closes [#91](https://github.com/tokens-bruecke/figma-plugin/issues/91)
6
+ - **export:** keep exporting when a color variable has an unknown shape ([0a0ba67](https://github.com/tokens-bruecke/figma-plugin/commit/0a0ba670660d7531a85af27bd5152f6213d5fcdc)), closes [#91](https://github.com/tokens-bruecke/figma-plugin/issues/91)
7
+
1
8
  ## [3.12.0](https://github.com/tokens-bruecke/figma-plugin/compare/v3.10.0...v3.12.0) (2026-09-08)
2
9
 
3
10
  ### Features
package/README.md CHANGED
@@ -32,6 +32,7 @@ The plugin converts Figma variables into design-tokens JSON that are compatible
32
32
  - [Split collections into separate files](#split-collections-into-separate-files)
33
33
  - [Split modes into separate files](#split-modes-into-separate-files)
34
34
  - [Omit collection names](#omit-collection-names)
35
+ - [Extended collections](#extended-collections)
35
36
  - [Use as cli tool](#use-as-cli-tool)
36
37
  - [Installation](#installation)
37
38
  - [Usage](#usage)
@@ -388,6 +389,33 @@ Alias references are also rewritten so they point to the flat path (the collecti
388
389
 
389
390
  ---
390
391
 
392
+ ### Extended collections
393
+
394
+ Collections created with [Extend a variable collection](https://help.figma.com/hc/en-us/articles/36346281624471-Extend-a-variable-collection) are exported as collections of their own. Figma stores only what an extension changes, so the export writes all the variables it inherits, with the overrides of its chain applied, which keeps every collection complete.
395
+
396
+ - The value of a variable is the closest override in the chain of extensions, or the value of the root collection when nothing overrides it. An override that was cleared falls through to the parent. Each mode follows the parent mode it inherits from, even when the extension renames it.
397
+ - Aliases to variables of the root collection point to the extension's own variable, so `{Core.color.brand}` becomes `{Regional.color.brand}` inside `Regional`. Aliases to other collections stay as they are.
398
+ - Extensions of a library collection are exported without the variables they inherit, because those live in the library file, not in yours. The export warns about them.
399
+ - With [Omit collection names](#omit-collection-names) the extended collections are skipped with a warning, because they repeat the variables of their root collection and would collide in a single namespace.
400
+
401
+ ```json
402
+ // "Regional" extends "Core" and overrides color/brand
403
+ {
404
+ "Core": {
405
+ "color": {
406
+ "brand": { "type": "color", "value": "#ff0000" },
407
+ "text": { "type": "color", "value": "{Core.color.brand}" }
408
+ }
409
+ },
410
+ "Regional": {
411
+ "color": {
412
+ "brand": { "type": "color", "value": "#00ff00" },
413
+ "text": { "type": "color", "value": "{Regional.color.brand}" }
414
+ }
415
+ }
416
+ }
417
+ ```
418
+
391
419
  ## Use as cli tool
392
420
 
393
421
  The CLI is published on npm: [tokens-bruecke](https://www.npmjs.com/package/tokens-bruecke)