New:

• We are introducing NEGATE as a Prototyping ExpressionFunction type!

New:

• Plugins are now able to explicitly unbind variables from nodes. See setBoundVariable.
• variableIds are now returned in a similar order to the Figma Design UI. See VariableCollection#variableIds
• Adds ability to set and query pluginData on Variable and Variable Collection nodes.
• Adds textRangeFills to the boundVariables structure. This will be populated on text nodes which have color variables bound to substrings.
• Plugins/widgets that touch straight connectors and set endpoint magnets other than CENTER or NONE will now error in development. Please update your code to use the CENTER or NONE magnets for straight connectors before 2024. See Version 1, Update 79 for more details.
• Added support for the devStatus field on Frames, Components, Component Sets, and Instances.

The Plugin API runtime has been updated to ensure proper usage of figma.showUI.

It is unsafe to call figma.showUI within an event handler for the figma.codegen.on("generate") event. In development, figma.showUI will now throw an error when called as a result of a figma.codegen.on("generate")

If you need to trigger code inside an iframe as the result of a generate callback, you should instead move the call to showUI outside of the event handler and use figma.ui.postMessage to communicate with the iframe from within the callback. This will ensure that your plugin can to handle concurrent generate events. Here's a code example for how to do this.

We're introducing an improved way to attach straight connectors to nodes in FigJam with a new CENTER magnet. Starting in 2024, straight connectors will only be able to attach to CENTER and NONE magnets. The magnets for elbowed connectors will remain unchanged.

Notice of breaking change:

New

• Add better documentation for resolving variable values. See resolveForConsumer and resolvedVariableNodes
• Add support for localhost in the manifest networkAccess allowedDomains field. See manifest networkAccess docs.
• Add the maskType property. For nodes that are used as masks (where node.isMask == true), maskType can be used to get/modify the masking type used (alpha, vector, or luminance) for the mask operation.

New:

• Add detachedInfo to detached instances to indicate if a node is detached from the main component, and to identify its original main component.
• Add figma.constants.colors, which maps color palette names to ColorPalette. We provide figJamBase and figJamBaseLight, a set of official FigJam colors.
• Each Reaction object has an actions array replacing the existing action property for executing multiple actions on the same trigger
• The Action object supports two new action types:
  • "SET_VARIABLE" for modifying the value of a variable based on a static value, another variable, or an expression
  • "CONDITIONAL" for checking if a condition is met before performing an action
  • For a general guide on using the new action types, see the updated guide for the Action object.

See the reactions property page for more details and code samples.

Notice of breaking change:

This update fixes a bug with the optional networkAccess key in the plugin manifest. Previously, we had an error where we would treat local worker scripts as well as blob: URLs as external resources. If you were affected by this, you can now update your networkAccess field.

New:

• Figma will now return inferred variables when there are variables in the file that match the raw values used in your design.
• Add openTypeFeatures property for text nodes to expose OpenType features that have been explicitly enabled or disabled.

The Variable object has been extended with with the ability to read and define a variable's code syntax field. Code syntax allows you to represent design variables in code using custom, syntactically correct variable names to support a seamless handoff experience. It can be configured for different contexts, including CSS, SwiftUI, and Compose. A variable's code syntax will appear in Dev Mode's code snippets when inspecting elements using the variable.

New:

• Variable.codeSyntax describes the current code syntax of a variable.
• Variable.setVariableCodeSyntax and Variable.removeVariableCodeSyntax let you modify the the codeSyntax field.

This update contains a small change for users of the Variables API public beta.

When getting or assigning elements to the Variable.scopes array, please update your code to use 'STROKE_COLOR' instead of 'STROKE'. The meaning is the same. The value 'STROKE' is deprecated and will no longer be supported in our type definitions.

For a full list of possible values, see VariableScope.

Color management is now supported within Figma! This version introduces properties for the color profiles of documents and exports.

New:

• Read-only access to the document's color profile.
• Read/write access to colorProfile for ExportSettings.