But why? I don’t see any reason why that won’t work if they are separate. After duplicating use the Swap Library feature if necessary.

I agree, this all works super weirdly in Figma and feels very raw. But they just added these mechanics so hopefully that would improve in the future.

@Gleb Sorry I didn’t explain it well. It works when copying files. Figma will duplicate the file correctly with all links, rewriting any instances links in the new file to point to components in that new file (if there are any instances there at all). This is very cool, although I’d rather like to see a dialog asking me where do I want to point instances links during/after copying.

Also, the issue we discussed was when I try to merge content or just link content (instances) to different files/libraries. DSO helps up to some point, it relinked some pages well, but only if the library was inside the file. Component Relinker did it by (I guess) caching the external library, but it crashes on large libraries, and relinking sometimes stops in the middle of the process. I tried the Swap option as well. For this, I need to have both libraries published, and it’s buggy, there are always missing library issues for some styles or icons. But I’ll dig into it more, thanks. Also, if I want to add bulk components to my library, every time I paste components to that file they become instances. Again, it would be nice to see a dialog: copy components or create instances. Otherwise, I don’t see a way to enrich libraries unless I CUT from the old library, but I don’t want to cut, I want to keep them where they were as well.

I tried your Master as well, (thanks for contributing!) it also helps with some things, but not with this particular problem.

Anyway, I managed to solve my issue, most of the things are now sorted out, my libraries are updated and properly linked, although the process was definitely not straightforward.

I guess due to Figma limitations it is not possible to link across files with plugins, is that correct?

Ah, ok, that makes sense. Yes, there is no perfect solution and swap library can be buggy at times. Glad you solved the issue though!

I think the main issue with it is that it only works with one component at a time and you need to relink multiple components. Is my assumption correct? Because other than that its versatility allows you to use it on any combination of local/published components.

Yep.

Thanks! @Gleb

I think the main issue with it is that it only works with one component at a time and you need to relink multiple components. Is my assumption correct?

Yes. But I will still keep it, it’s a useful plugin, good job.

Hello, I’m having some issues with the published components feature.

In my team we need to move an icon set out of a UI kit to create an isolated library for icons. When we cut and paste each icon in the new file, the components using those icons don’t recognize the new link and the action restore component appears on the right panel of the screen.

Any advice for this please.

Thanks in advance

For those who are using local components because they’re on free plans like me and want to move their master components to a different file while ensuring the instances link to the new file, use InstaRelinker by UniteUXTeam.

As you can see in the screenshots, the left column shows my old file’s master component (local), and the right column shows my new file’s master component (local). Hope this helps!