Make aws-sdk a peer dependency
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 79
- Forks
- 27
- PR merge metrics
- No merged PRs in 30d
Description
Currently I'm using dyno in an AWS Lambda, and when we package up our dependencies aws-sdk gets included, despite it not being needed because the lambda service itself has it included already. This bloats our package by 25M.
Anyone using this package will already likely be using aws-sdk anyway, so perhaps it would make more sense to make it a peer dependency.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no file or test; start by locating the package's dependency metadata and how dyno imports aws-sdk. Verify that aws-sdk is no longer bundled for Lambda consumers while existing DynamoDB client behavior and installation remain intact.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, javascript
- Domain
- backend, databases
- Issue type
- Refactor
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100