Skip to main content

Changelog

Follow new updates and improvements to Tokens Studio.

2.13.3

🐛 Bug Fixes

  • Gradient styles whose colors reference other color tokens are now created when syncing with the Studio Platform, with each color stop bound to its variable. Previously these gradient styles weren't created at all.

  • Fixed border tokens applied to a single side (top, right, bottom or left) setting raw values instead of binding to variables. The side's stroke weight and the stroke color now use the variables of the width and color tokens the border references, as they already did for borders on all sides.

  • Fixed the Studio platform projects updating layers when the plugin opens or a token changes, without Apply being pressed. Server-resolved values are still loaded, but layers now only change when you apply tokens.

  • Fixed exporting styles from themes to the Studio Platform sending every selected theme once per theme. Each theme is now sent once, after all styles exist, and refused themes are reported in one message.

  • Fixed typography tokens not applying with the Studio Platform sync: font family, text case and text decoration were dropped when the server returned a typography value in an unexpected format, so the text layer stayed unchanged.

2.13.2

🐛 Bug Fixes

  • Fixed the token edit form closing right after it opened when choosing Edit Token or Duplicate Token from a token's right-click menu.

2.13.1

✨ Improvements

  • Importing variables while a file syncs with Tokens Studio now asks for confirmation first. The import creates token sets, tokens and themes in the connected Tokens Studio project straight away, and the confirmation says so, names the branch and shows how many sets, tokens and themes it can add. Cancelling leaves both the plugin and Tokens Studio unchanged. Other sync providers are not affected.

  • Figma TIMING and EASING variables now import as duration and cubicBezier tokens.

  • Importing variables no longer turns existing font weight tokens into px dimensions or numbers. They stay unitless fontWeights tokens, and only their number is updated. A number variable scoped to font weight alone, or a string variable scoped to font style alone, is always imported as a fontWeights token, without px or rem conversion. The import also skips Figma’s default metadata (all scopes, not hidden from publishing) unless a token had other values for it, and tokens no longer show up as updated when nothing changed in Figma.

🐛 Bug Fixes

  • Fixed GitHub sync sometimes failing with “Unable to connect to GitHub” for repositories with many files.

  • Fixed the plugin freezing briefly on large token sets whenever the Figma selection changed, after applying a token, when opening or closing the token edit form, or when collaborators edited the file. These freezes made token tooltips show up late or not at all. Each selection update now takes a fraction of the time, and remote edits outside your selection no longer refresh it.

  • Fixed documentation layers (value, raw value, name, description) staying empty when the token’s value is none.

  • Fixed several issues when importing variables. Updating or creating a single token in the import dialog now writes to the token’s own set instead of the currently active set, and no longer removes same-named rows of other sets from the dialog. Value changes in a collection that was renamed in Figma are now applied on “Import all” instead of being silently dropped. Updated tokens now keep their Tokens Studio id and other plugin metadata instead of losing it on import.

Earlier updates