Feature request: reduce npm_modules size

[saragerion]

Bug description

The current bundle size of the Logger library is unnecessarily big. This has an impact on the performance of the Lambda functions (cold starts included).

Expected Behavior

The node_modules folder has a reasonable size.

Current Behavior

The node_modules folder is 139M.

Possible Solution

One of the biggest reasons is the lodash library that is currently a prod dependency, which is unnecessary.
It would also be good to double check whether we publish the NPM packages installing only the prod dependencies and not the dev dependencies.

Steps to Reproduce

Install the library in your local env, and check the node_modules folder size:

du -sh *
139M	node_modules
436K	package-lock.json
4.0K	package.json

Environment

• Powertools version used: latest
• Packaging format (Layers, npm): NPM
• AWS Lambda function runtime: all
• Debugging logs: N/A

Related issues, RFCs

N/A

[saragerion]

Thanks @michaelbrewer for the heads-up!

[michaelbrewer]

of coz we should see what size the packaged lambda is and how small we can make it.

[dreamorosi]

Good point, we initially removed the whole lodash in favor of smaller packages as mentioned here, but somehow it got reintroduced, I think around the time when we had multiple eslint configs.

[github-actions]

⚠️ COMMENT VISIBILITY WARNING ⚠️

Comments on closed issues are hard for our team to see.
If you need more assistance, please either tag a team member or open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.

[michaelbrewer]

@saragerion there is also a lot of test resources in "commons" that we already have in shared. About 208k worth.