Richard Simpson

I would also encourage closing this, but with the caveat that this should be documented to also avoid any questions in the future.

> I'll ask again: What's the issue with using cloudfront using ECR as an origin? Spinning up a non-trivial piece of infrastructure to use 5% of its functionality is not...

> There's nothing to spin-up, cloudfront is a hosted service. And one of its main features is exactly what's being asked here. If you want caching and geo-distribution sure. But...

This is probably, possibly related to https://github.com/open-telemetry/opentelemetry-lambda/issues/263

I don't see why this wouldn't be possible. We might have to tweak how logs are written so we don't write to ProgramData, but otherwise this seems like a fine...

This _should_ be a relatively easy matter of setting `exports` correctly. I think I could help contribute this, only caveat might be bundling/types.

In theory removing `module`, `esnext`, and `browser`, and doing the below would resolve it, though I think there's still a posibility of ambiguity due to some tools requiring explicit extensions...

> So it's not as simple as fixing a few exports, you also need to ensure valid ESM output (.js file endings) and for that you need to roll up...

This would be an awesome way to approach this. It looks like DD's work is open source too, might be able to reference their work or collab: https://github.com/DataDog/dd-trace-js/blob/master/packages/datadog-esbuild/index.js

> [AWS Snapstart](https://docs.aws.amazon.com/lambda/latest/dg/snapstart.html) would seem to remove this as a problem. Benchmarking I've done shows cold starts are largely removed as a factor when using SnapStart I believe even if/when...