fsharp-starter-kit
fsharp-starter-kit copied to clipboard
Published
20 hours ago •
kriasoft
kriasoft
postcss-loader issues
Two users reported me the following error:
[09:50:26] Finished 'appsettings' after 3ms
WebpackOptionsValidationError: Invalid configuration object. Webpack has been initialised using a configuration object that does not match the API schema.
- configuration has an unknown property 'postcss'. These properties are valid:
object { amd?, bail?, cache?, context?, dependencies?, devServer?, devtool?, entry, externals?, loader?, module?, name?, node?, output?, plugins?, profile?, recordsInputPath?, recordsOutputPath?, recordsPath?, resolve?, resolveLoader?, stats?, target?, watch?, watchOptions? }
For typos: please correct them.
For loader options: webpack 2 no longer allows custom properties in configuration.
Loaders should be updated to allow passing options via loader options in module.rules.
Until loaders are updated one can use the LoaderOptionsPlugin to pass these options to the loader:
plugins: {
new webpack.LoaderOptionsPlugin({
// test: /\.xxx$/, // may apply this only for some modules
options: {
postcss: ...
}
})
}
at webpack
It seems that the latest webpack 2 beta is not compatible with the stable postcss-loader. aspnet-starter-kit have already fixed that issue. Could you please merge that commit?
