config
config copied to clipboard
oclif
base config object and standard interfaces for oclif components
Bumps [@types/lodash](https://github.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/lodash) from 4.14.181 to 4.14.197. Commits See full diff in compare view [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter...
![dependabot[bot] avatar](https://avatars.githubusercontent.com/in/29110?v=4 "dependabot[bot] avatar"){kind=avatar}
when an array flag is used with a default, but the user doesn't specify a value, subsequent flags are read into the array suggestion: array flags *don't* read values starting...
This addresses both https://github.com/oclif/oclif/issues/299 and https://github.com/oclif/oclif/issues/488 `loadTSConfig()` in `src/ts-node.ts` was not properly resolving extended configuration files, because while `parseConfigFileTextToJson` will load and parse a given `tsconfig.json` file, it does not...
To explicitly call out a TS project (a backup inference is checked via devDeps)
Fixes #176 by using TypeScript's `parseJsonConfigFileContent()`, which resolves the "extends" in a tsconfig and merges the various options in the base and extending tsconfigs. I wasn't what was a good...
Hey, this MR tries to fix https://github.com/oclif/oclif/issues/299 by adding a ENV to set a custom typescript config, nothing special, but enables users to set a custom tsconfig in development scenarios....
add an alias 'default' to set a default command.
This is required for correctly suggesting flags mutiple times (only if the flag supports it) in shell completion. Without merging this PR, this feature can't be implemented on the shell...
https://github.com/oclif/oclif/issues/277
excludes all `__*__` folders from sub command parser
