Package individually doesn't optimise package size

Hello! This plugin works great, thank you for sharing it!

I wanted to test, if it works for our use case and I’ve found some problems.

We are using Yarn as package manager with workspaces enabled. In the stack that I’m testing, we are having 4 lambda functions. When I was using Webpack, each lambda had different package size, where the smallest was 1.5 MB and the biggest was 3 MB.

However when I was experimenting with this plugin, it looks like, package individually option doesn’t work. The package size is 6 MB for each lambda, which equals the size of package, that is created when package individually is disabled.

I was looking a little bit into the source code and it looks like, package individually option is handled by this plugin. Is this expected behaviour of esbuild? This is the config that I’m using:

custom:
  esbuild:
    packager: yarn
    bundle: true
    minify: true
    sourcemap: true
    keepNames: true

Versions: “serverless-esbuild”: “1.5.1” “serverless”: “2.3.0” Node.js v12.19.1

[PatrykMilewski]

I just tested it and it works great! Thank you @olup for fixing this issue!

[floydspace]

🎉 This issue has been resolved in version 1.8.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