Report a Problem

The title says almost all. I would like to kindly request a couple things regarding the Developer VM: Add a checkmark to the menu item when it is activated If possible, on reloads, keep the downloaded plugin code name instead of incrementing a suffix. If you are concerned about cache, just append a random query string to the request. Changing the name of the file confuses the Debugger that also has to reload all source maps Improve the documentation about the Developer VM in the API docs. Essentially it says “When the option is enabled, these plugins will run in the browser’s JavaScript engine, so that developer tools can be used”. And that we need a debugger statement to find our code. No mention to sourcemaps (hugely important) In fact, with Dev VM on you don’t need the debugger. Sim

I’ve found a couple of situations where it is more likely to crash: stepping over a figma global variable access opening the watch panel (adding a variable there is instant death of the process) taking too long in step-by-step execution Do any other developer experience the same issues? Is there anything that can be done at least to alleviate the issue?

In Figma API there exists isMaskOutline property on Frame like objects https://www.figma.com/developers/api#node-types isMaskOutlineBoolean default: false Does this mask ignore fill style (like gradients) and effects? But am missing this data in Figma Plugin API: figma.com Can found only isMask but isMaskOutline seems to be missing. Is my observation correct, or is this field renamed or accessible in some different way? Thank you for response Jan

I am trying to merge my branch into master but while the blank diff screen is loading I get the following red message “An error occurred”. Checking the console I see there’s a status 500 while trying to load the results.