+1 for this feature! I understand that it’s not easy, as some plugins / plugin actions make changes. But hopefully there’s a way of flagging an entire plugin (or an individual plugin action) as something that makes changes (and therefore requires “edit” access to use) vs plugins / plugin actions that don’t make modifications (and can therefore safely be used with just “view” access).
We’re using the Token Studio plugin and it’d be great if our developers could launch the plugin and simply view the design tokens used.
Yes, please! We’d love to make use of a localization plugin. It’d be easiest if the devs can push the strings themselves directly from Figma, so it’s one workflow for one person and not multiple flows for multiple people.
We have a plugin that helps developers convert Figma to code more easily. The developers usually only have view access, so they cannot use the plugin. This is a really big pain point for us.
Plugins made for DevMode can now be run by viewers!
Plugin in Dev Mode can access the current page, listen to events, and make network requests, but crucially they cannot modify the document, with the exception of writing certain metadata like pluginData and relaunchData. So, any method or operation in the plugin API that creates new nodes, deletes existing nodes, or modifies an existing node isn’t available in Dev Mode.
This would be awesome