-
-
Notifications
You must be signed in to change notification settings - Fork 6.3k
Scss compilation is broken when using css.loaderOptions.sass
in vue.config.js
#4630
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
Labels
Comments
I suspect this might be caused by mutating From /* config.module.rule('scss').oneOf('vue-modules').use('sass-loader') */
{
loader: 'sass-loader',
options: {
sourceMap: false,
sassOptions: {
includePaths: [
'./src/styles'
],
indentedSyntax: true
}
}
} When I change this to sassOptions: Object.assign(
+ {},
(loaderOptions.sass && loaderOptions.sass.sassOptions) || {},
{
indentedSyntax: true
}
) it compiles. |
haoqunjiang
added a commit
to haoqunjiang/vue-cli
that referenced
this issue
Sep 30, 2019
9 tasks
haoqunjiang
added a commit
that referenced
this issue
Sep 30, 2019
haoqunjiang
added a commit
to haoqunjiang/vue-cli
that referenced
this issue
Oct 9, 2019
…#4631) fixes vuejs#4630 (cherry picked from commit ebdb142)
haoqunjiang
added a commit
that referenced
this issue
Oct 10, 2019
* feat: support sass-loader v8 (cherry picked from commit af17a9b) * fix: fix sassOptions merging for scss syntax in sass-loader v8 (#4631) fixes #4630 (cherry picked from commit ebdb142) * fix: avoid accidentally overriding sass config with scss configs (#4637) (cherry picked from commit e63bf61) * chore: don't warn user for sass-loader version here
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Version
4.0.0-rc.4
Reproduction link
https://github.com/KubaJastrz/vue-cli-repro/tree/rc4/scss-bug
Environment info
Steps to reproduce
What is expected?
it works as described in documentation: https://next.cli.vuejs.org/guide/css.html#passing-options-to-pre-processor-loaders
What is actually happening?
The text was updated successfully, but these errors were encountered: