npm install --save-dev css-loader
The css-loader
interprets @import
and url()
like import/require()
and will resolve them.
Good loaders for requiring your assets are the file-loader and the url-loader which you should specify in your config (see below).
file.js
import css from 'file.css';
webpack.config.js
module.exports = {
module: {
rules: [
{
test: /\.css$/,
use: [ 'style-loader', 'css-loader' ]
}
]
}
}
You can also use the css-loader results directly as string, such as in Angular's component style.
webpack.config.js
{
test: /\.css$/,
use: [
'to-string-loader',
'css-loader'
]
}
or
const css = require('./test.css').toString();
console.log(css); // {String}
If there are SourceMaps, they will also be included in the result string.
If, for one reason or another, you need to extract CSS as a plain string resource (i.e. not wrapped in a JS module) you might want to check out the extract-loader. It's useful when you, for instance, need to post process the CSS as a string.
webpack.config.js
{
test: /\.css$/,
use: [
'handlebars-loader', // handlebars loader expects raw resource string
'extract-loader',
'css-loader'
]
}
Name | Type | Default | Description |
---|---|---|---|
url |
{Boolean} |
true |
Enable/Disable url() handling |
import |
{Boolean} |
true |
Enable/Disable @import handling |
sourceMap |
{Boolean} |
false |
Enable/Disable Sourcemaps |
importLoaders |
{Number} |
0 |
Number of loaders applied before CSS loader |
To disable url()
resolving by css-loader
set the option to false
.
To be compatible with existing css files (if not in CSS Module mode).
url(image.png) => require('./image.png')
url(~module/image.png) => require('module/image.png')
To disable @import
resolving by css-loader
set the option to false
@import url('https://fonts.googleapis.com/css?family=Roboto');
⚠️ Use with caution, since this disables resolving for all@import
s, including css modulescomposes: xxx from 'path/to/file.css'
feature.
To include source maps set the sourceMap
option.
I. e. the extract-text-webpack-plugin can handle them.
They are not enabled by default because they expose a runtime overhead and increase in bundle size (JS source maps do not). In addition to that relative paths are buggy and you need to use an absolute public path which include the server URL.
webpack.config.js
{
loader: 'css-loader',
options: {
sourceMap: true
}
}
The query parameter importLoaders
allows to configure how many loaders before css-loader
should be applied to @import
ed resources.
webpack.config.js
{
test: /\.css$/,
use: [
'style-loader',
{
loader: 'css-loader',
options: {
importLoaders: 2 // 0 => no loaders (default); 1 => postcss-loader; 2 => postcss-loader, sass-loader
}
},
'postcss-loader',
'sass-loader'
]
}
This may change in the future, when the module system (i. e. webpack) supports loader matching by origin.
The following webpack.config.js
can load CSS files, embed small PNG/JPG/GIF/SVG images as well as fonts as Data URLs and copy larger files to the output directory.
webpack.config.js
module.exports = {
module: {
rules: [
{
test: /\.css$/,
use: [ 'style-loader', 'css-loader' ]
},
{
test: /\.(png|jpg|gif|svg|eot|ttf|woff|woff2)$/,
loader: 'url-loader',
options: {
limit: 10000
}
}
]
}
}
For production builds it's recommended to extract the CSS from your bundle being able to use parallel loading of CSS/JS resources later on. This can be achieved by using the mini-css-extract-plugin to extract the CSS when running in production mode.
![]() Juho Vepsäläinen |
![]() Joshua Wiens |
![]() Kees Kluskens |
![]() Sean Larkin |
![]() Michael Ciniawsky |
![]() Evilebot Tnawi |
![]() Joscha Feth |