You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If a username doesn't exist in npm, the generated metadata should return a description that says something along the lines of:
Could not find {username} on npm.
Actual
Currently, if a username doesn't exist, the metadata description that is returned is:
{username} has 0 npm packages eligible for Tidelift funding. 💸
This is misleading.
Additional Info
The dynamic metadata logic generates the metadata description based off the results from the tidelife-me-up package. However, the tidelife-me-up package currently doesn't handle the case where the username doesn't exist. There is an open issue to fix this: JoshuaKGoldberg/tidelift-me-up#17.
So this issue is blocked until the open issue in the tidelife-me-up repo is fixed.
✨
The text was updated successfully, but these errors were encountered:
Bug Report Checklist
main
branch of the repository.Expected
This is a follow up issue from #842.
If a username doesn't exist in npm, the generated metadata should return a description that says something along the lines of:
Actual
Currently, if a username doesn't exist, the metadata description that is returned is:
This is misleading.
Additional Info
The dynamic metadata logic generates the metadata description based off the results from the tidelife-me-up package. However, the tidelife-me-up package currently doesn't handle the case where the username doesn't exist. There is an open issue to fix this: JoshuaKGoldberg/tidelift-me-up#17.
So this issue is blocked until the open issue in the tidelife-me-up repo is fixed.
✨
The text was updated successfully, but these errors were encountered: