How to serve react pages within the 200ms startup time limit?

wrangler deploy

wrangler deploy

now regularly gives me "Script startup exceeded CPU time limit." Using

lazy

lazy

lazy

lazy and

Suspense

Suspense

don't seem to help. The gzip size of the app is around 600kb. What are some strategies people use to serve react apps?

Harrison LoOP•6/28/23, 8:18 AM

Okay we can dynamically import the React component in fetch

justboereh•6/28/23, 8:46 PM

it’s probably better to use Pages instead of Workers for react apps.

Harrison LoOP•6/29/23, 6:42 AM

@justboereh Using worker to do SSR

justboereh•6/29/23, 11:34 AM

@harrisonlo I’m pretty sure SSR React will work in Pages, but i’m not 100% sure since I deployed Nuxt instead of React.

justboereh•6/29/23, 11:36 AM

Unless you’re building you’re own SSR (like you’re not using a meta framework like Next.js).

chrisb (@boscolo.co)•7/5/23, 10:25 PM

Are there any other tips for troubleshooting "Script startup exceeded CPU time limit."?
I have a small small script:
Total Upload: 388.83 KiB / gzip: 91.02 KiBTotal Upload: 388.83 KiB / gzip: 91.02 KiB
And it does almost no initialization at startup, but I cannot deploy it.

How to serve react pages within the 200ms startup time limit?

Similar Threads

Similar Threads

Similar Threads