Browserslist: caniuse-lite is outdated #1184
Comments
|
Hi. Just update the library as it mentioned in the text. Autoprefixer doesn't need any update since it always use latest version. SOLUTION UPDATE (2020) npx browserslist@latest --update-db |
|
Thank you! |
|
Sorry to intrude in this topic, but I am having the same issue. I ran the command ( In my case I am using the I hope you can help @ai or @PostMidnight |
|
@sybrendotinga hm, strange. Can you show your |
|
It is a big one, so I left all the clutter (name, description, etc.) out: {
"devDependencies": {
"@babel/core": "^7.2.2",
"@babel/plugin-syntax-dynamic-import": "^7.2.0",
"@babel/plugin-transform-runtime": "^7.2.0",
"@babel/polyfill": "^7.2.5",
"@babel/preset-env": "^7.3.1",
"@babel/runtime": "^7.3.1",
"@fortawesome/fontawesome-free": "^5.7.0",
"@intervolga/optimize-cssnano-plugin": "^1.0.6",
"@vue/test-utils": "^1.0.0-beta.27",
"axios": "^0.18.0",
"babel-core": "^7.0.0-0",
"babel-eslint": "^10.0.1",
"babel-jest": "^23.6.0",
"babel-loader": "^8.0.5",
"babel-plugin-component": "^1.1.1",
"browser-sync": "^2.26.3",
"browser-sync-spa": "^1.0.3",
"browser-sync-webpack-plugin": "^2.2.2",
"clean-webpack-plugin": "^1.0.1",
"css-loader": "^2.1.0",
"cypress": "^3.1.5",
"dotenv": "^6.2.0",
"dotenv-webpack": "^1.7.0",
"element-theme-chalk": "^2.5.3",
"element-ui": "^2.5.3",
"eslint": "^5.12.1",
"eslint-config-standard": "^12.0.0",
"eslint-friendly-formatter": "^4.0.1",
"eslint-loader": "^2.1.1",
"eslint-plugin-cypress": "^2.2.0",
"eslint-plugin-import": "^2.16.0",
"eslint-plugin-node": "^8.0.1",
"eslint-plugin-promise": "^4.0.1",
"eslint-plugin-standard": "^4.0.0",
"eslint-plugin-strict-vue": "^1.0.0",
"eslint-plugin-vue": "^5.1.0",
"eslint-plugin-vue-types": "^1.0.0",
"file-loader": "^3.0.1",
"friendly-errors-webpack-plugin": "^1.7.0",
"html-webpack-plugin": "^3.2.0",
"iotacss": "^1.6.0",
"jest": "^23.6.0",
"jest-serializer-vue": "^2.0.2",
"launch-editor-middleware": "^2.2.1",
"mini-css-extract-plugin": "^0.5.0",
"node-ip": "^0.1.2",
"node-sass": "^4.11.0",
"postcss-loader": "^3.0.0",
"regenerator-runtime": "^0.13.1",
"sass-loader": "^7.1.0",
"sass-resources-loader": "^2.0.0",
"static-server": "^2.2.1",
"style-loader": "^0.23.1",
"stylelint": "^9.10.1",
"stylelint-config-recommended": "^2.1.0",
"stylelint-config-recommended-scss": "^3.2.0",
"stylelint-config-sass-guidelines": "^5.3.0",
"stylelint-config-standard": "^18.2.0",
"stylelint-scss": "^3.5.1",
"stylelint-webpack-plugin": "^0.10.5",
"terser-webpack-plugin": "^1.2.1",
"url-loader": "^1.1.2",
"vue": "^2.5.22",
"vue-hot-reload-api": "^2.3.1",
"vue-html-loader": "^1.0.0",
"vue-jest": "^3.0.2",
"vue-loader": "^15.6.2",
"vue-style-loader": "^4.1.2",
"vue-template-compiler": "^2.5.22",
"vue-template-loader": "^1.0.0",
"vue-types": "^1.3.4",
"vuelidate": "^0.7.4",
"vuex": "^3.1.0",
"webpack": "^4.29.0",
"webpack-assets-manifest": "^3.1.1",
"webpack-bundle-analyzer": "^3.0.3",
"webpack-cleanup-plugin": "^0.5.1",
"webpack-cli": "^3.2.1",
"webpack-dev-server": "^3.1.14",
"webpack-merge": "^4.2.1",
"webpackbar": "^3.1.5"
}
}What I have also tried is to trash the node_modules, and re-run the |
|
Maybe you this |
|
@sybrendotinga yeap, Solutions:
|
|
Same issue here. Running |
|
@or-else answer is the same as above. Use full update |
|
Yes, indeed it helped. Thanks. |
|
If you have a multitude of out of date packages, the fastest way to update them is with npm-update-all. |
For me the second option ( I noticed that the third action required a lot of manual version picking. I would not recommend going through this process. The first option probably also requires to run the Thanks for helping! |
|
I have the same problem, |
|
For me this was caused by slightly out of date ng-packagr/build-ng-packagr. For an angular project, updating them both solved the issue. ng-packagr uses autoprefixer. |
|
@Dan503 thank you ,I got resolved this problem! |
npm will use whatever the oldest common dependency is of packages. This is why trying to install the latest version of a package doesn't always install the latest version of the package. An outdated module that also depends on it can hold back the upgrade. Sometimes you can figure out all the dependency conflicts by searching package-lock.json (Or the yarn equivalent). It can be difficult though. That is why the easiest way to fix node_modules version conflicts is by using npm-update-all. It is a bit of a nuclear solution but it tends to fix far more problems than it can potentially cause. |
|
I just tried to Then, I tried to Still see this warning. |
|
after tried so many things i got solved this using |
|
I tried |
|
@Grawl check |
|
i noticed in my case it's happened for npm install failed, and then i successfully installed npm, still, it shows me but after some time everything works fine. |
|
@ai it's I though if I run |
Yeap, it should do it. Sorry, I have no idea why it doesn’t work. Can you ask yarn community? |
|
I solved it by the following steps in my project:
{
"dependencies": {
...,
- "caniuse-lite": {
- "version": "1.0.30000923",
- "resolved": "https://registry.npmjs.org/caniuse-lite/-/caniuse-lite-1.0.30000923.tgz",
- "integrity": "sha512-j5ur7eeluOFjjPUkydtXP4KFAsmH3XaQNch5tvWSO+dLHYt5PE+VgJZLWtbVOodfWij6m6zas28T4gB/cLYq1w=="
- },
...
}
}
|
|
For any lost soul ending up here: My project uses The culprit was not |
|
Soon we will have special tool |
|
@ucarmurat I removed your comment, because “use old versions to not see the warning” is a very bad practice. Warning helps you. The problem is not a warning, but an outdated database. By hiding warning you keep the origin problem in the place. It is like to stop seeing the doctor to stop listen to sad news rather than start the treatment. |
|
Browserslist 4.10 was released with To hide warning:
|
|
This is what I get trying to run |
|
@CodeBradley seems like you have old Browserslist. Try |
Thanks, this solved the issue for me. |
lol same |
|
@cyayung here is the right solution )you mentioned old solutions) npx browserslist@latest --update-db |
|
@zdimaz try If it will not work, create an issue I remove your comment because of “noob” word. You will be blocked next time. It is not polite behavior. |
|
C:\Users\Admin>npx browserslist@latest --update-db Does not work autoprefixer |
Thanks for the reply. caniuse-lite is still outdated |
|
@zdimaz solution is in the root message. You need to run it in the project. |
|
@cyayung create an issue at Browserslist with all details |
|
Seeing the same: |
|
@aaronjensen yeap, you already have the latest If you still have a warning, please open a issue with your |
- avoids console output, as found in postcss/autoprefixer#1184
after this update command, high chance the project will no longer build...then need to find ways to roll back..... don't ask me how I know.... |
Apparently can't use yarn for this. Gets rid of caniuse-lite deprecation warning when running bin/webpack. postcss/autoprefixer#1184
方法： 執行`npx browserslist@latest --update-db` ref: postcss/autoprefixer#1184 (comment)
|
The official solution for npx browserslist@latest --update-db |
and others
Hello,
First of all, thank you for this awesome library!!!
We are using nodebb which depends on autoprefixer. During nodebb build we noted the following:
Browserslist: caniuse-lite is outdated. Please run next command npm update caniuse-lite browserslist
I believe this is related to autoprefixer dependency that may need updating.
Related issue reported in nodebb github page): NodeBB/NodeBB#7271
Thank you!
The text was updated successfully, but these errors were encountered: