Future features for Plugma

[gavinmcfarland]

This is a place to suggest ideas for future releases of Plugma.

Please limit one idea per comment.

[gavinmcfarland]

Better create command that's dynamic and supports options like, typescript, eslinting, plugin types (e.g. with and without UI)

[gavinmcfarland]

Ability to inspect any node on the canvas and pin certain properties

[gavinmcfarland]

Support for individual screens for each plugin command

[gavinmcfarland]

Support for widgets

[gavinmcfarland]

Ability to change theme mode from browser preview

[gavinmcfarland]

Customisable toolbar so developers can configure their own options

[gavinmcfarland]

Custom console inside plugin that can run the Figma API and echo results

[gavinmcfarland]

A banner that lets you know the UI is running on local dev server

[m1o191]

First, thanks for your awesome contribution to the figma plugin dev community!
I would like to have the ability to provide some code to be injected in the head tag of the UI, currently, there is no index.html file, but it's important to be able to add code to the head tag, for example, when applying dark theme support based on multiple variables such as the local storage and the user's preferred schema, to avoid FOUC, the code that adds the dark class needs to be in the head.

[gavinmcfarland]

Hi, thanks for your feedback! Good news—this is already built into V2. Things are still evolving, but if you'd like to try it out, you can install it with:

npm install plugma@next

The only breaking change I’m aware of is that you'll need to update your manifest to use a wildcard for WebSockets.

You can find the migration guide here:
Plugma V2 Migration Guide

[m1o191]

Thanks, this came in time! The testing feature looks promising too.