A bit of feedback and a question as I look at porting an app backend rom an old and now defunct version of Zeit/Vercel.
So my overall impression is that functions provide a very nice facade to AWS Lamda functions. But, while you hide the details it’s a pretty leaky abstraction. At least as far as the docs are concerned. It would be great if you removed any assumptions about prerequisite AWS knowledge. There are several points where you mention AWS.
In one place I read a mention of calling functions directly, Possibly not as a HTTP endpoint but that seems unlikely and I never saw any details. It seemed to be a ref to old functionality.
Another concept that you could explain is Bundled / Unbundled. I think I have it figured from several reads. But Unbundled get bundled by the deployment so not sure.
Hope that helps you improve the docs.
My question is about file sharing in the source without any pre deploy build steps. The options appear to be:
- single function file per endpoint
- a directory with several files, including the exported endpoint function
- so called ‘unbundled’ - either of the above but with modules imported via node node_modules mechanism (hmm, what about ESM modules :))
But what about files we want to share that are our own source and not imported modules? Can we stick them in the functions folder, import them and expect them to be deployed for us? Do we put them in a specfic folder, access in another function’s folder. Or do we need to put in node module , with or without full packaging?
Or is this why yo utalk about “bundled”? you expect a pre deploy process to bundle (in the usual sense) everything into one file / folder?
I’ll explore but it would be best if this was documented as I don’t want to rely on undocumented behaviour that could change.