avoid the "from" argument must be of type string error (#908) (e5dfd23)
invert Function behavior for url and import options (#939) (e9eb5ad)
properly export locals with escaped characters (#917) (a0efcda)
property handle non css characters in localIdentName (#920) (d3a0a3c)
Features
modules options now accepts object config (#937) (1d7a464)
support @value at-rule in selectors (#941) (05a42e2)
BREAKING CHANGES
minimum required nodejs version is 8.9.0
@value at rules now support in selector, recommends checking all @values at-rule usage (hint: you can add prefix to all @value at-rules, for example @value v-foo: black; or @value m-foo: screen and (max-width: 12450px), and then do upgrade)
invert {Function} behavior for url and import options (need return true when you want handle url/@import and return false if not)
exportLocalsStyle option was remove in favor localsConvention option, also it is accept only {String} value (use camelCase value if you previously value was true and asIs if you previously value was false)
exportOnlyLocals option was remove in favor onlyLocals option
modules option now can be {Object} and allow to setup CSS Modules options:
localIdentName option was removed in favor modules.localIdentName option
context option was remove in favor modules.context option
hashPrefix option was removed in favor modules.hashPrefix option
getLocalIdent option was removed in favor modules.getLocalIdent option
localIdentRegExp option was removed in favor modules.localIdentRegExp option
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
Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with @depfu rebase.
All Depfu comment commands
@depfu rebase
Rebases against your default branch and redoes this update
@depfu merge
Merges this PR once your tests are passing and conflicts are resolved
@depfu close
Closes this PR and deletes the branch
@depfu reopen
Restores the branch and reopens this PR (if it's closed)
@depfu pause
Ignores all future updates for this dependency and closes this PR
@depfu pause [minor|major]
Ignores all future minor/major updates for this dependency and closes this PR
@depfu resume
Future versions of this dependency will create PRs again (leaves this PR as is)
depfu[bot]
commented
4 years ago
Here is everything you need to know about this upgrade. Please take a good look at what changed and the test results before merging this pull request.
What changed?
✳️ css-loader (0.28.11 → 3.2.1) · Repo · Changelog
Release Notes
3.2.1
3.2.0
3.1.0
3.0.0
2.1.1
2.1.0
2.0.2
2.0.1
2.0.0
1.0.1
1.0.0
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by more commits than we can show here.
Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with
@depfu rebase.All Depfu comment commands