Support scoped CSS in the same file
This is kinda vague but I'd like to have a built-in option to write CSS that: * Exists in the same file as my components * Is scoped * Has auto generated class names, like CSS Modules * Extracted via the same pipeline as CSS Modules * Could potentially use Sass (since we already support it) * Fully static Basically I want "CSS Modules" but without the "Modules" part. Just put it in the same file if that's the only place I use it anyway. https://github.com/4Catalyzer/astroturf looks related. cc @jquense @markdalgleish
Posted by gaearon on Oct 2, 2018, 2:50 AM
Tags
Related issues
- Add 65536 size support for maps
- TypeScript 7.1 Iteration Plan
- nvim-treeconfig: upstream nvim-treesitter
- Add the "action" and "method" attributes to <button>
- [FEATURE] Support multiple Connector accounts (same connector, different accounts) in Claude and Claude Code on the web (claude.ai/code)
- > We were imposed GitHub for so many exercises!
Raise real-world problems, find people facing the same issue, and discuss solutions.4,000 issues0 comments
support (Software)
Add 65536 size support for maps
TypeScript 7.1 Iteration Plan
nvim-treeconfig: upstream nvim-treesitter
Add the "action" and "method" attributes to <button>
[FEATURE] Support multiple Connector accounts (same connector, different accounts) in Claude and Claude Code on the web (claude.ai/code)
> We were imposed GitHub for so many exercises!
Add support for Visual Studio 2026 Integration
Support for Helm v4
Support scoped CSS in the same file
This is kinda vague but I'd like to have a built-in option to write CSS that: * Exists in the same file as my components * Is scoped * Has auto generated class names, like CSS Modules * Extracted via the same pipeline as CSS Modules * Could potentially use Sass (since we already support it) * Fully static Basically I want "CSS Modules" but without the "Modules" part. Just put it in the same file if that's the only place I use it anyway. https://github.com/4Catalyzer/astroturf looks related. cc @jquense @markdalgleish
Comments (0)
No comments yet. Start the discussion.