-
Notifications
You must be signed in to change notification settings - Fork 337
Make size limit warning more prominent, don't preview when over limit #417
Comments
with regard to 2: The 1mb limit we calculate is not done in the same way that the runtime does it... Simulating this exactly is difficult. I think catching the error and returning our own error may be helpful when running up against the size limit, but halting on our calculated limit could break people who's workers are up against the limit and work today. |
Perhaps Cloudflare could increase the 1MB limit to 3MB to match StackPath. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
This issue has been automatically marked as stale because it has not had recent activity in the last 180 days. It will be closed if no further activity occurs in the next week. Please feel free to comment if you'd like it to remain open, and thank you for your contributions. |
This issue has been automatically closed because it has not had recent activity. You may re-open the issue if it is still relevant. |
The user report #393 included some unclear error messaging. The root of the problem was that the user's script exceeded the script size limit imposed by the Workers platform, however Wrangler could do a couple of things to improve the experience around this limit:
help
message with suggestions for reducing script size, such as disabling source maps, turning on minification, and enabling performance hints. (This may make the most sense for webpack projects only).The text was updated successfully, but these errors were encountered: