fix(lang): fix "Not enough non-option arguments" message for the Czech language

[mlc-mlapis]

Removing an extra comma at the end of the line.

[mlc-mlapis]

It seems that an additional formal step is still required. What is it? Can I help with it?

[mlc-mlapis]

It's a very trivial issue (only a typo, in fact) and simple to review. Why it takes so much time to merge?

[xmedeko]

@mlc-mlapis It needs to be approved by some maintainer: review is required by reviewers with write access.

Maybe @bcoe may help, please? The latest 17.6.0 release is unusable.

[mlc-mlapis]

@xmedeko Thanks for the help.

[mlc-mlapis]

@bcoe @nexdrew @nexdrew @maxrimue @lrlna Can you help, please? The latest 17.6.0 release is unusable.

[nexdrew]

Verified that this fixes the problem. Thanks for the contribution!

[nexdrew]

Bug introduced in #2220

[nexdrew]

@bcoe I'm not familiar with the tag/release protocol of yargs anymore, otherwise I would squash and merge this to prepare a 17.6.1 patch release.

Can we get a little help here, since this is affecting nx users? Thanks, hoping you're doing well!

[davidslaby]

I join @nexdrew's pleas. As nx user, I'm not able to run some commands. @bcoe or @mleguen could you help to release patch version, please? Thanks in advance!

[jirihybek]

Since this was not merged yet (a typo, in 25 days, really?) and it's breaking the nx package, I've found the following workaround. It may help someone.

Run node process with env var LANG like this: LANG=en_US npx create-nx-workspace....

[nexdrew]

I'll go ahead and merge it. Will have to figure out how to get a 17.6.1 release published.

Yargs is used by thousands of projects, and is (or at least was) used as a canary-in-the-goldmine package to help verify regressions of Node itself, so releases carry a lot of weight.

Perhaps @bcoe has been able to automate everything via release-please. Will see.