Skip to content

fix: Use @types/aws-lambda instead of aws-lambda#3

Merged
NishuGoel merged 1 commit intoNishuGoel:mainfrom
mikkopiu:main
May 31, 2024
Merged

fix: Use @types/aws-lambda instead of aws-lambda#3
NishuGoel merged 1 commit intoNishuGoel:mainfrom
mikkopiu:main

Conversation

@mikkopiu
Copy link
Copy Markdown
Contributor

The packages are often confused but aws-lambda is actually a mostly-unrelated CLI tool which happens to bring in aws-sdk as a dependency (which this package doesn't otherwise need) whereas @types/aws-lambda is the Lambda types for things like events -- as used here.

Being explicit with import type when using aws-lambda ensures the correct package is used.

This change means the users of this package won't unnecessarily get aws-sdk (v2) installed alongside it.

The packages are often confused but `aws-lambda` is actually a mostly-unrelated CLI tool which happens to bring in `aws-sdk` as a dependency (which this package doesn't otherwise need) whereas `@types/aws-lambda` is just the Lambda types for things like events -- as used here.
@NishuGoel NishuGoel merged commit 4feb31b into NishuGoel:main May 31, 2024
@NishuGoel
Copy link
Copy Markdown
Owner

Thanks for this improvement @mikkopiu 💪

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants