What is use case?

I try to avoid adding more queries, because it is hard to maintain so many queries for me.

The major use case is deduplicating information in package.json, especially since Browserslist and semver have different version range semantics.

I do not like solving this problem by adding an extra query. We already have too many queries.

Maybe we need to change node X query behavior in a major version.

We will not be able to release major version in next month because I spending all my free time on preparing PostCSS 8.

@ai I've added semver query as it uses the same logic with the project version query, but if it causes too much technical debt, I can remove it.

I am right that you have no critical issue to be fixed with this PR?

Let me finish with PostCSS 8 release process and then I will think about Node.js versions.

@ai Yes, this is just a convenience.