Support `required` flags

Some options must always be specified.

I want to have a way to specify the required options in API.

Example

const cli = meow(`
    Usage
      $ process

    Options
      -i, --input   Input file
      -o, --output  Output file

    Examples
      $ process --input=lib/file.js --output=dest/file.js
`, {
    required: ['input', 'output']
});

A program without required options must quit with an error message.

$ process --output=dest/file.js

Missing required option:
    --input, -i  Input file

---

IssueHunt Summary

sbencoding has been rewarded.

Backers (Total: $60.00)

• issuehunt ($60.00)

Submitted pull Requests

• #110 Feat/add required flags
• #141 Implement isRequired feature as described in #51 and #110

---

Tips

• Checkout the Issuehunt explorer to discover more funded issues.
• Need some help from other developers? Add your repositories on IssueHunt to raise funds.

[sindresorhus]

I’m gonna reopen this as I think it could be useful for CLI only tools (ones that don’t have an API).

It could be specified like:

flags: {
	rainbow: {
		type: 'boolean',
		alias: 'r',
		required: true
	}
}

We should be clear in the docs that API level option validation should be preferred.

The required option could also accept a function that could receive the arguments and do its own check whether it’s required. For example, if the flag is only required when another flag is specified.

[SamVerschueren]

I agree with @kevva. I believe this should be handled by the code that is called. That allows the most flexibility with informative custom error messages.