Skip to content

Maintenance: homepage field in the package.json file returns 404 #1498

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
1 of 2 tasks
dreamorosi opened this issue Jun 13, 2023 · 1 comment · Fixed by #1495
Closed
1 of 2 tasks

Maintenance: homepage field in the package.json file returns 404 #1498

dreamorosi opened this issue Jun 13, 2023 · 1 comment · Fixed by #1495
Labels
confirmed The scope is clear, ready for implementation internal PRs that introduce changes in governance, tech debt and chores (linting setup, baseline, etc.) logger This item relates to the Logger Utility

Comments

@dreamorosi
Copy link
Contributor

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

Future readers

Please react with 👍 and your use case to help us understand customer demand.

@dreamorosi dreamorosi added triage This item has not been triaged by a maintainer, please wait internal PRs that introduce changes in governance, tech debt and chores (linting setup, baseline, etc.) labels Jun 13, 2023
@dreamorosi dreamorosi added confirmed The scope is clear, ready for implementation logger This item relates to the Logger Utility and removed triage This item has not been triaged by a maintainer, please wait labels Jun 13, 2023
@dreamorosi dreamorosi linked a pull request Jun 13, 2023 that will close this issue
9 tasks
@github-project-automation github-project-automation bot moved this from Working on it to Coming soon in AWS Lambda Powertools for TypeScript Jun 13, 2023
@github-actions
Copy link
Contributor

⚠️ 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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
confirmed The scope is clear, ready for implementation internal PRs that introduce changes in governance, tech debt and chores (linting setup, baseline, etc.) logger This item relates to the Logger Utility
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant