@figma/code-connect
Advanced tools
Changelog
Code Connect v1.0.4 (7th August 2024)
component
definition in FigmaConnect protocol to be optional and have a default implementation.Changelog
Code Connect v1.0.3 (23th July 2024)
checkouts
folder resolution edge casecreate
command creating invalid code--skip-update-check
flag--label
flag to the publish
and unpublish
commands to publish or unpublish to a custom labelpublish
commandChangelog
Code Connect v1.0.2 (10th July 2024)
Changelog
Code Connect v1.0.1 (20th June 2024)
The automatic update check introduced in v1.0.0 did not show the correct update command for React users with the @figma/code-connect
package installed locally – it always showed the command for globally updating the package.
We now show both npm install @figma/code-connect@latest
and npm install -g @figma/code-connect@latest
as options. React users with the package installed locally should use npm install @figma/code-connect@latest
, and users of other targets (or with the package installed globally) should use npm install -g @figma/code-connect@latest
.
We have temporarily removed the update
command added in v1.0.0.
Changelog
Code Connect v1.0.0 (19th June 2024)
figma connect
, which guides you through the setup process and auto-connects your componentsinclude
/exclude
config optionsfigma.nestedProps
now work as expectedcreate
now outputs Swift files with the correct syntaxChangelog
Code Connect v0.2.1 (17th June 2024)
@FigmaChildren
annotationsChangelog
Code Connect v0.2.0 (14th June 2024)
Code Connect now uses a single CLI tool for all supported targets. This ensures consistency and feature parity, and provides the foundations for our upcoming Android Compose and extensibility support.
For Code Connect Swift users, you should follow the updated CLI installation instructions to install the new CLI version, and update your Code Connect Swift package to v0.2.0
by following the Swift installation instructions.
For Code Connect React users, no change to installation is necessary, and you can simply update the npm dependency to v0.2.0
.
If you have a Code Connect configuration file, you will need to ensure it is located in your React or SwiftUI project root (e.g. alongside your package.json
or .xcodeproj
file), and you will need to update it to remove the top level react
or swiftui
key. The Code Connect CLI will offer to update your config file for you, but in unusual cases a manual migration may be necessary. This allows us to simplify configuration going forward, as each target now has its own configuration file, situated in the project root.
Please let us know via GitHub Issues if you encounter any problems.
--outDir
option to connect create
to specify output directory for created filesfigma.nestedProps
figma.className
figma.textContent
figma.children
@FigmaString
, @FigmaBoolean
and @FigmaEnum
instead of @FigmaProp
. The old syntax is still supported, but we recommend using the new syntax going forward.@FigmaChildren
property wrapperfigma.enum
valuesfigma.boolean
enumsfigma.enum
(e.g. values from an object or enum
) now render correctly (fixes https://github.com/figma/code-connect/issues/55)