Feature request: automatically use `name`, `version` and `description` fields in nearest package.json

[zanminkian]

Support a method named usePackageJson. When it's called, commander use will use the nearest package.json file, and use its name, version and description filds as commander's name, version and description.

const program = new Command();
program.usePackageJson(import.meta.url, {name: true, version:true, descrition: true});

// Equivalent to:
const packageJson = getProjectPackageJson();
const program = new Command();
program.name(packageJson.name).version(packageJson.name).description(packageJson.description);

Why?

1. Name and version are commonly used. Almost every cli tool need them. Commander is expected to simplify it.
2. Using import packageJson from '../package.json' seems not a good prectice for developers. I think the source code should not rely on a json config outside of the source code base. For example, package.json is in the root, while the cli.js is in <root>/src directory. the code inside src rely a config outside of src. It seems break the edge.

[shadowspawn]

I might be missing something. These two comments seem to conflict? Unless you mean it is ok for Commander to look for nearest file, but you don't want the program author to need to refer to a higher level package.json.

When it's called, commander use will use the nearest package.json file

I think the source code should not rely on a json config outside of the source code base.

[shadowspawn]

I had noticed possibility for looking for package.json for version, but good suggestion that could also get name and description too.

[shadowspawn]

(I am slightly surprised Node.js does not have a nice way of returning package.json contents or location, since in many cases node loaded and processed package.json to work out what entry point to use for the package.)

[zanminkian]

Unless you mean it is ok for Commander to look for nearest file, but you don't want the program author to need to refer to a higher level package.json.

Exactly what I mean.

[zanminkian]

(I am slightly surprised Node.js does not have a nice way of returning package.json contents or location, since in many cases node loaded and processed package.json to work out what entry point to use for the package.)

These api can help.

[shadowspawn]

Nice, thanks for link! Currently still experimental.
findPackageJSON added in nodejs/node#55412