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
{{ message }}
This repository has been archived by the owner on Aug 3, 2023. It is now read-only.
The user report in #896 reveals an issue with using Workers Sites with large-scale static sites; the user had a project with over 60k assets in it. The asset manifest wrangler generates in order to optimize cache invalidation on the edge is included in the overall bundle size for a worker script, and so can blow up the 1MB limitation when applied to such a large scale project. We should look at ways to optimize the asset manifest to increase the capacity for larger projects like this.
The text was updated successfully, but these errors were encountered:
Any development in this subject? I'm having the same problem as reported in #896 we also have around 70k files. I even tried to reduce the number of files to 48k and then to 24k and still run into the same problem, so far the only website I was able to host with wrangler publish was one with 2k files
The user report in #896 reveals an issue with using Workers Sites with large-scale static sites; the user had a project with over 60k assets in it. The asset manifest wrangler generates in order to optimize cache invalidation on the edge is included in the overall bundle size for a worker script, and so can blow up the 1MB limitation when applied to such a large scale project. We should look at ways to optimize the asset manifest to increase the capacity for larger projects like this.
The text was updated successfully, but these errors were encountered: