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 was archived by the owner on Apr 16, 2020. It is now read-only.
Repository navigation
This repository was archived by the owner on Apr 16, 2020. It is now read-only.
Throw error when conflicting type params are passed #56
@devsnek allowing duplicate flags isn’t necessary to allow overriding; but it may be that node’s options parser lacks the capability to properly distinguish them.
@ljharb my point is more that this isn't an issue specific to --type (although -m is unique in that its the only short flag which can "disagree" with a longer flag). perhaps someone could raise this issue upstream?
Activity
GeoffreyBooth commentedon Mar 9, 2019
Examples:
devsnek commentedon Mar 9, 2019
getting rid of
-mwould help so that its more obvious when you've duplicated the flag.aside from that, node in general just allows duplicated flags.
this is particularly important because it means you can override things from NODE_OPTIONS
ljharb commentedon Mar 9, 2019
@devsnek allowing duplicate flags isn’t necessary to allow overriding; but it may be that node’s options parser lacks the capability to properly distinguish them.
devsnek commentedon Mar 9, 2019
@ljharb my point is more that this isn't an issue specific to
--type(although-mis unique in that its the only short flag which can "disagree" with a longer flag). perhaps someone could raise this issue upstream?GeoffreyBooth commentedon Mar 10, 2019
cc @addaleax
GeoffreyBooth commentedon Apr 4, 2019
Resolved in #45