-
Notifications
You must be signed in to change notification settings - Fork 162
Closed
Labels
confirmedThe scope is clear, ready for implementationThe scope is clear, ready for implementationinternalPRs 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.)loggerThis item relates to the Logger UtilityThis item relates to the Logger Utility
Description
Summary
The package.json
file of each package published on npm has an homepage
field that will be used on npmjs.com
to link back to the docs/repo of the module. Currently the link for the Logger utility returns 404 as it uses the old package name (logging
vs logger
). This should be fixed.
Why is this needed?
So that customers who land on the npm page of the utility can link back to the repo.
Which area does this relate to?
Logger
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
confirmedThe scope is clear, ready for implementationThe scope is clear, ready for implementationinternalPRs 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.)loggerThis item relates to the Logger UtilityThis item relates to the Logger Utility