Unhandled exception when --target has unexpected value

[Ky6uk]

• I have searched for similar issues
• I am using the latest version of npm-check-updates
• I am using node >= 10.17

---

ncu --target woof will throw an error with the stack trace to the output channel. I'm not sure, but it feels like something unhandled.

[raineorshine]

Yeah, we can do a nicer error message there. I'm going to wait until commander.js v7 when the choices feature is added.

tj/commander.js#1331

[LitoMore]

I strongly recommend you to use meow. For using meow, we don't need to wait any feature from upstream, because it's simple and powerful.

[raineorshine]

I strongly recommend you to use meow.

Looks great, but I don't think it's worth switching cli frameworks just for validation, which can be easily implemented if we don't want to wait for commander.

For using meow, we don't need to wait any feature from upstream, because it's simple and powerful.

Actually, we're waiting for help text generation.

[LitoMore]

Actually, we're waiting for help text generation.

I can help. ✌️

[raineorshine]

This was done at some point