Serverless-http timeouts on netlify functions local enviroment

[coelmay]

@kohki-shikata

From what my understand, the package serverless-http converts legacy express code to server-less code. Is this incorrect?

I have never used serverless-http so I can neither confirm nor deny this.

If you are wanting to make a RESTful API with Netlify functions, I suggest reading over following threads I recently posted in this topic

How should I configure Netlify Functions to act as a Rest API backend only?

Hi every one, I’m looking for separating the repository of the functions (backend) and the site (frontend). Therefore, there’s no site beside of the functions and Netlify tries to create a new one automatically. I’m planning to create a Rest API backend only with Netlify Functions. How should I configure Netlify Functions to achieve that? Note: I use TypeScript, and the built .netlify directory looks like this: .netlify/functions-serve/test

Support for creating RESTful APIs with Netlify Functions

Hey there! Love Netlify. Great service. There is nothing better than an opinionated tool with sensible defaults that removes the need for cumbersome configs. However! There is one sensible default that consistently causes me trouble: the way Netlify sets up API endpoints based on file names. It’s fine for a quick prototype, but even with prototypes I prefer to follow RESTful conventions for my APIs. So let’s say I have a simple CRUD app with some users, I want endpoints to create, fetch one, f…