Exporters in CI/CD and CLI going 1.0!

Enjoy the newest CLI features that will empower your developers even more.

This version was released on November 30, 2023

We are super excited to announce that after the recent release of the new developer experience, we are also moving our CLI to stable release 1.0, including heaps of improvements and fancy new toys to play with — check it out!

Introducing: Run exporters from CLI

We're introducing the biggest addition to the CLI yet: The ability to run exporters from your command line or CI/CD pipelines. This means you can completely bypass Supernova hooks if you want to manage the lifecycle of the code or asset yourself.

There are many use cases for this feature, including situations when:

  • You are unable to use hooks because you can't give access to private repositories due to security limitations / rules yet you still want to use exporters to deliver code/assets to your codebases.
  • You want to run exporters behind company VPNs.
  • You want to have detailed control over when exporters run.
  • You want to integrate exporters with your CI/CD pipelines and with release lifecycle.
  • You want to integrate exporters with events in your repositories, such as GitHub actions.
  • You want to run exporters as part of your versioning cycle.
  • You want to use exporters locally from your command line.
  • And many more, depending on the setup you're running.

We've updated our documentation to show what all is possible but here is the TLDR:

null

This new command in the CLI will take your exporter in exporterDir and generate output similar to how you would from VSCode extension or our developer pipelines! You have now obtained the same code you'd get from any other place you can run the exporters:

null

This powerful new addition to the CLI will unlock many new workflows you were asking for and we can't wait to see what you build with it.

Introducing: CLI 1.0

After many months of polish and feedback from you, we are moving CLI to 1.0. This brings some much needed improvements, and general availability of the CLI, so you can start using it in your production environments without any issues.

The updates include:

  • Support for OSX, Windows and Linux environments.
  • Support for Node 16, 18 and 20.
  • Reworked success reporting of commands.
  • Colors!
  • Added help and examples to each command.
  • All current commands polished and aligned on reporting.
  • Much better error handling, error reporting, and code resilience.
  • The CLI will properly signal to the system when errors occur, including dedicated stable error codes.

And there are many more improvements under the hood. Let us know how we did!

Introducing: CLI documentation

To make your CLI experience even better, we updated our new developer documentation with a new section focused on the CLI and how to use it. This includes descriptions and examples of all commands, how to use them, and examples of how the CLI can be integrated with CI/CD pipelines.

Other

We've also fixed some pesky bugs and improved some behaviors to make your life easier.

General

  • It's now possible to paste ordered and unordered lists into tables.
  • We have fixed all reported issues with the npm proxy that you may have encountered in the last few days while we switched internally to a different, much more efficient approach. This will give us the opportunity to significantly improve the private packages going forward.

Figma Variables Plugin

  • Figma variables plugin properly imports transparency data now.
  • Synchronizing multiple variables in multiple modes (1000+) does not result in the plugin UI getting stuck and not being refreshed.
  • Collections in "Collections not in Supernova" are now unchecked by default.
  • Plugin shows the proper empty state if you don't have any variables in your file.
  • The Open design system button now leads to the proper design system.
  • Synchronizing extra collections after the initial import doesn't move the collection into the unsynchronized collections.

 

That's it for this release, and we'll be back with more soon. As always, if you'd like to see something new, fixed, or improved, join our Slack community — we're always there. You can also request a feature via our Feature Request Portal. Thanks for your support!