You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Including sass files while using sass-loader version 8+ throws error when compiling the app
ValidationError: Invalid options object. Sass Loader has been initialised using an options object that does not match the API schema. - options has an unknown property 'indentedSyntax'. These properties are valid: object { implementation?, sassOptions?, prependData?, sourceMap?, webpackImporter? } at validate
Reason is sass-loader introduced breaking change in 8.0 moving all sass options under sassOptions sub-key
Fix will be probably hard without introducing incompatibility with previous versions of sass-loader. Are you sure this option is actually necessary ? My understanding is both node-sass and dart-sass are able to switch between syntax based on file extension - indented for sass and non-indented for scss
Other problem I see is that in saber-config the build.loaderOptions.sass is used for both sass and scss configuration. It would be useful to have dedicated key just for scss
Steps to reproduce
What is expected?
What is actually happening?
Other relevant information
Result of running saber -v:
Browser version (optional):
Is Saber a global or local install?
Which package manager did you use for the install?
Does this issue occur when all plugins are disabled?
The text was updated successfully, but these errors were encountered:
Bug report
Including sass files while using
sass-loader
version 8+ throws error when compiling the appReason is
sass-loader
introduced breaking change in 8.0 moving all sass options undersassOptions
sub-keyProblematic file is config-css.js
Fix will be probably hard without introducing incompatibility with previous versions of
sass-loader
. Are you sure this option is actually necessary ? My understanding is bothnode-sass
anddart-sass
are able to switch between syntax based on file extension - indented forsass
and non-indented forscss
Other problem I see is that in
saber-config
thebuild.loaderOptions.sass
is used for bothsass
andscss
configuration. It would be useful to have dedicated key just forscss
Steps to reproduce
What is expected?
What is actually happening?
Other relevant information
saber -v
:The text was updated successfully, but these errors were encountered: