search

aws / aws-lambda-base-images

Apache License 2.0
649 stars 107 forks source link

Node v18 Released #47

Closed chenrui333 closed 1 year ago

chenrui333 commented 2 years ago

Even though we are still waiting for node v16 base image, this is the issue tracker for node v18 base image

https://nodejs.org/en/blog/announcements/v18-release-announce/

paul-uz commented 1 year ago

How is that single JS then referenced in my actual function? Does esbuild handle that as well?

simlu commented 1 year ago

I guess this thread has now completely derailed, so I'm going to unsubscribe. However, relevant to the recent discussion, please take a look at "@vercel/ncc". We've been using it for hundreds of production lambda functions (and billions of executions) to bring down cold start / package size. It might take a bit of tinkering to get to work (depending on your dependencies - really helps if you have tests you can run against the compiled code), but the impact on cold start times is fantastic.

paul-uz commented 1 year ago

@ffxsam I gave esbuild a quick test, and it seems to be working, mostly. I don't think tree-shaking is working by default though, as an included package I wrote is having all its functions bundled, not just the one being used in my main file.

koshic commented 1 year ago

@paul-uz plz read https://esbuild.github.io/api/#tree-shaking and stop posting irrelevant comments here )