A problem related to Chromium CDP used by SipLoader

[Web-Distortion]

SipLoader uses the initiator of a request defined in Chromium CDP to determine dependencies among resources (source code is here).
This is not fine-grained enough as we do not know when the requested resources are actually evaluated.

[SipLoader]

What's the exact meaning of fine-grained here? Currently SipLoader evaluates a requested resource object when the object has no precedent dependencies.

[Web-Distortion]

Fine-grained here means that when a JS file A requests for another JS file B, SipLoader cannot determine when to evaluate B upon receiving it: should it

1. pend the execution of A and directedly evaluate B, or
2. wait until A is entirely evaluated.

[SipLoader]

Yeah, that's the case. But tracking such fine-grained dependencies requires the data flow information during web page loading, which cannot be simply collected by Chromium DevTools Protocol. We are considering to integrate a finer-grained dependency tracking mechanism into SipLoader that can indicate the exact order of object evaluation.