You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 28, 2020. It is now read-only.
Currently, using es-check foo dist/*.js returns ES-Check: there were no ES version matching errors! 馃帀
However you could assume that if the dev mistyped foo instead of es4, he could also mistype se7 instead of es7.
I think es-check should throw an error when it does not recognize a valid ecmaVersion argument (see the default behavior in
Devs that check their ES version do not need to be handled; lets tell them the harsh truth; they made a typo!
Are There Examples Of This Requested Update Elsewhere?
Nope, but issue #40 could have been avoided perhaps?
Specially if when such an error is detected, you could display a usage info with all the possible ecmaVersion.
The text was updated successfully, but these errors were encountered:
Requested Update
Currently, using
es-check foo dist/*.js
returnsES-Check: there were no ES version matching errors! 馃帀
However you could assume that if the dev mistyped
foo
instead ofes4
, he could also mistypese7
instead ofes7
.I think
es-check
should throw an error when it does not recognize a validecmaVersion
argument (see thedefault
behavior ines-check/index.js
Line 74 in b7a40f2
Why Is This Update Needed?
Devs that check their ES version do not need to be handled; lets tell them the harsh truth; they made a typo!
Are There Examples Of This Requested Update Elsewhere?
Nope, but issue #40 could have been avoided perhaps?
Specially if when such an error is detected, you could display a
usage
info with all the possibleecmaVersion
.The text was updated successfully, but these errors were encountered: