Skip to content
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

Option to return Chrome versions for Chromium-based browsers #508

Open
ylemkimon opened this issue Jul 19, 2020 · 4 comments · May be fixed by #511
Open

Option to return Chrome versions for Chromium-based browsers #508

ylemkimon opened this issue Jul 19, 2020 · 4 comments · May be fixed by #511

Comments

@ylemkimon
Copy link

Due to insufficient compatibility data, most tools ignore browsers unpopular in US, such as UC Browser and QQ Browser. (e.g., babel/babel#8552) But as far as I understand, this is the very reason Browserslist is created. Fortunately, most of them are based on Chromium and compatibility is almost identical to the version of Chromium they are based on. So an option to return corresponding Chrome versions for those browsers would be useful and encourage people to support them.

@ai
Copy link
Member

ai commented Jul 19, 2020

We already have mobileToDesktop option. We can add something like normalize.

Do you want to send PR?

@ylemkimon
Copy link
Author

ylemkimon commented Jul 19, 2020

@ai Yes, I would like to send a PR. One question is should I implement this as a query or an option? The former seems to be backward compatible but may break if the version doesn't match and there isn't a global query (yet), whereas the latter needs to update all the tools.

@ai
Copy link
Member

ai commented Jul 19, 2020

As an option, because it if a feature for a tool (like Babel), not a user.

It will be much easier for us to convince a few tools to use the new option, than change user’s configs.

@ai
Copy link
Member

ai commented Jul 19, 2020

@JLHwung will it be a useful option for Babel?

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

Successfully merging a pull request may close this issue.

2 participants