chore: remove @oclif/plugin-legacy dependency#3659
Merged
Conversation
This removes the @oclif/plugin-legacy plugin which is no longer needed.
eablack
had a problem deploying
to
AcceptanceTests
GitHub Actions
Failure
eablack
had a problem deploying
to
AcceptanceTests
GitHub Actions
Failure
This type definition was previously provided transitively through @oclif/plugin-legacy. Now that the legacy plugin is removed, we need to explicitly include it as a devDependency.
eablack
had a problem deploying
to
AcceptanceTests
GitHub Actions
Failure
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This PR removes the
@oclif/plugin-legacydependency from the project, as it is no longer needed. The plugin has been removed from both package.json dependencies and the oclif plugins configuration.Type of Change
Patch Updates (patch semver update)
Testing
Notes:
Verify that the CLI still builds and runs correctly without the legacy plugin.
Steps:
npm installto verify package-lock.json is validnpm run buildto ensure the build succeeds