NullVoxPopuli · October 29, 2025 21:34 · Oct 29, 2025 · Oct 2, 2025 · Oct 2, 2025 · Sep 30, 2025
diff --git a/Browsers can't handle large module graphs.md b/Browsers can't handle large module graphs.md
@@ -44,3 +44,12 @@ Related information:
 
 - https://github.com/NullVoxPopuli/vite-lots-of-module-repro
   Lots of modules, if your OS is busy, it'll be slow enough to load correctly. otherwise repros
+
+
+
+---------------
+
+## 2025-10-29
+
+"A" fix goes in to vite 7.2.0-beta.1
+- https://github.com/vitejs/vite/issues/17499#issuecomment-3460646226
diff --git a/README.md → Browsers can't handle large module graphs.md b/README.md → Browsers can't handle large module graphs.md
diff --git a/README.md b/README.md
@@ -43,5 +43,4 @@ Related information:
 ### Repros
 
 - https://github.com/NullVoxPopuli/vite-lots-of-module-repro
-  Lots of modules, takes a long time to load but doesn't have the error (depends on what the OS is doing)
-  - on a machine that is not burdened, this repros
+  Lots of modules, if your OS is busy, it'll be slow enough to load correctly. otherwise repros
diff --git a/README.md b/README.md
@@ -40,7 +40,8 @@ Related information:
 
 - https://github.com/colocohen/quico
 
-### Repros?
+### Repros
 
 - https://github.com/NullVoxPopuli/vite-lots-of-module-repro
-  Lots of modules, takes a long time to load but doesn't have the error
+  Lots of modules, takes a long time to load but doesn't have the error (depends on what the OS is doing)
+  - on a machine that is not burdened, this repros
diff --git a/README.md b/README.md
@@ -39,3 +39,8 @@ Related information:
 ### Things to keep an eye on
 
 - https://github.com/colocohen/quico
