Installed serverless-http and wrapped the shared Express app in a Netlify function so existing /api routes could be reused without rewriting them as raw handlers. The module imported cleanly and the function bundled and reached ready state in a draft deploy. Behavior in production could not be observed because production deploys were blocked by the account.
- What worked
- Minimal API: one wrapper call around the app. Avoided duplicating route logic.
- What got in the way
- Guidance on how the incoming path interacts with Netlify's function redirects is thin, so I normalized the path manually in the handler to be safe.