Closed greenkeeper[bot] closed 5 years ago
dependency
css-loader was updated from 1.0.1
to 2.0.0
.Update to this version instead π
The main BREAKING CHANGES:
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.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')
.urls()
with ?#hash
(#803) (417d105)import
at-rules (#806) (4bdf08b)URL
in import
at-rules (#818) (3ebdcd5)require
for urls()
(#854) (3338656)composes
(#845) (453248f)urls()
resolving logic for modules
(local
and global
) and without modules (#843) (fdcf687)import
option doesn't affect on composes
(#822) (f9aa73c)urls
(#856) (5e702e7)import
at-rules (#857) (5e6034c)urls()
(#832) (da95db8)exportOnlyLocals
option (#824) (e9327c0)postcss
ast from other loaders (i.e postcss-loader
) (#840) (1dad1fb)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')
.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
optionimport
option only affect on import
at-rules and doesn't affect on composes
declarations@import
at rules now emit warningspostcss@7
postcss
ast increase performancedependency
css-loader was updated from 1.0.1
to 2.0.1
.Update to this version instead π
The new version differs by 8 commits.
e233d0a
chore(release): v2.0.1
a88fed1
fix: safe checking if params are present for at rule (#871)
503391f
chore(deps): update defaults (#870)
8c0bb58
Update CHANGELOG.md (#867)
124ada5
ci: fix commitlint analyze (#869)
ba8a7bc
docs: improve readme (#868)
12f88e2
test: resolving in node_modules (#866)
1825e8a
fix: getLocalIdent
now accepts false
value (#865)
See the full diff
dependency
css-loader was updated from 1.0.1
to 2.0.1
.dependency
css-loader was updated from 1.0.1
to 2.0.2
.dependency
css-loader was updated from 1.0.1
to 2.0.2
.dependency
css-loader was updated from 1.0.1
to 2.1.0
.dependency
css-loader was updated from 1.0.1
to 2.1.0
.
The dependency 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: