New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Downgrade oclif and typescript #666
Conversation
Upgrading oclif introduced bugs with boolean flags. Need to downgrade again until oclif/core#536 is merged to oclif.
We detected some changes at packages/*/src and there are no updates in the .changeset. |
packages/cli-main/package.json
Outdated
@@ -51,7 +51,7 @@ | |||
] | |||
}, | |||
"dependencies": { | |||
"@oclif/core": "1.16.4", | |||
"@oclif/core": "1.9.2", | |||
"@oclif/plugin-commands": "^2.2.0", | |||
"@oclif/plugin-help": "^5.1.14", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@shauns excellent point, I've updated those as well.
WHY are these changes introduced?
Upgrading oclif introduced bugs with boolean flags. Need to downgrade again until oclif/core#536 is merged to oclif.
This is an alternative approach vs #662
WHAT is this pull request doing?
Downgrades oclif and typescript, essentially reverting #555 (but with some extra work because the
base-command
code has changes)How to test your changes?
Run the CLI...
Measuring impact
How do we know this change was effective? Please choose one:
Checklist
dev
ordeploy
have been reflected in the internal flowchart.