-
Notifications
You must be signed in to change notification settings - Fork 82
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
Cannot read property 'getInstance' of undefined #555
Comments
Hi @mattmccafferty thanks for reporting this! Do you mind giving us some more info: what version of the extensions are you on? and what version of the cli? You can find the cli version by running |
Extension: v49.4.0 |
What plugins do you have installed? |
@oclif/plugin-autocomplete 0.1.5 (core) |
Did an update, just to try it: sfdx update sfdx force:org:open |
Also tried this: npm install --global sfdx-cli
husky > Setting up git hooks
Thank you for using core-js ( https://github.com/zloirock/core-js ) for polyfilling JavaScript standard library! The project needs your help! Please consider supporting of core-js on Open Collective or Patreon:
Also, the author of core-js ( https://github.com/zloirock ) is looking for a good job -)
Thank you for installing EJS: built with the Jake JavaScript build tool (https://jakejs.com/)
Thank you for using husky!
|
I am experiencing the exact same problem. Unable to run any sfdx commands. |
its failing with this line: |
looks like salesforce-alm was introduced to my system this morning... |
@mattmccafferty I'm fairly certain its related to the sfdx update. I was able to deploy a package on friday using vscode, then installed the latest version of sfdx. This is when everything stopped working |
It must have updated this morning as the timestamp I have is 8:58AM on the salesforce-alm folder and that appears to have been published 4 days ago, and I was working fine on Friday too.... just tried this too:
Thank you for using core-js ( https://github.com/zloirock/core-js ) for polyfilling JavaScript standard library! The project needs your help! Please consider supporting of core-js on Open Collective or Patreon:
Also, the author of core-js ( https://github.com/zloirock ) is looking for a good job -)
|
Having the same issue here:
|
Hi team, I am also getting the same error. since update. My version: sfdx-cli/7.69.0-c7be45ae22 darwin-x64 node-v12.18.3 Error information:
|
Can you try removing your installed version of
|
In fact, please remove all these plugins: Those are bundled with the CLI and there is no reason to have it installed unless you are tiring to pin to a specific branch or an earlier version. If you really are trying to link to an older version, try uninstalling it and reinstalling that plugin. If you still get there error then, I'll try to see why the oclif module resolution is failing. |
this appears to have worked.... sfdx plugins:uninstall salesforcedx |
After I uninstalled salesforcedx, tried the additional ones. One said I still had salesforcedx installed... did I do this right?? each failed... sfdx plugins:uninstall force-language-services sfdx plugins:uninstall salesforce-alm sfdx plugins:uninstall salesforce-lightning-cli |
That was only for the people who did have them installed, like @aabrego-sfdc |
That also worked for me but I don't recall to have installed any plugin manually previously. Thanks @amphro and @mattmccafferty Summarizing the commands for anyone with the same issue:
|
yeah, i never installed them either. |
@jefersonchaves you don't need to install salesforcedx as it is bundled with the cli. Only install it if you need to pin to a future version. Since you didn't specify a version, I'm assuming you want latest so it is better to use the one that is shipped with the CLI.
You will still see salesforcedx in the output above. |
@amphro: fair enough, I just commented that I don't recall having installed the other ones. So I forced the uninstall anyway, including |
Ya, I'm saying you shouldn't reinstall |
I uninstalled all these 4 plugins:
And my My final configuration looks like this:
Thanks @amphro and everyone for your input. @amphro Separate but related question: why @salesforce/lwc-dev-server plugin is also listed along with the |
Cannot do anything with vs code and salesforce.
This error occurs for any of the commands. Reinstalled latest node.js just in case.
stack:
"status": 1, "name": "TypeError", "message": "Cannot read property 'getInstance' of undefined", "exitCode": 1, "commandName": "ConfigGetCommand", "stack": "TypeError: Cannot read property 'getInstance' of undefined\n at ConfigGetCommand.hooksFromLifecycleEvent (C:\Users\jeepg\AppData\Local\sfdx\node_modules\salesforce-alm\node_modules\@salesforce\command\lib\sfdxCommand.js:401:44)\n at ConfigGetCommand.init (C:\Users\jeepg\AppData\Local\sfdx\node_modules\salesforce-alm\node_modules\@salesforce\command\lib\sfdxCommand.js:248:20)\n at async ConfigGetCommand._run (C:\Users\jeepg\AppData\Local\sfdx\node_modules\salesforce-alm\node_modules\@salesforce\command\lib\sfdxCommand.js:92:13)\n at async Config.runCommand (C:\Users\jeepg\AppData\Local\sfdx\client\7.69.0-c7be45ae22\node_modules\@oclif\config\lib\config.js:172:9)\n at async Main.run (C:\Users\jeepg\AppData\Local\sfdx\client\7.69.0-c7be45ae22\node_modules\@oclif\command\lib\main.js:22:9)\n at async Main._run (C:\Users\jeepg\AppData\Local\sfdx\client\7.69.0-c7be45ae22\node_modules\@oclif\command\lib\command.js:43:20)\n at async Object.run (C:\Users\jeepg\AppData\Local\sfdx\client\7.69.0-c7be45ae22\dist\cli.js:32:20)\nOuter stack:\n at Function.wrap (C:\Users\jeepg\AppData\Local\sfdx\node_modules\salesforce-alm\node_modules\@salesforce\core\lib\sfdxError.js:151:27)\n at ConfigGetCommand.catch (C:\Users\jeepg\AppData\Local\sfdx\node_modules\salesforce-alm\dist\ToolbeltCommand.js:247:46)\n at async ConfigGetCommand._run (C:\Users\jeepg\AppData\Local\sfdx\node_modules\salesforce-alm\node_modules\@salesforce\command\lib\sfdxCommand.js:97:13)\n at async Config.runCommand (C:\Users\jeepg\AppData\Local\sfdx\client\7.69.0-c7be45ae22\node_modules\@oclif\config\lib\config.js:172:9)\n at async Main.run (C:\Users\jeepg\AppData\Local\sfdx\client\7.69.0-c7be45ae22\node_modules\@oclif\command\lib\main.js:22:9)\n at async Main._run (C:\Users\jeepg\AppData\Local\sfdx\client\7.69.0-c7be45ae22\node_modules\@oclif\command\lib\command.js:43:20)\n at async Object.run (C:\Users\jeepg\AppData\Local\sfdx\client\7.69.0-c7be45ae22\dist\cli.js:32:20)", "warnings": []}
The text was updated successfully, but these errors were encountered: