lambda functions can't be placed in sub directories

This issue is a spin-off of #846

On Netlify, if you want to have the serverless function hello you can either have the file functions/hello.js or functions/hello/hello.js

Redwood currently only supports the first of those two options (functions/hello.js)

This issue is about adding support for the second way of doing it as well. Plus, possibly, functions/hello/index.js

All three options would result in a function available at http://localhost:8911/hello

Netlify’s docs for this are here https://docs.netlify.com/functions/build-with-javascript/

Potential steps brought over from the linked Issue

• Determine how many levels on nesting is supported on netlify, vercel, etc. Netlify: Only one level. Vercel: Unlimited
• Make the import code support nested subdirectories.
• Make the various parts that reference the “name” work with subdirectories.
• Write tests.

(Personally I don’t have a need for this right now, so anyone else; please feel free to pick this up if you want to)

[viperfx]

Would like to just add my use case here for this feature

With the redwood app I am working on, we integrate with different services. We are working on a Slack app, Intercom app, Zapier App etc.

We use the serverless functions to the do following functionality:

• Oauth redirect and callback URLs
• Incoming webhook support to integrate with platforms
• APIs we create according to the platform spec.

So the project right now sits at close to 20 functions, and we are not yet done with the integrations we want to develop.

For code organization, I have used the following naming scheme, to make things a bit more manageable. [platform]-[function].js

e.g. intercom-oauth-callback.js, slack-auth.js

Another use case is the use of libraries such as https://quirrel.dev/ - which will greatly benefit from folder support. As each “queue” is a serverless function.

[Tobbe]

Maybe not the best/fastest way as it added a layer, but it did make it organized and might be host-platform agnostic (works on Netlify and Vercel).

Having an Express app as a router on the top level (/feed in this case) is exactly what Netlify themselves use in their examples, so I think that’s a perfectly valid approach. To get that to work on Vercel I had to do some tricks with the vercel.json config files and the routing in there.

So if we choose this route (sorry 😛😁) we need to do this setup on Vercel as part of deployment.

next.js does some magic with their /pages/api folder. So it’s not impossible, just a bit of work 😃