-
-
Notifications
You must be signed in to change notification settings - Fork 432
Deep import from scoped npm package breaks webpack resolve.aliases #463
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
Comments
@gizm0bill thanks in near future i investigate this |
@gizm0bill using
|
@evilebottnawi aliases in webpack can be setup in various ways, and should resolve deep from the aliased path: https://webpack.github.io/docs/configuration.html#resolve-alias |
@gizm0bill seems alias don't work now for all packages #410, it is related to this problem, right? |
Might be, need to check.. |
@solidevolution aliases works only with modules: |
@evilebottnawi we don't use sass/scss and experimental versions ;) |
@solidevolution |
You can try this fix. It makes my aliases work again. Maybe it will help to you too. |
Hi, I think I have the same issue. I'm trying to @import files from a subdirectory. Importing files from the same directory works like a charm, but from a subdirectory I get the same error as the initial post. My folder structure
in main.scss in webpack.config.js module: {
rules: removeEmpty([
{
test: /\.scss$/,
loader: extractCSS.extract([
{
loader: `style-loader`,
},
{
loader: `css-loader`,
},
{
loader: `postcss-loader`,
},
{
loader: `sass-loader`,
},
]),
},
])
} |
@katiasmet {
loader: "sass-loader",
options: {
includePaths: ['src/_scss']
}
} If this don't help, please create minimum reproducible test repo, thanks! |
Ok that worked :D thanks a lot! |
Closing due to inactivity. Please test with latest version and feel free to reopen if still regressions. Thanks! |
The text was updated successfully, but these errors were encountered: