parsed value will look like below, I deduced this based on the documentation:
{ // string value (if you have used 'add' in npx changeset add) ['add'],// boolean values "sinceMaster": true, "verbose": true, "empty": true, "open": true, "gitTag": true, "snapshot": true// string values // Note: if you have passed these options in your CLI, these keys will be parsed as string, no matter the what you pass in // example: if you pass in - otp=123, 123 here, even though is a number, gets parsed as string since otp is configured to be parsed as // string in the above code "output", "otp", "since", "ignore", "tag", "snapshot", "snapshotPrereleaseTemplate",// The alias option in mri allows you to define alternative names (aliases) for CLI arguments. // This is particularly useful for supporting:// Short flags: Such as -v for - verbose. // Kebab-case flags: Allowing flags like - since-master to map to camelCase variables in JavaScript (e.g., sinceMaster). // Deprecated flags: If you want to support older names for backward compatibility but still map them to the current property names.}
parsed variable is used in a function named run imported from /run.ts
// run function callrun(parsed._, parsed, cwd).catch((err)
The first parameter is pared._ because in the documentation, it is provided that parsed commands like ‘add’ looks like { _: [‘add’]}
// run function definitionexport async function run( input: string[], flags: { [name: string]: any }, cwd: string) {
parsed contains mri parsed object based on the CLI args and the configuration set for booleans, strings, defaults, aliases.
cwd is a current working directory, you can get this with process.cwd()
Hey, my name is Ramu Narasinga. I study large open-source projects and create content about their codebase architecture and best practices, sharing it through articles, videos.