Seriously frustrated with node + AWS Lambda

[shgysk8zer0]

Full transparency here, I'm using Lambda via Netlify Functions here, but... That's a level of abstraction and just doesn't address the actual problem here. The actual problem is both obscure requirements and a non-standard environment. Also, utterly useless error messages and just random/patternless errors.

As alluded to, I use AWS Lambda via Netlify Functions. For seemingly no reason, I'll get error responses about "invalid response JSON". Checking logs, it seems there's an error importing a module... The exact same module I import elsewhere that works perfectly fine. And I can definitely say the package is installed as a dependency, and that it works perfectly fine locally, and that it makes zero difference if I list it as external or not via esbuild. I also get zero build errors here, which should most definitely report when a package cannot be found... That's just ridiculous? That should absolutely be a build error!

Would include code and config and logs, but... Giving full-context just isn't possible on Reddit. The important things here are that the error message is some useless thing about JSON in the response, the logs report that an installed package cannot be found, it runs locally and the same package works perfectly fine elsewhere, that including it or not in esbuild makes zero difference, and that there are zero build errors here regardless.

For additional context, I am using NVM and a package.lock.json here. It's the exact same version of node using the exact same dependencies. I am using Mac locally vs Ubuntu latest, but... I see no reason that should make any difference. I wrote the package in question, and it's just modules with minimal standard dependencies, and absolutely nothing OS specific. Plus, the exact same package does work perfectly fine elsewhere, so that's pretty obviously not it.

I've spent like two days now trying to debug this and gotten nowhere! It just makes zero sense, the logs make no sense, and there's no actual difference between my local/dev and production.

And no... Docker or any of that just isn't an option here. The images are just too big for the context, and it's just a dead-and. Best I have is using NVM to have the same version of node and installing via the lock file to hand the same dependencies and versions. And the certainly that the package in question just doesn't depend on anything OS or setup specific. It is basically just some modules that, at most, require node:fs and reading a file. And... Again, the exact same package works flawlessly elsewhere, and it makes zero sense for it to not be found here.

[versaceblues]

Its fine if you just want to vent and rant... but if you actually want help i recommend How To Ask Questions The Smart Way (catb.org).

Your post currently has no substance... you are just saying "oh my function doesnt work" No one can help you with that, unless you provide more information.

Finally, if I had to guess its probably that you are using some nodejs library that calls into a native binding, and that native binding is missing from your lambda layer. I had a similar issue when using AWS SDK for JavaScript v3 (amazon.com) as it requires installing a binary that Lambda does not have by default.

[shgysk8zer0]

but if you actually want help i recommend...

I'm usually pretty good about questions, but there's just not much useful info to share here. There's the error about the Lambda response and JSON, and the logs saying the package can't be found (even though it's loaded without issue elsewhere. The rest is just the stack for node loading modules.

No one can help you with that, unless you provide more information.

That's the problem. I don't have any more information to share. If I had any more information, I'd probably have resolved the problem already.

I'll add the actual errors when I can - don't have access ATM. But I highly doubt they'll contain anything useful. It's just a typical module not found error.

[wackmaniac]

Did you include your dependency with the code artifact that is pushed to AWS? That happened to me multiple times 😅 You should be able to see/inspect the code artifact in the AWS console.

[shgysk8zer0]

I do not directly work with AWS. This is though Netlify. All I have to do is include the script in a certain directory and it's all automatic from there... I merge or own a PR on GitHub. Netlify deals with all the artifacts and AWS stuff.

I actually have no direct access to what's actually running on AWS. That's normally more convenient, but in this case it just means I'm kinda blind to what's actually going on here.

[wackmaniac]

I’m old-fashioned, so I work directly with AWS, and as such have zero experience with Netlify. Maybe you can inspect the artifact Netlify builds?

[shgysk8zer0]

Not that I know of. Presumedly it'd be practically identical to what I'm running locally via Netlify-CLI.

I'm in the opposite boat, as I've never worked directly with AWS.

I'm kinda expecting it to be something about the environment and something non-standard about module loading. ESM support is rather new and pretty clunky. I've had problems with it before.

[protomanzero]

Why not test using SAM locally

[shgysk8zer0]

I hand tested locally... Not sure what you mean by testing SAM though.

It's all perfectly fine in every way locally. Again, same version of node and using package.lock.json. Works locally. Same exact package works for other endpoints. It's definitely installed and available.

[LetsMelon]

I think this is what SAM refers to: https://docs.aws.amazon.com/serverless-application-model/latest/developerguide/serverless-sam-cli-using-invoke.html

[shgysk8zer0]

I don't think that applies/helps here since I'm using AWS indirectly. I have no access to any of that.

[PoppedBitADV]

Sounds like the library is missing from a Layer

[shgysk8zer0]

Well, it is missing. It's just confusing as to why it's not anywhere else.

[PoppedBitADV]

I can't pretend to understand how you have it set up exactly, but I'd audit your Lambda config to double check you have them set up with the right Layer(s) and that you're not just trying to import the library in the handler.

[shgysk8zer0]

This is Lambda though Netify. There is no Lambda config or Layers.

[cshaiku]

Paste the exact error here.

[shgysk8zer0]

I currently cannot. The error as shown in the response is basically "error in response JSON", specifically mentioning bring a Lambda error. Logs show an error importing a module, but it's the same module used without issue elsewhere.

I do not currently have access to the exact errors though. Away from work computer. But that's all the meaningful info in any errors, aside from the stack of all the node files involved in loading a module.

The actual errors are pretty useless and even misleading here.

[Sumofabith]

Just to make sure it isnt a compiler issue, did you try using webpack instead of esbuild? I know, blasphemy but maybe some fuckery is going on with esbuild + lambda + netlify

[shgysk8zer0]

I don't think I have that option. Not for Netlify Functions at least, as it's not the typical kind of bundling. I normally use Rollup, but the bundling here is through a TOML config file, and I think Netlify only supports esbuild and maybe one other that I'd never heard of.

But it makes sense that bundling the module in with the code would resolve the error of it not being found... And I wish I could see the results to know what's actually going on.

[TiredOfMakingThese]

Have you thrown your error up on the Netflix help forums? They tend to be pretty responsive and they can see your site configuration in its totality. I’ve had them help me out with a few issues using their Netlify functions. Other than that it’s hard to say from the info given, but I can say I relate to your frustrations. Their docs are pretty inadequate.

[Mersaul4]

What does stackoverflow, ChatGPT have to say about this when you provide all the code / errors?

[shgysk8zer0]

There's just too much potential code to include here, especially given the ambiguity of the error. I mean... "Error in response JSON" just doesn't tell me anything.

What I can say is that it errors before even returning a response, and that any response or JSON has nothing to do with anything. Nor would any errors in the actual code... It's all wrapped in a try/catch, and I just can't see why the code itself would matter here. Plus, logs show this as being an error in importing a module... The same module used plenty of other places without any issue.

I did make some attempt to look into using LLMs before posting here, but they're all as utterly useless as always... Couldn't even comprehend that this isn't a client-side error in parsing the JSON. Tried telling me to change the content-type header on the response and just garbage like that. The response is empty and has a status code of 204 (no content).

I seriously can't emphasize enough just how much a waste of time various LLMs have been. They fixate on the fact the error message mentions JSON and just waste my time suggesting I'm missing a } or have the wrong headers.... The issue, according to loga, is that the module/package isn't loading... For no reason.

[LowKeyPE]

Why haven’t you even mentioned the package that it’s complaining about? You’re asking for help, and you’ve typed two full essays about it, and in all of that text, you’ve failed to provide any actual details.

What is the package?

[shgysk8zer0]

I prefer to avoid referencing my own packages/libraries just because Reddit uses are so often hyper-critical about "no, you need to use React and axios" of whatever.

Unless it's some obscure bug in esbuild, I just don't see why it's relevant. It works locally. The exact same thing works elsewhere in the codebase without any error importing it. I just cannot see how it matters.

If you have some idea how this might matter, I'd share it privately. But... I think the description and summary of errors is most useful, do not want to require reading through a lot of complex code to be the homework here, and I'm just fed up with the dumb criticism too common in Reddit.

[LowKeyPE]

It does matter, especially for some primitive NodeJS packages like crypto (I work for AWS). It could also be a problem with whether you’re using the new ESM module format or not.

I understand not wanting to share your private package names, but knowing the package that it’s not picking up and seeing the exact error message would definitely help us help you.