fix underprefetching

Author: wmertens

packages/qwik/src/optimizer/src/plugins/bundle-graph.ts

@@ -58,10 +58,7 @@ export function convertManifestToBundleGraph(
   for (const bundleName of Object.keys(graph)) {
     const bundle = graph[bundleName];
     const imports = bundle.imports?.filter((dep) => graph[dep]) || [];
-
-    // We only include dynamic imports that have qrl segments
-    // If the dev wants to include other dynamic imports, they can just make a qrl()
-    const dynamicImports = bundle.dynamicImports?.filter((dep) => graph[dep]?.hasSegments) || [];
+    const dynamicImports = bundle.dynamicImports?.filter((dep) => graph[dep]) || [];
 
     // Overwrite so we don't mutate
     graph[bundleName] = {

packages/qwik/src/server/preloading.md

@@ -31,15 +31,16 @@ If we have available bandwidth, we can download code before it is needed. We sho
 
 To know which code is most likely to be needed, we can use the bundle scoring system.
 
+We will err on the side of caution, so if we are not sure, we will preload the bundle. This is better than making the user wait. In the end, all of the code that might be needed for the current page should be preloaded. However, we should make sure that bundles that are more likely to be needed are preloaded first.
+
 ### Bundle scoring system
 
-Each bundle gets a score based on:
+Each bundle gets some metrics that will be used to score it. The scoring should help us decide which bundles to preload first.
 
 - Interactivity: How much impact to interactivity is there if the bundle is missing?
   - score 0 to 5
   - a click handler is very interactive, but the Task that gets executed by the signal that changes might also be important
-  - qwik core is not interactive at all, but its importers are
-  - dependencies get the sum score of their importers
+  - qwik core is not interactive directly, so it gets 0.
 - Size: How much code is there to download?
   - score: percentage of total js bundle size, including all static imports and their static imports etc
   - heavy bundles that are not interactive should not be preloaded at all, but very interactive bundles should be preloaded before others, so that smaller bundles can download in parallel.