npm / @oclif/core
@oclif/core
What changed in @oclif/core 4 to 5, from its official release notes, upgrade guides and advisories. Sources checked 2026-10-19.
1 breaking1 security1 deprecations8 new APIs and options3 behavior and defaults10 fixes and other
See which of these apply to your code, ranked, in your agent:
npx @unstale/cli init@oclif/core 53 changes
Breaking changes 1
Requires Node >=22 and drops EOL Node versions.
New APIs and options 1
Adds an environment variable to configure the stdin read timeout.
Fixes and other changes 1
When --json is enabled, errors use the error's oclif exit code.
@oclif/core 421 changes
Security 1
Resolved a security vulnerability in the PowerShell path.
Deprecations 1
Warnings are now emitted for hidden, deprecated aliases.
New APIs and options 7
Exposes the root help formatter for developers to use.
Adds Args.option() for typed arg options.
Adds an API and basic logic for command-level constraints, including conditions.
Adds overloads that provide variadic argument return types.
Adds the multiple property to ArgProps for defining variadic arguments.
Allows an array of default values for varargs.
Implements variadic argument parsing with a shift/pop algorithm.
Behavior and default changes 3
Validates variadic argument constraints at definition time.
Help text shows a ... suffix for variadic arguments.
Flag help now shows the environment variable associated with a flag, helping users identify how to configure it.
Fixes and other changes 9
Error messages are now included in --json output.
Causative errors are now also pretty-printed, making them easier to read.
A typo in a PowerShell command was fixed.
WSL handling is corrected.
Includes the multiple property in cached argument metadata.
Provides clearer messages when variadic arguments are invalid.
--flags-dir now works with third-party plugins.
Windows shell identification is more reliable.
Descriptions are retained when the summary is hidden in help.