The devDependency css-loader was updated from 1.0.1 to 2.0.0.
This version is not covered by your current version range.
If you don’t accept this pull request, your project will work just like it did before. However, you might be missing out on a bunch of new features, fixes and/or performance improvements from the dependency update.
css modules are disabled by default, you need setup their use modules option. You can setup their using local (true is alias for this value) and global (previous behaviour) value. Why it is disabled by default? A lot of developers use css without css modules features and they get performance problems due postcss plugins spend time on analyze and processing file.
resolving logic for uls() and import at-rules works the same everywhere, it does not matter whether css modules are enabled (with global and local module) or not. Examples - url('image.png') as require('./image.png'), url('./image.png') as require('./image.png'), url('~module/image.png') as require('module/image.png').
resolving logic for uls() and import at-rules works the same everywhere, it does not matter whether css modules are enabled (with global and local module) or not. Examples - url('image.png') as require('./image.png'), url('./image.png') as require('./image.png'), url('~module/image.png') as require('module/image.png').
by default css modules are disabled (now modules: false disable all css modules features), you can return old behaviour change this on modules: 'global'
css-loader/locals was dropped in favor exportOnlyLocals option
import option only affect on import at-rules and doesn't affect on composes declarations
invalid @import at rules now emit warnings
use postcss@7
Bonus
code refactoring, updating deps and reusing postcss ast increase performance
FAQ and help
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html). If those don’t help, you can always [ask the humans behind Greenkeeper](https://github.com/greenkeeperio/greenkeeper/issues/new).
The devDependency css-loader was updated from
1.0.1
to2.0.0
.This version is not covered by your current version range.
If you don’t accept this pull request, your project will work just like it did before. However, you might be missing out on a bunch of new features, fixes and/or performance improvements from the dependency update.
Release Notes for v2.0.0
2.0.0 (2018-12-07)
The main BREAKING CHANGES:
modules
option. You can setup their usinglocal
(true
is alias for this value) andglobal
(previous behaviour) value. Why it is disabled by default? A lot of developers usecss
without css modules features and they get performance problems duepostcss
plugins spend time on analyze and processing file.uls()
andimport
at-rules works the same everywhere, it does not matter whether css modules are enabled (withglobal
andlocal
module) or not. Examples -url('image.png')
asrequire('./image.png')
,url('./image.png')
asrequire('./image.png')
,url('~module/image.png')
asrequire('module/image.png')
.Bug Fixes
urls()
with?#hash
(#803) (417d105)import
at-rules (#806) (4bdf08b)URL
inimport
at-rules (#818) (3ebdcd5)require
forurls()
(#854) (3338656)composes
(#845) (453248f)urls()
resolving logic formodules
(local
andglobal
) and without modules (#843) (fdcf687)Features
import
option doesn't affect oncomposes
(#822) (f9aa73c)urls
(#856) (5e702e7)import
at-rules (#857) (5e6034c)urls()
(#832) (da95db8)exportOnlyLocals
option (#824) (e9327c0)postcss
ast from other loaders (i.epostcss-loader
) (#840) (1dad1fb)BREAKING CHANGES
uls()
andimport
at-rules works the same everywhere, it does not matter whether css modules are enabled (withglobal
andlocal
module) or not. Examples -url('image.png')
asrequire('./image.png')
,url('./image.png')
asrequire('./image.png')
,url('~module/image.png')
asrequire('module/image.png')
.modules: false
disable all css modules features), you can return old behaviour change this onmodules: 'global'
css-loader/locals
was dropped in favorexportOnlyLocals
optionimport
option only affect onimport
at-rules and doesn't affect oncomposes
declarations@import
at rules now emit warningspostcss@7
Bonus
postcss
ast increase performanceCommits
The new version differs by 67 commits.
634ab49
chore(release): 2.0.0
6ade2d0
refactor: remove unused file (#860)
e7525c9
test: nested url (#859)
7259faa
test: css hacks (#858)
5e6034c
feat: allow to filter import at-rules (#857)
5e702e7
feat: allow filtering urls (#856)
9642aa5
test: css stuff (#855)
3338656
fix: reduce number of require for url (#854)
533abbe
test: issue 636 (#853)
08c551c
refactor: better warning on invalid url resolution (#852)
b0aa159
test: issue #589 (#851)
f599c70
fix: broken unucode characters (#850)
1e551f3
test: issue 286 (#849)
419d27b
docs: improve readme (#848)
d94a698
refactor: webpack-default (#847)
There are 67 commits in total.
See the full diff
FAQ and help
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html). If those don’t help, you can always [ask the humans behind Greenkeeper](https://github.com/greenkeeperio/greenkeeper/issues/new).Your Greenkeeper bot :palm_tree: