unstale

npm / @figma/code-connect

@figma/code-connect

What changed in @figma/code-connect 2, from its official release notes, upgrade guides and advisories. Sources checked 2026-10-21.

4 breaking3 new APIs and options1 performance3 behavior and defaults4 fixes and other

See which of these apply to your code, ranked, in your agent:

npx @unstale/cli init

@unstale/cli 0.2.1 on npm

@figma/code-connect 215 changes

Breaking changes 4

  • The command always generates a parserless template file, including in projects configured for a framework-specific parser.

    2.0.2release notes

  • Unsupported output filenames are rejected with guidance to use .figma.ts or .figma.js.

    2.0.2release notes

  • Framework-specific parsers can now be used only with migrate and unpublish; other commands exit with guidance to migrate to template files.

    2.0.0release notes

  • Framework-specific parsers will no longer receive updates or support; template files are the only actively maintained way to use Code Connect.

    2.0.0release notes

New APIs and options 3

  • Set this environment variable to 1 to disable telemetry of preflight validation failure counts sent by figma connect publish.

    2.0.2release notes

  • Running a command with this flag shows the stack trace for a network request failure.

    2.0.2release notes

  • The command now accepts a component template file declared in a .figma.batch.json file, allowing that component to be previewed individually.

    2.0.1release notes

Performance 1

  • Performance optimizations were made for the preview command.

    2.0.0release notes

Behavior and default changes 3

  • JSON output now includes each connection's source file.

    2.0.2release notes

  • Publishing now sends preflight validation failure counts to Figma; set DO_NOT_TRACK=1 to disable this telemetry.

    2.0.2release notes

  • On Professional plans, publishing now confirms the active library and framework when they are first selected, and explains how to change the selection or upgrade if the limit is exceeded.

    2.0.2release notes

Fixes and other changes 4

  • File discovery now works in project folders with special characters while preserving configured exclusions and project-relative includes with a leading slash.

    2.0.2release notes

  • The command leaves existing template files unchanged and reports success when no components need migrating.

    2.0.2release notes

  • Filtering text layers by parent path no longer crashes, including when the text is inside nested instances.

    2.0.2release notes

  • Network request failures now show the underlying reason, such as a timeout or connection error, instead of only “fetch failed.”

    2.0.2release notes