-
-
Notifications
You must be signed in to change notification settings - Fork 427
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
With "modern" API, the importer
behaves strangely with nested imports
#1237
Comments
@adrienharnay sass doesn't know how to work with JSN files, so this behavior is logical, you need a custom resolver
It works, but only for
It's expected because
What do you mean? Just use:
|
Modification Proposal
I believe there are some quirks in the current
importer
implementation that limit possible use cases. One of these use cases is to import JSON files withsass
orembedded-sass
implementations.Expected Behavior / Situation
Here is a minimal reproduction with steps to understand the limitations and changes needed to make the importer work.
From the README:
// No need to pass
loadPaths, because modern API handle them itself
comment is not 100% right.restrictions: [/\.(((sa|sc|c)ss)|json)$/i],
, the JSON file won't be picked up by the webpack resolver and thus it won't load.sass-loader
load
function because it won't call our importer (?).I remain available to exchange on the topic, having spent a few hours browsing and debugging the code.
Please paste the results of
npx webpack-cli info
here, and mention other relevant informationThanks in advance!
The text was updated successfully, but these errors were encountered: