-
Notifications
You must be signed in to change notification settings - Fork 161
Closed
Labels
completedThis item is complete and has been merged/shippedThis item is complete and has been merged/shippedinternalPRs that introduce changes in governance, tech debt and chores (linting setup, baseline, etc.)PRs that introduce changes in governance, tech debt and chores (linting setup, baseline, etc.)parametersThis item relates to the Parameters UtilityThis item relates to the Parameters Utility
Milestone
Description
Summary
When we publish a utility to npmjs.com, the README file of the utility is used as cover page for people visiting the page of the package. Currently the page is empty and this is likely due to the README file not being included in the tarball published to npm.
Why is this needed?
We need to fix this so that users landing on the page for the first time will know what the utility is about and maybe try it.
Which area does this relate to?
Parameters
Solution
No response
Acknowledgment
- This request meets Powertools for AWS Lambda (TypeScript) Tenets
- Should this be considered in other Powertools for AWS Lambda languages? i.e. Python, Java, and .NET
Future readers
Please react with 👍 and your use case to help us understand customer demand.
Metadata
Metadata
Assignees
Labels
completedThis item is complete and has been merged/shippedThis item is complete and has been merged/shippedinternalPRs that introduce changes in governance, tech debt and chores (linting setup, baseline, etc.)PRs that introduce changes in governance, tech debt and chores (linting setup, baseline, etc.)parametersThis item relates to the Parameters UtilityThis item relates to the Parameters Utility
Type
Projects
Status
Shipped