Open Armour opened 6 years ago
Enable css-loader sourceMap option will cause FOUC.
No FOUC when sourceMap enabled for css-loader.
In webpack.config.base.babel.js:
webpack.config.base.babel.js
... // Use a list of loaders to load css files { test: /\.css$/, use: [ devMode ? 'style-loader' : MiniCssExtractPlugin.loader, { loader: 'css-loader', options: { sourceMap: !devMode, importLoaders: 1 } }, // TODO: enable sourceMap in devMode without FOUC { loader: 'postcss-loader', options: { sourceMap: true, plugins: () => [postcssImport, postcssPresetEnv, cssnano] } }, ], }, // Use a list of loaders to load scss files { test: /\.scss$/, use: [ devMode ? 'style-loader' : MiniCssExtractPlugin.loader, { loader: 'css-loader', options: { sourceMap: !devMode, importLoaders: 2 } }, // TODO: enable sourceMap in devMode without FOUC { loader: 'postcss-loader', options: { sourceMap: true, plugins: () => [postcssImport, postcssPresetEnv, cssnano] } }, { loader: 'sass-loader', options: { sourceMap: true } }, ], }, ...
simply change !devMode to true will cause the FOUC.
!devMode
true
SourceMap support in development.
Related: https://github.com/webpack-contrib/css-loader/issues/613 https://github.com/facebook/create-react-app/pull/3202
I'm submitting a
Current behavior
Enable css-loader sourceMap option will cause FOUC.
Expected behavior
No FOUC when sourceMap enabled for css-loader.
Minimal reproduction of the problem with instructions
In
webpack.config.base.babel.js
:simply change
!devMode
totrue
will cause the FOUC.What is the motivation / use case for changing the behavior?
SourceMap support in development.