fix: ACNA-4397 - TypeError: opts.getPluginsList is not a function#778
Merged
fix: ACNA-4397 - TypeError: opts.getPluginsList is not a function#778
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
arjuncooliitr
approved these changes
Mar 10, 2026
dthampy
approved these changes
Mar 10, 2026
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
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.
Closes #776
Description
https://github.com/oclif/core/releases/tag/4.8.4 released earlier today, is causing the issue.
It is a dependency of @oclif/plugin-plugins. When I tested with v4.8.3, it doesn't cause the issue. Because of semver, whenever you updated the plugins-plugin (through a cli reinstall) it will update the patch version.
The problem is... we can't update any plugins (which would be a workaround) because the plugins-plugin is broken.
Fix is to either:
We will use option 2 since it is the least risky update without updating a major version (which requires extensive testing).
Motivation and Context
Add ability to install plugins without getting the error.
How Has This Been Tested?
Local test via
./bin/run plugins(remove node_modules and package-lock.json, runnpm i)Types of changes
Checklist: