expo-api-routes

Create serverless API routes in Expo Router by adding a `+api.ts` file to your project. This convention allows you to handle HTTP methods, parse requests, and execute backend logic directly within your app structure.

No, you cannot use Node.js APIs in Expo API routes deployed to EAS Hosting. Because the deployment environment uses Cloudflare Workers, you must use standard Web APIs and cloud databases instead of Node-specific modules.

Securely manage environment variables for Expo API routes by configuring secrets in your deployment settings. This allows your serverless functions to access API keys and sensitive credentials without exposing them to the client side.

Using the `+api.ts` convention in Expo, you can implement backend logic like data validation, database operations, handling Stripe webhooks, user authentication, and proxying external APIs securely.

Yes, Expo Router supports dynamic routes and CORS for serverless functions. You can handle dynamic route parameters, configure CORS headers, and manage error handling within your `+api.ts` files.

The main limitation of using Cloudflare Workers for Expo API routes is the runtime environment. You cannot rely on Node.js built-in modules or local file system access, meaning you must use Web APIs and cloud-based databases.