Jake

The JSON is the raw transformed component data from the adapter, which is what each formatter process into a snippet (theres a formatter for each React, Angular, Web Component, Vue)....

sorry for being so late to this. can you try again and see if your issues were resolved by https://github.com/figma/plugin-samples/pull/86

@John-Oula can you provide the error you are getting and your version of node? on fresh install i am getting a successful build.

would love that. could you provide an example of the desired output code for a svelte component definition and instance? for example... for this button definition: i am generating this...

ah yes this is great feedback, i have a pretty greedy cleaning regex, should probably add a bit more discretion. as for the ignoring prefix convo, run the configuration mode...

this is interesting! token studio [uses shared plugin data](https://docs.tokens.studio/contributing/shared-data), so it is theoretically possible to access these values. im curious what you would be looking to surface with your templates?...

this is great feedback and i have had this floating around in the back of my head for awhile now. i want to avoid generating svg for every single node...

I agree on this being a great addition. This would also unblock desires for additional "global" node-type based templates. see #21. Currently thinking over a few different approaches here. One...

Work on this project is slow coming due to capacity, however i think this could merge nicely with some of the thoughts i had for query interfaces for figma.children.

i think the best way to do this is to put a template on the child that renders the child code and use `figma.children` on the parent. is there any...