feat(clerk-js): Add support for loading UI styles as first CSS stylesheet - #4291
Conversation
|
dstaley
changed the title
| import type { ClerkHostRouter } from '@clerk/shared/router'; | ||
| import { ClerkHostRouterContext } from '@clerk/shared/router'; | ||
| import type { ClerkOptions, LoadedClerk } from '@clerk/types'; | ||
| //@ts-ignore - This is treated as a string export by Webpack |
There was a problem hiding this comment.
[question] Would it be better to use@ts-expect-error so in the case this is no longer an issue in the future the @ts-ignore doesn't just stick around forever?
There was a problem hiding this comment.
Deleted this file as it wasn't being included anyway, only the src/ directory was.
| rootElement.setAttribute('id', 'clerk-components'); | ||
| document.body.appendChild(rootElement); | ||
|
|
||
| const stylesheet = document.createElement('link'); |
There was a problem hiding this comment.
@brkalow I'm assuming since we're within an instance where the rootElement didn't exist that we can safely assume the stylesheet isn't part of the DOM. Do you think we need to add some attributes to the link element and check for those?
There was a problem hiding this comment.
@dstaley It should be safe, but in this case I feel like this is a place where we it would be a good idea to add the check.
4 participants
Description
This PR adds support for inserting the new UI stylesheet as the first stylesheet in the document. This is to allow user styles to take precedence over our own. For example:
If the UI stylesheet appears after the app stylesheet in the DOM,
cl-buttonwill overridehiddengiven they have the same specificity. By prepending our stylesheet, we allow our users' styles to take precedence.To support this, I had to remove Webpack's experimental support for CSS which doesn't currently support emitting the URL of the stylesheet; it always wants to append it to the DOM.
Checklist
npm testruns as expected.npm run buildruns as expected.Type of change