Yarn compains about 'yargs' about multiyargs

[vseventer]

It's a warning rather than an error it looks like, or does it interrupt the installation process? The reason is that the engines field should be used for process-related engines, like checking the node version. This package kinda hijacks this field for yargs, which I guess should really be a peer dependency.

[janaagaard75]

Yes, it's just an annoying warning. Everything works fine.

I think npm ignores the yargs property in engines, because I haven't installed yargs, and I don't get any warnings or errors when adding multiyargs. I understand why yargs has been added to engines, but if you have to read package.json in order to get any benefit of it, wouldn't it be better to have the information in the readme (as it's already the case)?

The dependency is only implicit in the sense, that if another module could create a cli with a similar interface, then it would also work with multiyargs. So the ideal solution would be something like npm updating the dependency system to allow specifying a peer dependency on an interface. 🙂