+
+### Repros?
+
+- https://github.com/NullVoxPopuli/vite-lots-of-module-repro
+  Lots of modules, takes a long time to load but doesn't have the error
diff --git a/README.md b/README.md
@@ -31,4 +31,11 @@ Related information:
   - [This hn comment](https://news.ycombinator.com/item?id=19722880) implies that the default is 1000 in Chrome -- however, the [vite issue](https://github.com/vitejs/vite/issues/17499) suggests 2000 simultaneous streams.
     This also suggests that a server must also support higher max concurrent streams.
 - General http/2: 
-  - https://sites.google.com/site/mytechnicalcollection/networking/http2
+  - https://sites.google.com/site/mytechnicalcollection/networking/http2
+
+
+---------------
+
+### Things to keep an eye on
+
+- https://github.com/colocohen/quico
diff --git a/README.md b/README.md
@@ -1,5 +1,5 @@
-Vite: https://github.com/vitejs/vite/issues/17499
-Chrome: https://issues.chromium.org/issues/355006326 
+- Vite: https://github.com/vitejs/vite/issues/17499
+- Chrome: https://issues.chromium.org/issues/355006326 
 
 ----------
 

diff --git a/README.md b/README.md
@@ -1,8 +1,13 @@
+Vite: https://github.com/vitejs/vite/issues/17499
+Chrome: https://issues.chromium.org/issues/355006326 
+
+----------
+
 Much of the benefit of vite + http/2 is the ability to rely on cached requests of http/2 -- as in, turning off "disable cache" in the network tools.
 
 However, when an app has to perform 10k network requests on boot, chrome and firefox error with: 
 
-I believe this is potentially related to:
+I believe this is potentially related to limitations in maybe both the browser and the server
 - https://issues.chromium.org/issues/355006326 - the main issue report to Chromium about this use case (large ES module graph)
   - Errors we can receive
     - net::ERR_FAILED

diff --git a/README.md b/README.md
@@ -13,7 +13,7 @@ I believe this is potentially related to:
       > Vite issue thread that is still open and related to this https://github.com/vitejs/vite/issues/17499
       
       However, it's unclear whether we can do anything with Vite or Chrome to fix this -- as we are using dev mode, and nginx isn't relevant
-- I can avoid errors entirely if I throttle the network to "Fast 3G" (this is, however, very slow)
+- I can avoid errors entirely if I throttle the network to "Fast 4G" (this is, however, very slow)
   - after this completely, I can un-throttle the network, and all requests succeed
 - I can avoid errors by checking "Disable cache" -- this, however, defeats the point of http/2 and vite
 

diff --git a/README.md b/README.md
@@ -23,7 +23,7 @@ Related information:
 - rolldown-vite's "Full bundle mode" - https://discord.com/channels/804011606160703521/1416465954816135318/1416763408619143328
 - SETTINGS_MAX_CONCURRENT_STREAMS, https://issues.chromium.org/issues/41456843
   - Some have this set _very low_ (even [as low as 100](https://github.com/dotnet/runtime/issues/35088))
-  - [This hn comment](https://news.ycombinator.com/item?id=19722880) implies that the default is 1000 in Chrome
+  - [This hn comment](https://news.ycombinator.com/item?id=19722880) implies that the default is 1000 in Chrome -- however, the [vite issue](https://github.com/vitejs/vite/issues/17499) suggests 2000 simultaneous streams.
     This also suggests that a server must also support higher max concurrent streams.
 - General http/2: 
   - https://sites.google.com/site/mytechnicalcollection/networking/http2
diff --git a/README.md b/README.md
@@ -6,7 +6,7 @@ I believe this is potentially related to:
 - https://issues.chromium.org/issues/355006326 - the main issue report to Chromium about this use case (large ES module graph)
   - Errors we can receive
     - net::ERR_FAILED
-    - net::ERR_CONNECTION_RESET
+    - net::ERR_HTTP2_PROTOCOL_ERROR
   - Hope
     - https://issues.chromium.org/issues/355006326#comment27
       > Modifying nginx server config to use keepalive_requests 10000; and it solved the problem.

diff --git a/README.md b/README.md
@@ -11,6 +11,7 @@ I believe this is potentially related to:
     - https://issues.chromium.org/issues/355006326#comment27
       > Modifying nginx server config to use keepalive_requests 10000; and it solved the problem.
       > Vite issue thread that is still open and related to this https://github.com/vitejs/vite/issues/17499
+      
       However, it's unclear whether we can do anything with Vite or Chrome to fix this -- as we are using dev mode, and nginx isn't relevant
 - I can avoid errors entirely if I throttle the network to "Fast 3G" (this is, however, very slow)
   - after this completely, I can un-throttle the network, and all requests succeed

diff --git a/README.md b/README.md
@@ -11,6 +11,7 @@ I believe this is potentially related to:
     - https://issues.chromium.org/issues/355006326#comment27
       > Modifying nginx server config to use keepalive_requests 10000; and it solved the problem.
       > Vite issue thread that is still open and related to this https://github.com/vitejs/vite/issues/17499
+      However, it's unclear whether we can do anything with Vite or Chrome to fix this -- as we are using dev mode, and nginx isn't relevant
 - I can avoid errors entirely if I throttle the network to "Fast 3G" (this is, however, very slow)
   - after this completely, I can un-throttle the network, and all requests succeed
 - I can avoid errors by checking "Disable cache" -- this, however, defeats the point of http/2 and vite

diff --git a/README.md b/README.md
@@ -0,0 +1,27 @@
+Much of the benefit of vite + http/2 is the ability to rely on cached requests of http/2 -- as in, turning off "disable cache" in the network tools.
+
+However, when an app has to perform 10k network requests on boot, chrome and firefox error with: 
+
+I believe this is potentially related to:
+- https://issues.chromium.org/issues/355006326 - the main issue report to Chromium about this use case (large ES module graph)
+  - Errors we can receive
+    - net::ERR_FAILED
+    - net::ERR_CONNECTION_RESET
+  - Hope
+    - https://issues.chromium.org/issues/355006326#comment27
+      > Modifying nginx server config to use keepalive_requests 10000; and it solved the problem.
+      > Vite issue thread that is still open and related to this https://github.com/vitejs/vite/issues/17499
+- I can avoid errors entirely if I throttle the network to "Fast 3G" (this is, however, very slow)
+  - after this completely, I can un-throttle the network, and all requests succeed
+- I can avoid errors by checking "Disable cache" -- this, however, defeats the point of http/2 and vite
+
+
+
+Related information:
+- rolldown-vite's "Full bundle mode" - https://discord.com/channels/804011606160703521/1416465954816135318/1416763408619143328
+- SETTINGS_MAX_CONCURRENT_STREAMS, https://issues.chromium.org/issues/41456843
+  - Some have this set _very low_ (even [as low as 100](https://github.com/dotnet/runtime/issues/35088))
+  - [This hn comment](https://news.ycombinator.com/item?id=19722880) implies that the default is 1000 in Chrome
+    This also suggests that a server must also support higher max concurrent streams.
+- General http/2: 
+  - https://sites.google.com/site/mytechnicalcollection/networking/http2
No results found