Hi, thanks for bringing this up. We plan to roll out a fix to the detachedInfo property by the end of day this Wednesday October 11. It’s supposed to give you the component key for remote components.

Hi! I see that now detachedInfo correctly contains component key, thanks. One more question: how can I use this key in dev-mode? If I try figma.importComponentByKeyAsync, I receive error Can't call "importComponentByKeyAsync" in read-only mode

You can’t use figma.importComponentByKeyAsync in dev mode because it modifies the file, and dev mode plugins are read-only.

If you have an instance node that you need to get the component for, you can just use instanceNode.mainComponent: InstanceNode | Plugin API

It seems that I can’t use detachedInfo in case of remote components in dev mode. Is there any possibility to find out what was original component for detached node in dev mode? Maybe detachedInfo could return ComponentNode itself, not just key?

I have the same issue.

HI @James_Yang is there any alternative to get detached component information by key in plugin code generation in dev mode ?

I have a frame node and a detached component.

I very well get the detached info and its component key but i am not able to get the component by its key.