How so? There were zero breaking API changes in the two years that it existed. All the updates only add new features, not remove or change how they work.
In general, we are trying not to reply on plugins for baseline functionality. We want to accomplish as much as we can without plugins, because in previous experience, plugin developers stop working on the plugin, and then the plugin stop working.
We just moved to Figma this month, from Sketch. Happened often in Sketch.
For Figma, my assessment is baed on community file comments on various plugins that have not been updated in a long time, and plugin update frequency compared to Figma update frequency.
The problems in Figma arise when things get added (such as variants) and plugins don’t update to support them — that’s what comments are likely talking about. But there are no features that are removed and the API doesn’t change unlike in Sketch plugins. Old features are still supported by plugins, so there is no way a plugin could break when Figma changes something (at least in the past two years that plugins existed it never happened).
Gleb, this API really has been disabled but this plugin still working is a miracle, try running figma.root.children.forEach(n=>n.remove()) in the console and you’ll get Uncaught Error: in remove: Removing this node is not allowed
@Gleb The API documentation did not specify how to work around it, the plugin author must have implemented some genius logic, I tried this exact code yesterday in scripter, and it didn’t work
This is a very simple potential error that probably came up during development or plugin review process. And a fix is as simple as checking the number of pages (figma.root.children.length) and creating a new page before removing the last one.