John Gee

There is not a separate option name for `--no-cheese`, both it and `--cheese` affect the option key `cheese`. Try the behaviour with: ``` .addOption(new Option("-t, --cheese-type ").conflicts("cheese")) ``` Example file:...

I have marked this issue as a feature request. It got left out of the implementation because it didn't fit into the pattern of specifying the internal option name, and...

> Could you guide me please? What would be useful is a real-world example. I understand you want to add a conflict with just the negative option of a dual...

For interest, did you encounter this lack in use or noticed in code? Yes, this is a case we could handle. I wrote code for this in `parseargs` where node...

I have opened a PR which will autodetect `node --eval` and `node --print` when _no_ arguments are specified to `.parse()`. To avoid breaking existing code or getting weird test results...

Released in v12.1.0

For interest, `parseArgs` started down this route and is also intending to switch to https://github.com/nodejs/eslint-plugin-nodejs-internal: - https://github.com/pkgjs/parseargs/issues/17 - https://github.com/pkgjs/parseargs/issues/90

I checked the TypeScript `moduleResolution` in my project. Ah ha, my tsconfig has `node16` and the `arethetypeswrong` warning is for `node16`+`CommonJS`, that lines up. ``` "compilerOptions": { "module": "node16", ```

Hmm, this is potentially tricky. TypeScript is not the tool for generating multiple versions of definition files. They recommend you generate one of ESM/CJS from your TypeScript and then use...

I had the same issue but I was not sure if it was a bug or a side-affect of having colon included in the word separators (added by the git...