The build process is currently all or nothing for user settings, you can only bundle, you can’t “compile” each module into a specific stylesheet.
What is the expected behaviour?
With HTTP2, it makes sense to break up CSS into smaller files e.g. user settings submodules. We should anticipate this need.
What is the current behaviour?
We’re currently bundling everything into the ReadiumCSS-after.css stylesheet.
What is the motivation / use case for changing the behaviour?
Implementers might prefer to append/remove styles for user settings on user interaction.
Do you know which CSS modules (stylesheets) are impacted?
This is limited to user settings.
Other information (e.g. related issues, suggestions how to fix, links for us to have context)
That’s probably for v1, and not the beta.
I would vastly prefer implementing that using good old gulp/grunt given how tedious Webpack or some others are at working with CSS – creates an awful lots of issues for people not familiar with the latter bunch.
I'm submitting a feature request
Short description of the issue/suggestion:
The build process is currently all or nothing for user settings, you can only bundle, you can’t “compile” each module into a specific stylesheet.
What is the expected behaviour?
With HTTP2, it makes sense to break up CSS into smaller files e.g. user settings submodules. We should anticipate this need.
What is the current behaviour?
We’re currently bundling everything into the
ReadiumCSS-after.cssstylesheet.What is the motivation / use case for changing the behaviour?
Implementers might prefer to append/remove styles for user settings on user interaction.
Do you know which CSS modules (stylesheets) are impacted?
This is limited to user settings.
Other information (e.g. related issues, suggestions how to fix, links for us to have context)