Skip to content

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
Member

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.

2 participants