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

bug or expected: `last 1 Node version` throws `browserslist: Unknown browser Node` #410

Open
JounQin opened this issue Sep 7, 2019 · 4 comments

Comments

@JounQin
Copy link

@JounQin JounQin commented Sep 7, 2019

As title, I think it should make sense like last 1 Chrome version.

@ai

This comment has been minimized.

Copy link
Member

@ai ai commented Sep 7, 2019

What is your use case for this query?

BTW, what version to you expect to have for last 2 Node versions?

@JounQin

This comment has been minimized.

Copy link
Author

@JounQin JounQin commented Sep 7, 2019

I'm writing a shareable config, which targets latest modern browsers and node.

https://github.com/1stG/configs/blob/master/packages/browserslist-config/latest.js

All available node versions are listed at https://nodejs.org/dist/index.json .

So last 2 node versions should emit 12.10.0 and 12.9.1 for now.

@ai

This comment has been minimized.

Copy link
Member

@ai ai commented Sep 7, 2019

Yeap, this behavior looks good. Do you want to send PR?

@JounQin

This comment has been minimized.

Copy link
Author

@JounQin JounQin commented Sep 8, 2019

OK, I'll do in few days.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
2 participants
You can’t perform that action at this time.