import CSS in Card component
#7
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
thescientist13
force-pushed
the
import-css
branch
from
e224226
to
1323d06
Compare
thescientist13
force-pushed
the
import-css
branch
from
c567962
to
b0fe718
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Wanted to test out / demonstrate being able to
importCSS into a web component for inlining. Goal would be to have Greenwood align around the standard soon.TODO
import.meta.urlsupport - custom imports bundling breaks when used in API routes and SSR pages ProjectEvergreen/greenwood#1151greenwoodResourceLoadersupport for API routes (and SSR pages?)assetvschunk?)invalid URL) ProjectEvergreen/greenwood#1161node:specifiers? Or I think we were getting relative paths for specifiers?