-
Notifications
You must be signed in to change notification settings - Fork 10
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
CSS Modules ™️ plugin #1233
Labels
Milestone
Comments
thescientist13
added
Plugins
Greenwood Plugins
CLI
feature
New feature or request
v0.30.0
labels
May 18, 2024
thescientist13
moved this to 🔖 Ready
in [Greenwood] Phase 9 - Standards and Conventions
May 18, 2024
This was referenced May 18, 2024
Merged
4 tasks
This was
linked to
pull requests
Jun 22, 2024
Merged
36 tasks
1 task
thescientist13
moved this from 🔖 Ready
to 🏗 In progress
in [Greenwood] Phase 9 - Standards and Conventions
Oct 7, 2024
12 tasks
12 tasks
3 tasks
thescientist13
moved this from 🏗 In progress
to 👀 In review
in [Greenwood] Phase 9 - Standards and Conventions
Oct 9, 2024
github-project-automation
bot
moved this from 👀 In review
to ✅ Done
in [Greenwood] Phase 9 - Standards and Conventions
Oct 18, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Summary
The new Greenwood website is piloting a plugin for supporting a very basic implementation of CSS Modules ™️ optimized for providing a nice co-located CSS DX in particular for Light DOM Web Components used for static templating.
Like a footer, for example
Would strip out the
import
statement and add the CSS as a<style>
tag to the HTML page, including for SSR, leaving you with something like this in your final HTMLDetails
As CSS Modules are a spec and can get quite complex, this should definitely be marked as experimental and YMMV, but did want something nice to compliment a .css first authoring experience with minimal fuss / happy path only support. The below are probably a couple things we can handle for the PR
Discussions
And these are probably better left to putting into a discussion
prerendering
because things run in a Worker Thread? 🤔 )The text was updated successfully, but these errors were encountered: