-
-
Notifications
You must be signed in to change notification settings - Fork 9.4k
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
Cannot parse scss files with default vue-cli webpack config. Unexpected character #3567
Comments
How does your extended webpack.config.js look like? |
I just coped an examples from docs. Tried all of them, and then changed the paths, if I received a "not found" error |
From the error above I can understand that the sass-loader was not applied at all. Try something like this: module.exports = (storybookBaseConfig, configType, defaultConfig) => {
defaultConfig.module.rules.push({
test: /\.scss$/,
use: [require.resolve('style-loader'), require.resolve('css-loader'), require.resolve('sass-loader')],
});
return defaultConfig;
}; also, make sure that all of the loaders are installed. |
Hi everyone! Seems like there hasn't been much going on in this issue lately. If there are still questions, comments, or bugs, please feel free to continue the discussion. Unfortunately, we don't have time to get to every issue. We are always open to contributions so please send us a pull request if you would like to help. Inactive issues will be closed after 30 days. Thanks! |
Hey there, it's me again! I am going close this issue to help our maintainers focus on the current development roadmap instead. If the issue mentioned is still a concern, please open a new ticket and mention this old one. Cheers and thanks for using Storybook! |
Hello
I cant get my styles work in storybook from default vue-cli webpack config.
I tried to make a custom webpack config, but it seems doesnt work for me: throws even more different errors
Webpack with default vue-cli config throws errors like:
I`m using:
full error log, if it helps:
The text was updated successfully, but these errors were encountered: