chore(deps): update dependency @figma/code-connect to v1.5.3

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
@figma/code-connect	1.4.4 → 1.5.3

---

Release Notes

figma/code-connect (@​figma/code-connect)

v1.5.3

Compare Source

Fixed

React

• Fixed rendering of nested arrow function callbacks

Features

General

• Adds figma connect preview <file> --unique, which is similar to --all but hides duplicate outputs.

Template files

• Added id to InstanceHandle to expose the instance's Figma node ID. It matches the Plugin API's SceneNode.id, including stable paths for nested instance sublayers.

v1.5.2

Compare Source

Fixed

• Fixed JavaScript template files authored with import figma from 'figma' publishing an unexecutable import.

v1.5.1

Compare Source

• Copy tweaks for CLI support notice

v1.5.0

Compare Source

[!WARNING]
Framework-specific parsers will no longer receive updates or support from August 17th, 2026. Template files will be the only actively maintained way of using Code Connect. See our migration guide for more information and instructions on migrating parser-based Code Connect:
https://developers.figma.com/docs/code-connect/templates-migration-guide/

Fixed

Template files

• Fixed nested rendered examples being dropped or formatted incorrectly when interpolated directly or passed to the React, Swift, and Kotlin child-rendering helpers.
• Migrated template files no longer include unused generated prop constants.

Features

Template files

• Added a --delete option to figma connect migrate that deletes source Code Connect files after they are successfully migrated.
• Template files (TypeScript and JavaScript) now support importing local helper modules via relative paths (for example, ./shared-helpers) to promote reuse of shared formatting and utility logic. Helper code is bundled into the published template so it can run standalone, and helpers may import other local helpers to organize shared logic across multiple files. Only relative imports within the project are supported (external packages are not), and helpers must be brought in with import syntax — require remains available for the Figma API itself. Helper code you don't actually use is left out of the published template, and if the bundled output exceeds the maximum template size, the CLI fails before publishing.

General

• figma connect preview can now render a component in states beyond its default, and inspect its properties:
  • figma connect preview <file> --inspect prints the component's properties and variants — name, type, variant options, and default — without rendering a snippet.
  • figma connect preview <file> --props Name=Value … renders a single specific property combination. Pairs are space-separated arguments (quote a pair only when its name or value contains spaces, e.g. "Has Icon Start=true"). Property names and variant values are matched case-insensitively, unspecified properties keep their defaults, and an invalid variant value is reported along with the valid options. To target a property when two properties share a name but differ in type, prefix the pair with the type, e.g. "BOOLEAN:textMsg=false" "TEXT:textMsg=Hello"; the prefix is optional and only needed to disambiguate.
  • figma connect preview <file> --all renders every property combination of the component — the cartesian product of its variant and boolean properties. Requires a specific component file argument. Use --max-combinations <number> to render fewer combinations when the full set is large.

v1.4.9

Compare Source

Fixed

General

• Fixed parser invocation failing when a path or argument contained a space. This affected the Swift parser (Xcode project / Swift package paths), the Compose parser (Gradle wrapper paths), and the custom parser (any user-provided parserCommand referencing a path with spaces).

Template files

• Fixed template-only projects unnecessarily building and running a native parser. When every Code Connect file is a parserless template (.figma.ts/.figma.js), the CLI no longer invokes the Swift or Compose parser — which is slow at best and can fail outright (for example a Swift package targeting macOS 12 whose Figma dependency requires macOS 13, producing "the library '...' requires macos 12.0, but depends on the product 'Figma' which requires macos 13.0"). Projects that also contain native source files are unaffected and still run the parser.

Swift

• Raised the supported swift-syntax upper bound to allow the 603.x release. Previously the cap below 603 could silently downgrade swift-syntax in projects that depend on both Code Connect and swift-syntax (directly or transitively) on a Swift 6.3 toolchain. Older toolchains remain supported.

Features

General

• Added @figma/code-connect/figma-types-no-require, a variant of the template type definitions for projects that have @types/node installed. The default @figma/code-connect/figma-types entry declares a global require (so const figma = require('figma') works without @types/node), but that declaration overrides Node's own require type and causes errors like Property 'resolve' does not exist on require.resolve(...) elsewhere in projects that use @types/node. Such projects can now use "@figma/code-connect/figma-types-no-require" in their types array instead, adding it to their main tsconfig.json without a separate config. The default entry is unchanged, so no existing setup needs to change.

