Better classnames for development mode
See original GitHub issueAt the moment the classnames are mangled into base64 hash or something:
e.g.
class="sc-jAaTju kAxljF sc-bdVaJa iHZvIS"
It would be nice to somehow allow rebass to pass the folder_file_componentName:base64 for development mode. The same as how css-loader does it.
Issue Analytics
- State:
- Created 5 years ago
- Comments:12 (1 by maintainers)
Top Results From Across the Web
More meaningful/semantic class names during development ...
Is it possible to use class names similar to styled components names. Maybe with random prefix like: const Wrapper = styled.div` ...
Read more >Material UI class names in production do not resolve correctly
Class names generated by makeStyles in production break functionalty that apparently works correctly in development mode.
Read more >6 Tips for Tailwind CSS Development (with resources!)
Let's start with something that is highly recommended for every project: using clsx for joining class names. Clsx is a simple JavaScript utility ......
Read more >How to configure CSS Modules for webpack - LogRocket Blog
This is achieved by creating a unique class name for CSS selectors, ... mode: "development", devServer: { static: path.resolve(__dirname, ".
Read more >Element.getElementsByClassName() - Web APIs | MDN
A string containing one or more class names to match on, separated by whitespace ... Note: In quirks mode, the class names are...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@johnmcdowall
babel-plugin-styled-components
seems to work forstyled-components
but not rebass components. Is their anything for rebass as well?@baddox I believe your code demonstrates what is the desired output and what is the immediate issue. Well done!
Seems like this has been mentioned to the emotion team as well:
https://github.com/emotion-js/emotion/issues/756
The issue above suggests a way to create a solid headstart on where a PR could be made to make sure that the
autoLabel
feature can work for rebass components. Due to the nature of abstracting components, it may be quite the undertaking.Maybe even a fork of
babel-plugin-emotion
tobabel-plugin-rebass
? I’m unsure. I’m still learning this system. I’m here because wanted to see how good code is maintained, and perhaps I could help@jxnblk and anyone else; please correct me if I’m wrong about anything.