Got Chrome 4 as earliest supported version
See original GitHub issueCommands and results
npx browserslist '> 0.5% in my stats'
Result
and_chr 80
android 80
chrome 80
chrome 70
firefox 74
ios_saf 13.4
ios_saf 13.3
ios_saf 13.0-13.1
ios_saf 12.2-12.4
safari 13
Looks like it’s exactly what I have in my browserslist-stats.json
.
But when I use babel/preset-env
and pass the same string/same config got next (debug mode on)
Using targets:
{
"android": "80",
"chrome": "4",
"firefox": "74",
"ios": "12.2",
"safari": "13"
}
When I pass all browsers’ version into babel-env directly I don’t have problems with build.
Versions
"@babel/core": "7.9.0"
Issue Analytics
- State:
- Created 3 years ago
- Reactions:2
- Comments:20 (15 by maintainers)
Top Results From Across the Web
Google Chrome version history - Wikipedia
Versions Edit ; 29.0.1547, 2013-08-20 (Linux, macOS, and Windows) 2013-08-21 (Android) 2013-09-12 (iOS), Blink 29 (except iOS), 3.19.18. Support for VP9 final ...
Read more >4. Update to latest Chrome version - Google Support
To update your devices to the latest version of Chrome, you can use the Chromebook Recovery Utility. It can take as little as...
Read more >UPDATE Chrome support ends for Windows 7 & 8.1 early 2023
Google Chrome 108 is now displaying warnings about the upcoming end of support : "To get future Google Chrome updates, you'll need Windows...
Read more >Looking Back At the First Version of Google Chrome - YouTube
In this video, I take a look back at the first version a.k.a. the original version of Google Chrome ever released, Chrome version...
Read more >Google will end Chrome support on Windows 7 and 8.1 in ...
Google will end Chrome support on Windows 7 and 8.1 in early 2023. You'll still be able to use older versions of Google's...
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 FreeTop 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
Top GitHub Comments
The fix released in 4.16.1.
I doubled checked and the fix works as expected.
I was running
npm browserslist --mobile-to-desktop '> 0.5% in my stats'
When running
node cli.js --mobile-to-desktop '> 0.5% in my stats'
it does no longer reportsand_chr 4
butand_chr 87
. 🎉I updated the PR.