I'm not sure I want to have more version constraints in here to maintain.

@taylorotwell, well, then, it seems to me, you need to roll back the changes from #5216 because:

cross-env 5.2 require node >= 4.0
cross-env 6.0 require node >= 8.0
cross-env 7.0 require node >= 10.14

In #5216, changes were adopted from version 6 to version 7. Should I create a PR return to version 6?

@andrey-helldar but npm will warn anyone who attempts to install v7 with a lower NPM version than 10.14? Why should we keep these constraints ourselves?

@driesvints, I think I did not immediately understand what Taylor wrote. This is a language barrier problem.

I agree, an additional check does not need to be introduced, but I saw Graham’s #5212 (comment) and decided to create this PR.