Replies: 1 comment
-
I think we probably have you covered, but it's still in an early state.
In webpack you usually don't "generate" modules, but instead write or generate imports that lead to the creating of a module.
This sounds like you can create a JS module that wraps a css module.
Webpack allows to configure the css support via rules.
The current experimental css modules implementation in webpack does mangle class names. Removing unused rules is planned but not yet implemented. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hello webpack team.
I am one of the developers of a library named Stylable, it's a CSS pre-processor which involves a deep integration with
webpack
andmini-css-extract-plugin
.Currently part of our integration feels a bit hacky because some of the APIs we required are not documented and so we learned from reading the code.
We saw the initial work around Native CSS support and we think this will be a great opportunity to simplify our integration and use official API's
Due to the complexity of our integration, we'd like to propose a few APIs we'll be needing from the upcoming built-in CSS integration:
CssModule
s from our pluginCSS modules
but with runtime functionality backed in, and having different export structure.st.css
file extension from the built-in webpack CSS process or somehow use the built-in integrations as a post-process for asset handling and chunkingI hope we can start a discussion around adding these APIs/features so we'll be able to continue maintaining a clean and efficient integration to webpack.
Thanks in advance.
Beta Was this translation helpful? Give feedback.
All reactions