Template files

• Augmented the getSlot API: getSlot('SlotName') still renders the same way, and the returned value now also exposes connectedInstances (the connected instances directly in the slot). This lets you render a slot's connected children inline. For example getSlot('body').connectedInstances.map((c) => c.executeTemplate().example).

React & HTML

• Augmented the figma.slot API: figma.slot('SlotName') still maps the slot the same way, and you can now also write figma.slot('SlotName').connectedInstances in a props object to render the slot's code-connected instances inline. For example props: { content: figma.slot('Content').connectedInstances }.

v1.4.8

Compare Source

Fixed

General

• Fixed browser compatibility issues where importing @figma/code-connect in Storybook or webpack environments would fail with "Can't resolve 'child_process'" or "Console is not a constructor" errors. Node.js-only modules (child_process, console) are now imported dynamically only when needed by CLI commands, making the package safe to use in browser environments.

Template files

• Fixed parserless template projects failing to publish or parse when Code Connect could not infer a React, HTML, Swift, or Compose parser. The CLI now proceeds without a parser and uses the default template-file globs.
• Fixed a "getInstanceSwap(...)?.executeTemplate is not a function" error that could break a template when getInstanceSwap('prop') referenced an instance-swap property that isn't present on the selected node (for example a property that is conditionally hidden by a boolean). The missing property now renders an inline error, consistent with the other accessors, instead of failing the whole template.
• Fixed migrated text-layer references (from the React/HTML figma.textContent('...') helper) producing a TypeScript error and silently rendering nothing when the layer was missing. Migration now preserves the original behavior — the text renders when the layer is found, and a clear error is shown when it isn't.

Features

Template files

• The figma connect migrate command now uses the same --dir and --file filtering behavior as publish, parse, and unpublish. The migrate-only positional glob argument has been removed.
• The figma connect migrate command can now migrate compatible large source files into batch template files. Files with 10 or more Code Connect docs are attempted automatically, --batch all forces a batch attempt, and --batch none disables batch migration.

v1.4.7

Compare Source

Fixed

General

• The --file (-f) option on figma connect publish, unpublish, and parse now accepts multiple files, so you can target several Code Connect files in one command (e.g. figma connect publish --file a.figma.ts b.figma.ts). Previously only a single file path was accepted.
• Tweak retry behavior for publish command to reduce 429s errors
• Shared flags (--verbose, --token, --config, --dir, --file, --out-file, --out-dir, --api-url, --skip-update-check, --exit-on-unreadable-files, --dry-run) now work whether you write them before or after the subcommand name. Previously, only figma connect publish -v toggled verbose mode; figma connect -v publish was silently ignored.

Compose

• Fixed a crash that prevented the Code Connect Gradle plugin from being used with projects on Kotlin 2.3 or newer. The plugin now runs Kotlin source parsing in an isolated worker process, so it no longer ships an embedded Kotlin compiler in the consumer's build environment and cannot conflict with the host project's Kotlin Gradle Plugin across version upgrades.
• Fixed parseCodeConnect / createCodeConnect failing in multi-module Gradle projects when the plugin is applied to more than one subproject. The task now resolves the -PfilePath/-PoutputDir arguments against the root project so every subproject finds the input the CLI wrote at the build root.
• The Code Connect Gradle tasks now work cleanly with Gradle's configuration cache enabled. Previously, enabling --configuration-cache caused an opaque serialization error; the tasks now store and reuse the configuration cache entry as expected.

v1.4.5

Compare Source

Fixed

General

• The preview command now prints a clearer single-line message if the preview service is temporarily unavailable, instead of repeating a per-file error.
• figma connect preview now splits requests into smaller chunks when previewing many components at once, so previews of large component libraries no longer fail with “Payload Too Large” errors.

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment

Project	Deployment	Actions	Updated (UTC)
shoreline-docs	Ignored	Preview	Aug 14, 2026 2:51pm