A warning about "caniuse-lite" prints during minification

[glasser]

minifier-css depends recursively on browserslist, which you can see in its checked-in shrinkwrap file.

browserslist has this code to print a warning if its dependency caniuse-lite is more than 6 months out of date. It was last updated in Meteor in February so it is printing for all users who minify right now.

I don't even know if minifier-css takes advantage of anything provided by browserslist or caniuse-lite. I suggest it should set the $BROWSERSLIST_IGNORE_OLD_DATA environment variable to disable this warning.

[benjamn]

Should be mitigated by c2499b1f21ef195f31652deac7443cc33b98af66, which will be released as part of Meteor 1.8.2. Disabling the warning is tempting, but I don't mind the additional incentive to keep these packages up-to-date.

[evolross]

FWIW I'm still seeing this after updating my app to Meteor 1.9.

[repetitioestmaterstudiorum]

Seeing this in Meteor 1.10.1

[linegel]

Appears in Meteor 1.10.1

[Natas0007]

Still in Meteor 1.10.2. I've disabled with the env var, but just giving a heads up.

[afrokick]

There is PR #11075 for updating the version of PostCSS to resolve this issue.

[afrokick]

Will be in 1.10.3 Thanks @filipenevola

[filipenevola]

minifier-css@1.5.1 is published.

[iancwinter]

Still there in 1.11. :-(

[afrokick]

Ok, i’ll update it later to use the latest version of PostCSS

[filipenevola]

Published minifier-css@1.5.3 and standard-minifier-css@1.6.1.

meteor update standard-minifier-css should fix your warning.

[iancwinter]

Hmm… I already have standard-minifier-css@1.6.0 as part of Meteor 1.11 so not sure a downgrade to 1.5.3 would fix things (and may introduce other incompatibilities). Unless minifier-css is different to standard-minifier-css.

[afrokick]

@filipenevola so, we need to update standard-minifier-css to use the latest version of minifier-css, right?

#11170

[filipenevola]

Yeah, meteor update standard-minifier-css is also necessary (1.6.1 was published).

But I believe this warning can come back again and again, then we need to always bump these versions when PostCSS releases a new version.