You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A Web page may have a <script type="module" src="page.js">. Browser will initiate loading script. If the "page.js" has import statements - then those resources will also be loaded before "page.js" is evaluated, and so on recursively in a waterfall.
The performance of the application depends on the dependency graph of the "page.js". However, this performance overall is not current easily observable using existing tools.
The text was updated successfully, but these errors were encountered:
Thanks for filing this! Would you be interested in discussing this on the WebPerfWG call? It'd be interesting to discuss what the current solutions for this issue are, and why they are not necessarily sufficient.
A Web page may have a
<script type="module" src="page.js">
. Browser will initiate loading script. If the "page.js" hasimport
statements - then those resources will also be loaded before "page.js" is evaluated, and so on recursively in a waterfall.The performance of the application depends on the dependency graph of the "page.js". However, this performance overall is not current easily observable using existing tools.
The text was updated successfully, but these errors were encountered: