remove `chakra-*` class names from prod builds
See original GitHub issueI’ve noticed that in Prod builds chakra-
classes are being added, but they are not being used. So why would we need them especially in Prod builds?
I think having an option to remove them make sense, i feel now that cluttering html classes with this, especially considering they are not being used and just there.
Issue Analytics
- State:
- Created 3 years ago
- Comments:11 (4 by maintainers)
Top Results From Across the Web
Advanced techniques in Chakra UI - LogRocket Blog
Dive deeper into the functionality of Chakra UI with these tips and tricks explained with an example tutorial.
Read more >How to override Chakra UI (or Emotion CSS-in-JS) styling with ...
Any CSS classnames I write will not override Chakra UI component styles, even when passing them directly as className, ...
Read more >Upgrading to v1 - Chakra UI
Install the framer-motion package. We use this to manage animations and transitions within components. · Remove the emotion-theming package. · Rename the @emotion ......
Read more >chakra-ui/package.json - UNPKG
1, {. 2, "name": "chakra-ui",. 3, "version": "0.3.9",. 4, "description": "Responsive and accessible React UI components built with React and Emotion",.
Read more >emotion/babel-plugin
Contextual Class Names, ✓, Generated class names include the name of the ... default in @emotion/babel-plugin but they will be removed in production...
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
Yes, this is fairly traditional css behavior. Like most other things, we can’t predict what users will or won’t need to target or how they do the targeting, but this at least gives them the option to do so.
Gonna close this as a duplicate of #2229. You should be able to achieve this in your own build process using
babel-plugin-react-remove-classname
or something similar.@with-heart Maybe this should be a issue to think about. There should be an easy integrated way in chakra to replace the “chakra” prefix with some other string.