As of Chrome v125, the PerformanceResourceTiming entries that get emitted for JS assets that are loaded via dynamic import have changed from being "other" to being "script". This causes the totalDownloadSize method of Navigation under @shopify/performance to change.
As a result, applications that use dynamic imports for progressive loading of the page will appear to have increased download sizes from their previous values in Chrome v124.
These new values do appear to be more correct, as the previous ones excluded these values as "other", but this points to a need to have a better heuristic for matching script & style downloads during a navigation.
Interesting! Doing some digging, this is the CL that changed that behavior.
I agree the behavior is better. I'd love to chat about improving initiator type further, if that helps.
As of Chrome v125, the PerformanceResourceTiming entries that get emitted for JS assets that are loaded via dynamic import have changed from being "other" to being "script". This causes the
totalDownloadSize
method ofNavigation
under@shopify/performance
to change.As a result, applications that use dynamic imports for progressive loading of the page will appear to have increased download sizes from their previous values in Chrome v124.
These new values do appear to be more correct, as the previous ones excluded these values as "other", but this points to a need to have a better heuristic for matching script & style downloads during a navigation.