How to process nodes asynchronously in batches

I’m want to search for text styles, colour styles, and components in the background while my UI is displaying a loading screen. AFAIK, the main ways of extracting these elements are single function calls such as figma.getLocalTextStyles() and figma.root.findAll(). Is there a way to “break up” these calls into smaller chunks?

If you make a spinner or something using CSS only (no JS), it will keep on spinning while the task is processing.

There is no way to break up findAll into chunks other than to launch it on different nodes separately. E.g. you can find all frames on each page of the file first and then launch findAll on every frame, pausing the process for a bit after every findAll is complete.

I’m already using pure css for my loading screen

Unfortunately, parts of it still freezes up when I make the expensive function calls:

As for finding all frames on each page, how do I handle the scenario where component nodes are not put inside frames?

Wait for the UI to load and then call the function.

Also, in the example code that you showed in an older post,

You used a Promise to delay your async function processChunks() for every 100 iterations. Does this mean that delay() takes processChunks() off the main JS thread and allow other functions in code.ts (and even ui.html) to execute, then processChunks() takes over again when the delay “expires”?

Wait for the UI to load and then call the function.
Is there a way for me to detect when ui.html has finished loading? I’ve tried 1. checking the Run event with Figma.on:

2. and I’ve also tried to chain it with as async functions:

Method 2 straight up doesn’t work, and method 1 works partially ie plugin UI window appears, but as a blank window until function is complete

Have you tried using findAllWithCriteria?

I was using findAllWithCriteria and it still took a long time (~30sec) with my design system file which has >1000 components and >10k layers. I’m thinking of trying @Gleb’s approach of calling findAllWithCriteria on each frame in each page, but I’ll also need to handle the case for component nodes which are not a part of any frame

From the UI, send a message to the code when the load event fires.