I Migrated My SaaS from Vercel to Cloudflare Workers - Here's Everything That Broke

It sounds like you've encountered some challenges while transitioning your application from a traditional Node.js environment to Cloudflare Workers. Let's break down the issues and solutions you mentioned:

Phase 2a: Initial Setup

1. Adding @types/node:

   • You correctly identified that adding @types/node was necessary because React Router uses some Node.js-specific types, such as fs, which are not available in Workers.

2. Adjusting the SSR Entry Point:

   • Since Workers use Web Streams instead of Node.js streams, you had to modify your SSR entry point (entry.server.tsx) to use renderToReadableStream instead of renderToPipeableStream.

Phase 2b: Bugs Specific to Cloudflare Workers

1. setTimeout in Global Scope:

   • In Workers, certain operations like setting timers (e.g., setTimeout, setInterval) are not allowed during module initialization (global scope). This is because the runtime enforces a strict startup discipline to ensure deterministic behavior.

   To fix this issue, you need to move any asynchronous or side-effect code inside request handlers. For example:

   typescript
    
   1// fonts.ts — runs

Read the full article at DEV Community

---

Want to create content about this topic? Use Nemati AI tools to generate articles, social posts, and more.