-
Notifications
You must be signed in to change notification settings - Fork 168
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Problem using @Import rule to import a CSS which has nested @Import rules #9794
Comments
I noted while researching that you can have nested imports if the importer is located at the root level.
We can have the structure
with shared-imports.css
with view-imports.css
but we can not have an import in a sub directory so having for instance
where main-view.css
this will fail as it cant find the loaders. |
Seems that this is from the |
This issue is the same as reported for the extract-loader peerigon/extract-loader#48 |
Just noting that this issue is waiting for extract-loader issue to be fixed and documented for now. |
Will this be resolved by moving to Vite? |
Probably as we don't need the extract-loader with Vite. |
This was a problem only in webpack |
Having the following project structure:
If
view-styles.css
contains@Imports
like this:and import this file into
styles.css
, like this:The application starts, but frontend errors appears like this:
Simply by removing the imports from
view-styles.css
the theme styles are being applied and only the view-specific styles are missing (which are not imported). Also by importing the view-specific styles directly into thestyles.css
it works without a problem.Desired Behaviour:
To be able to use
@Import
rules in CSS files that have nested@Import
rules.Environment:
The text was updated successfully, but these errors were encountered: