As ESL is going to migrate to pure CSS style distribution, as an ESL developer, I want to be able to have a build flow set up for CSS sources.
⚠️ The new flow should be currently available as addition to existin LESS flow
Pure CSS components (in terms of preprocessing with LESS) should be able to use CSS as a source file format.
The source file should be able to use @import instruction to split up source code, but the import instruction should be resolved during build step of component outputs.
❓ Consider the PostCSS import plugin or another similar tool
We are not gonna have any additional steps to processing
CSS Nesting (fully covered by current browserlist)
Please make sure all root-level CSS sources will create a separate CSS file in the resultoutput.
As ESL is going to migrate to pure CSS style distribution, as an ESL developer, I want to be able to have a build flow set up for CSS sources.
Pure CSS components (in terms of preprocessing with LESS) should be able to use CSS as a source file format.
The source file should be able to use
@importinstruction to split up source code, but theimportinstruction should be resolved during build step of component outputs.❓ Consider the PostCSS import plugin or another similar tool
We are not gonna have any additional steps to processing
CSS Nesting (fully covered by current browserlist)
Please make sure all root-level CSS sources will create a separate CSS file in the resultoutput.