Skip to content
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

Resolve broken relative logo sources on npmjs (relative → absolute) #9610

Merged
merged 1 commit into from Oct 19, 2022
Merged

Resolve broken relative logo sources on npmjs (relative → absolute) #9610

merged 1 commit into from Oct 19, 2022

Conversation

brandonmcconnell
Copy link
Contributor

@RobinMalfait Looks like that last PR caused a slight regression on npmjs where the logo is completely broken now, because it registers the source URLs as relative links instead of absolute links.

You can see that bug here: https://www.npmjs.com/package/tailwindcss

Before and after this PR (assuming this works 🤷🏻‍♂️… it should)

Before After
Light Screen Shot 2022-10-19 at 18 40 02 Screen Shot 2022-10-19 at 18 39 42
Dark Screen Shot 2022-10-19 at 18 40 02 Screen Shot 2022-10-19 at 18 39 21

Unfortunately, npmjs doesn't yet have a dark mode of their own, so even after corrected, the logo will be mostly invisible on their site unless a stroke or some other sort of style is added to the logo to add contrast between the white text and white background.

@RobinMalfait RobinMalfait merged commit 2faf86f into tailwindlabs:master Oct 19, 2022
@RobinMalfait
Copy link
Contributor

Hey! Thank you for your PR!
Much appreciated! 🙏

Very odd, we used relative URLs before as well 🤔

@brandonmcconnell
Copy link
Contributor Author

brandonmcconnell commented Oct 19, 2022

@RobinMalfait It appears the relative links work on npmjs for img elements but not source.

Probably worth opening a ticket on npmjs for this as well.

And… there

@brandonmcconnell
Copy link
Contributor Author

Btw it appears that npmjs has since fixed that issue, so the correct logo displays for both light and dark mode, at least AFAICT when checking locally

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants