Caniuse lite is outdated как исправить

Liran H

8,1637 gold badges37 silver badges48 bronze badges

answered Jul 31, 2020 at 14:21

It sounds like you are using Visual Studio’s Web Compiler extension. There is an open issue for this found here: https://github.com/madskristensen/WebCompiler/issues/413

There is a workaround posted in that issue:

1. Close Visual Studio
2. Head to C:UsersUSERNAMEAppDataLocalTempWebCompilerX.X.X (X is the version of WebCompiler)
3. Delete following folders from node_modules folder: caniuse-lite and browserslist
   Open up CMD (inside C:UsersUSERNAMEAppDataLocalTempWebCompilerX.X.X) and run: npm i caniuse-lite browserslist

Simple, safe solution

The answer from @Alexandr Nil is safe, and was effective for me. I am writing as a full answer because it is easy to miss his comment.

npm --depth 20 update --save caniuse-lite browserslist 

This is good because:

1. There is no deletion of package-lock.json. Deleting that would leave you vulnerable to many packages getting upgraded with breaking changes, and you have a much bigger headache than you had before!

2. It is easy to understand exactly what it is doing, because it is explicit and very limited on what is to be updated.

3. It avoids the very large depth of 99 or 9999 which will work on some projects and systems, but not on others. If you have limited the depth to too small a number, it will not break anything. You can increase the depth and try again, until the project compiles successfully. I don’t know whether I actually needed 20, or could have managed with a smaller depth, such as 5 or 10. But with a depth of 20 took less than a minute to run.

4. It is quick and easy!

Thank you to @Zbyszek for suggesting to add the «—save» option. And yes, —depth is currently deprecated, but I assume they will replace it with something else rather than entirely remove it, so for now this seems to be the least destructive approach.

answered Dec 6, 2020 at 12:58

Many advise you to remove the package-lock.json or the yarn.lock. This is clearly a bad idea!

I am using Yarn and I was able to correct this problem by removing only the caniuse-db and caniuse-lite entries in my yarn.lock and doing a yarn.

It is not necessary to break the main function of the lockfile by deleting it.

answered Nov 16, 2020 at 11:02

For Angular Developers

Although, I’m answering this very late. I have a bad habit of checking changelogs of every library I use 😀 and while checking the release notes of Angular CLI, I figured out that they released a new patch yesterday (9th Jan 2020) which fixes this issue.

https://github.com/angular/angular-cli/releases/tag/v8.3.22

So when you will run ng update, you should get updates for @angular/cli:

And running ng update @angular/cli will fix this warning.

Cheers!

answered Jan 10, 2020 at 2:21

I found a short cut rather than going through vs code appData/webCompiler, I added it as a dependency to my project with this cmd npm i caniuse-lite browserslist. But you might install it globally to avoid adding it to each project.

After installation, you could remove it from your project package.json and do npm i.

Update:

In case, Above solution didn’t fix it. You could run npm update, as this would upgrade deprecated/outdated packages.

Note:

After you’ve run the npm update, there may be missing dependencies. Trace the error and install the missing dependencies. Mine was nodemon, which I fix by npm i nodemon -g

answered May 30, 2019 at 15:11

Continuation of answer above.

Had the same «plugin error» as @MehrdadBabaki. I uninstalled web compiler, deleted the AppData WebCompiler folder mentioned above, then reopened VS2019 and reinstalled web compiler.

THEN I went to the WebCompiler folder again and did npm i autoprefixer@latest npm i caniuse-lite@latest and npm i caniuse-lite browserslist@latest

answered Apr 26, 2019 at 19:52

answered Apr 18, 2019 at 2:01

In my case, I deleted out the caniuse-lite, browserslist folders from node_modules.

Then I type the following command to install the packages.

npm i -g browserslist caniuse-lite --save

worked fine.

As mentioned in Scott Kuhl’s answer this issue is mentioned in
https://github.com/madskristensen/WebCompiler/issues/413

For me, running the command npm i caniuse-lite- browserslist only worked for about 1/2 a day before it was an issue again.

The following solution, mentioned in the post, works much better. This updates the node.js file so that it uses console.log instead of console.warn when returning these errors.

You can manually update this file located at
C:Users[Username]AppDataLocalTempWebCompiler[VersionNumber]node_modulesbrowserslist

Or, so that it is done automatically, add the following to your .csproj file by:

1. Right click on project file and select «Unload Project»
2. Edit the .csproj file
3. Paste the following into the project file. I pasted it towards the end of the file, before the </Project> end tag and before the build web compiler package was imported.

    <ItemGroup>
        <PackageReference Include="MSBuildTasks" Version="1.5.0.235">
            <PrivateAssets>all</PrivateAssets>
            <IncludeAssets>runtime; build; native; contentfiles; analyzers</IncludeAssets>
        </PackageReference>
    </ItemGroup>
    <PropertyGroup>
        <TempFolder>$([System.IO.Path]::GetTempPath())</TempFolder>
    </PropertyGroup>
    <ItemGroup>
        <BrowsersListNodeJsFiles Include="$(TempFolder)WebCompiler*node_modulesbrowserslistnode.js" />
    </ItemGroup>
    <Target Name="BrowsersListWarningsAsInfo" BeforeTargets="WebCompile">
        <FileUpdate Files="@(BrowsersListNodeJsFiles)"
                    Regex="console.warn"
                    ReplacementText="console.log" />
    </Target>

1. Reload the project back into the solution.

answered Mar 27, 2019 at 12:51

I had same problem too this command works for me

npm i autoprefixer@latest

It automatically added need dependency in package.json and package-lock.json file like below:

package.json

"autoprefixer": "^9.6.5",

package-lock.json

"@angular-devkit/build-angular": {

...

"dependencies": {
    "autoprefixer": {
      "version": "9.4.6",
      "resolved": "https://registry.npmjs.org/autoprefixer/-/autoprefixer-9.4.6.tgz",
      "integrity": "sha512-Yp51mevbOEdxDUy5WjiKtpQaecqYq9OqZSL04rSoCiry7Tc5I9FEyo3bfxiTJc1DfHeKwSFCUYbBAiOQ2VGfiw==",
      "dev": true,
      "requires": {
        "browserslist": "^4.4.1",
        "caniuse-lite": "^1.0.30000929",
        "normalize-range": "^0.1.2",
        "num2fraction": "^1.2.2",
        "postcss": "^7.0.13",
        "postcss-value-parser": "^3.3.1"
      }
    },

...

  }

...

"autoprefixer": {
    "version": "9.6.5",
    "resolved": "https://registry.npmjs.org/autoprefixer/-/autoprefixer-9.6.5.tgz",
    "integrity": "sha512-rGd50YV8LgwFQ2WQp4XzOTG69u1qQsXn0amww7tjqV5jJuNazgFKYEVItEBngyyvVITKOg20zr2V+9VsrXJQ2g==",
    "requires": {
      "browserslist": "^4.7.0",
      "caniuse-lite": "^1.0.30000999",
      "chalk": "^2.4.2",
      "normalize-range": "^0.1.2",
      "num2fraction": "^1.2.2",
      "postcss": "^7.0.18",
      "postcss-value-parser": "^4.0.2"
    },

...

}

answered Oct 23, 2019 at 13:23

My Issue solved by doing this in my react native project

npx browserslist@latest —update-db

console ->

Latest version:     1.0.30001363
Installed version:  1.0.30001296
Removing old caniuse-lite from lock file
Installing new caniuse-lite version
$ npm install caniuse-lite
npm WARN deprecated sane@4.1.0: some dependency vulnerabilities fixed, support for node < 10 dropped, and newer ECMAScript syntax/features added
npm WARN deprecated uuid@3.4.0: Please upgrade  to version 7 or higher.  Older versions may use Math.random() in certain circumstances, which is known to be problematic.  See https://v8.dev/blog/math-random for details.
npm WARN deprecated uglify-es@3.3.9: support for ECMAScript is superseded by `uglify-js` as of v3.13.0
Cleaning package.json dependencies from caniuse-lite
$ npm uninstall caniuse-lite
caniuse-lite has been successfully updated

Target browser changes:
- and_chr 96
+ and_chr 103
- and_ff 95
+ and_ff 101
- android 96
+ android 103
- chrome 96
- chrome 95
- chrome 94
+ chrome 103
+ chrome 102
+ chrome 101
- edge 96
- edge 95
+ edge 103
+ edge 102
- firefox 95
- firefox 94
+ firefox 102
+ firefox 101
- ios_saf 15.2
- ios_saf 15.0-15.1
+ ios_saf 15.5
+ ios_saf 15.4
+ ios_saf 15.2-15.3
- opera 82
- opera 81
+ opera 87
+ opera 86
+ opera 85
- safari 15.2
- safari 15.1
- safari 13.1
+ safari 15.5
+ safari 15.4
- samsung 15.0
- samsung 14.0
+ samsung 17.0
+ samsung 16.0

answered Jul 6, 2022 at 11:59

tno2007tno2007

1,81423 silver badges15 bronze badges

I did downgrade the node version from 12 to 10

EDIT

This error occurred with me because I was using node version 12.
When I downgrade to version 10.16.5 this error stops. This error happened in my local env, but in prod and staging, it not happens. In prod and staging node version is 10.x so I just do this and I didn’t need to update any package in my package.json

answered Oct 24, 2019 at 2:44

Nick ManningNick Manning

2,7561 gold badge29 silver badges49 bronze badges

answered May 1, 2020 at 10:57

I’ve fixed this issue by doing, step by step:

1. remove node_modules
2. remove package-lock.json,
3. run npm --depth 9999 update
4. run npm install

answered May 18, 2020 at 11:15

Minimal solution that worked for me for current project

• A create-react-app project
• Ubuntu / *nix
• 2020
• Node 14.7

delete node_modules/browserslist directory in the project

now

npm run build

no longer generates that message

answered Aug 16, 2020 at 13:26

VirendraVirendra

5674 silver badges5 bronze badges

TriSTaRTriSTaR

4073 silver badges19 bronze badges

caasi

added a commit
to caasi/caasih.net
that referenced
this issue

May 7, 2020

joelmichael

added a commit
to fosterful/scheduler
that referenced
this issue

May 22, 2020

Apparently can't use yarn for this.
Gets rid of caniuse-lite deprecation warning when running bin/webpack.
postcss/autoprefixer#1184

Kamigami55

added a commit
to CAMPUS-NYCU/SmartCampus
that referenced
this issue

May 22, 2020