Skip to content

Warning "Container#eachAtRule is deprecated" After update to 0.18.0 #136

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
jiangfengming opened this issue Sep 11, 2015 · 22 comments
Closed

Comments

@jiangfengming
Copy link

Container#eachAtRule is deprecated. Use Container#walkAtRules instead.
Container#eachRule is deprecated. Use Container#walkRules instead.
Container#eachDecl is deprecated. Use Container#walkDecls instead.
@LeoAJ
Copy link

LeoAJ commented Sep 11, 2015

+1

@minhtranite
Copy link

@just-boris
Copy link

It is so bothering to see it in the output with any way to remove them.
I see that source code already has alias for that rules: https://github.com/webpack/css-loader/blob/master/lib/processCss.js#L35

Maybe it worth revert condition and use deprecated methods as fallback?

@veeracs
Copy link

veeracs commented Sep 16, 2015

+1

@just-boris
Copy link

Well, we need to wait until plugins mentioned by @vn38minhtran will have got a new version

@ljconde
Copy link

ljconde commented Sep 16, 2015

+1

2 similar comments
@filipalacerda
Copy link

+1

@yacodes
Copy link

yacodes commented Sep 22, 2015

+1

@goncalvesjoao
Copy link

+1
its strange I update to 0.19 version that uses postCSS 5 that supposedly solves this issue, but the warnings still occur.

@goncalvesjoao
Copy link

my bad. just deleted node_modules and ran npm install again and the warnings are gone!
Guys, just update css-loader to ^0.19.0 and this issue seems to be closed.

@ljconde
Copy link

ljconde commented Sep 23, 2015

@goncalvesjoao is right. Issue is fixed in 0.19.0.

@filipalacerda
Copy link

yep @goncalvesjoao is right. It's fixed in 0.19.0. :)

@thisiskylierose
Copy link

Updated to 0.19.0 and the warnings still appear.

@axelson
Copy link

axelson commented Sep 29, 2015

Is there a way to be sure which loader is generating a given error message?

@fgaleano
Copy link

+1. I'm running 0.19.0 and I see these warnings. Is it possible it's not css-loader after all?

@thisiskylierose
Copy link

It's some of the dependencies css-loader uses. If I get time, I will have a look and create a pull request.

@fxmaxvl
Copy link

fxmaxvl commented Oct 15, 2015

After updates - css-loader to 0.19 and nodejs to last stable version - problem disappeared

@sokra
Copy link
Member

sokra commented Oct 19, 2015

fixed

@sokra sokra closed this as completed Oct 19, 2015
@sdd
Copy link

sdd commented Nov 10, 2016

This has just started showing up for me, after not seeing those warnings before, after changing to Yarn, with css-loader ^0.23 in my package.json

@cycleseven
Copy link

I was seeing these same warnings. Turns out css-loader wasn't the culprit in my case, it was actually an outdated version of autoprefixer-loader. Might be helpful knowledge for somebody out there!

@michael-ciniawsky
Copy link
Member

@cycleseven Don't use autoprefixer-loader it is 'unofficial' without guaranteed support => postcss-loader + autoprefixer is the recommended way

@duhaime
Copy link

duhaime commented Feb 9, 2018

I removed autoprefix-loader from package.json and my webpack.config file, then updated css loader to: css-loader": "^0.28.9 and all was well.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests