Some is deprecated
See original GitHub issuepostcss
was renewed recently - https://github.com/postcss/postcss/releases/tag/5.0.0 and now I get following:
Container#eachAtRule is deprecated. Use Container#walkAtRules instead.
Container#eachRule is deprecated. Use Container#walkRules instead.
Container#eachDecl is deprecated. Use Container#walkDecls instead.
Node#style() is deprecated. Use Node#raw()
Node#before is deprecated. Use Node#raws.before
Node#_value was deprecated. Use Node#raws.value
Issue Analytics
- State:
- Created 8 years ago
- Comments:16 (6 by maintainers)
Top Results From Across the Web
What is deprecated in IT? - TechTarget
Learn about deprecated in IT, which is when something is available or allowed, but is not recommended or that its failings are recognized....
Read more >Deprecation - Wikipedia
In several fields, especially computing, deprecation is the discouragement of use of some terminology, feature, design, or practice, typically because it ...
Read more >Deprecate Definition & Meaning - Merriam-Webster
The meaning of DEPRECATE is to express disapproval of. How to use deprecate in a sentence.
Read more >Deprecate - Definition, Meaning & Synonyms - Vocabulary.com
To deprecate is to show disapproval or to make someone feel unimportant by speaking to them disrespectfully, like seniors who deprecate younger students ......
Read more >Deprecated meaning? - Stack Overflow
Deprecated means they don't recommend using it, and that it isn't undergoing further development. But it ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
upgrading css-loader to the latest version (0.23) solved my issue.
@ai Sorry, I’ve checked again and it’s really cssnext’s problem, my bad. Thank you!