-
-
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
build-storybook (v3) doesn't work anymore #1203
Comments
What loaders are you injecting? |
[{
test: /\.scss$/,
use: [{
loader: 'style-loader'
}, {
loader: 'css-loader',
options: {
importLoaders: 1
}
}, {
loader: 'postcss-loader',
options: {
plugins: () => [
autoprefixer(autoprefixerConfig)
]
}
}, {
loader: 'resolve-url-loader',
options: {
sourceMap: true,
keepQuery: true
}
}, {
loader: 'sass-loader',
options: {
sourceMap: true
}
}]
}, {
test: /\.svg$/,
use: [{
loader: 'svg-sprite-loader',
options: {
runtimeGenerator: path.join(cwd, 'tasks/helpers/svg-to-component.js'),
runtimeOptions: {
iconModule: path.join(cwd, paths.src.app, 'ui/components/icon/icon.js')
}
}
}]
}, {
test: /\.(eot|woff|ttf)$/,
loader: 'file-loader'
}] |
Node 8 is the |
It's possible got get working. Can you confirm it does work in node < 8 ? |
@ndelangen with node v7 all works. |
I'm not sure what to do, I'm not faced with this error on my machine, and I'm running Node 8.0.3. |
@dangreen try upgrading the |
@danielduan i'm already on latest version of sass-loader |
Do you have a repository we can use to reproduce the issue? |
Maybe related to this issue. |
I think we’re having the same issue as OP, here’s a repo to reproduce with: https://github.com/artsy/reaction-force. The build task appears to succeed (see deployment step), but no JS files are output. |
If this is still an issue on the latest versions, please reopen. |
In my configuration i inject some loaders into
module.rules
, it perfectly works withstart-storybook
.build-storybook
v2 also works perfectly: it compile and copy all assets into build dir.With v3: it doesn't copy assets anymore.
Also in browser i have this issue (node-sass? wtf??):
The text was updated successfully, but these errors were encountered: