From Discord: AWS Lambda environment fail with `.toWebHandler` about effect HOT 3 OPEN

when using SST Ion and calling HttpApp.toWebHandler the following error pops
Cannot read properties of undefined (reading 'addEventListener')
It points to request.signal.addEventListener("abort", ...)
the issue is that in aws lambdas the fetch API spec is not complete meaning that the Request is missing AbortController api support, the kind that would give it the .signal property.
Supposedly aws lambda support it in their nodejs 18 lambdas
but according to everyone else besides aws thats not true and you must add /* global fetch */ to the start of the file, but even then it seems that it's not enough and it does not make AbortController and AbortSignal available
There is a suggested polyfill but it won't help us because the the Request is coming straight from the lambda

from effect.

Well, calling it a platform bug is quite a stretch given it's AWS that is not spec-compliant. BTW make sure comments are not removed in the build pipeline, otherwise /* global fetch */ has no effect

from effect.

@mikearnaldi Ah, I am not the one impacted lol
I think it's a bug because it breaks in /platform, not /platform-node or something.. In general Request is not a platform-agnostic concept. node can't produce a server that speaks in Request and Response for example. It only knows IncomingMessage and OutgoingMessage which also have different semantics (for the node-native http and https they inverse at the boundaries, you send OutgoingMessage and receive it as an IncomingMessage, send back an OutgoingMessage and it arrives as an IncomingMessage), It can be 'fixed' (mitigated) with a simple check for the existence of the signal.
Not fixing this means that even if we were to release a theoretical /platform-aws, it'll be inoperable unless it ships it's own AwsHttpApp.toWebHandler

from effect.