-
-
Notifications
You must be signed in to change notification settings - Fork 186
fix: prefer classic readme if npm picks up a different filename #130
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
fix: prefer classic readme if npm picks up a different filename #130
Conversation
And is not the standard filenames
|
@jonathanyeong is attempting to deploy a commit to the danielroe Team on Vercel. A member of the Team first needs to authorize it. |
| return false | ||
| } | ||
|
|
||
| const filenames = [ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@danielroe if this approach makes sense, I can extract this out into a shared const since it's duplicated in fetchReadmeFromJsdelivr
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
danielroe
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
(made a few small tweaks - hope that was ok!)
thank you for this ❤️
|
Of course! Thank you for making the PR better! |
Fixes: #117
Why
When fetching from registry npmjs, the incorrect readme filename is returned:
Doing some digging it might be because biomejs stores all its readmes in a single folder. Someone had a similar issue here.
Changes made
Testing
Visiting preview link of biomejs shows english README by default (https://npmxdev-git-fork-jonathanyeong-jy-fix-incorrect-readme-poetry.vercel.app/@biomejs/biome)