2

Not sure why this stopped working but all of the sudden sfdx forgot my org configuration.

I pulled down the latest changes from the master branch and went to push them into my checked out branch and this is the error I am getting.

ERROR running force:source:push: No org configuration found for name

As you can see the org is available and connected. What would cause this to disconnect and how am I able to reconnect?

I have tried everything from sfdx force:auth:jwt:grant --clientid... to sfdx force:source:deploy ... to creating a new project. Has this happened to anyone before?

enter image description here

Error UPDATE:

Error: Cannot find module '@oclif/config'
    at Function._load (/usr/local/lib/node_modules/sfdx-cli/node_modules/@salesforce/lazy-require/lib/LazyLoader.js:89:24)
    at require (/usr/local/lib/node_modules/sfdx-cli/node_modules/v8-compile-cache/v8-compile-cache.js:159:20)
    at Object.<anonymous> (~/.local/share/sfdx/node_modules/@oclif/command/lib/command.js:6:16)
    at Module._compile (/usr/local/lib/node_modules/sfdx-cli/node_modules/v8-compile-cache/v8-compile-cache.js:178:30)
    at Function._load (/usr/local/lib/node_modules/sfdx-cli/node_modules/@salesforce/lazy-require/lib/LazyLoader.js:89:24)
    at require (/usr/local/lib/node_modules/sfdx-cli/node_modules/v8-compile-cache/v8-compile-cache.js:159:20)
    at Object.<anonymous> (~/.local/share/sfdx/node_modules/@oclif/command/lib/index.js:24:19)
    at Module._compile (/usr/local/lib/node_modules/sfdx-cli/node_modules/v8-compile-cache/v8-compile-cache.js:178:30)

But I can see that the files are there:

enter image description here

3

Ya, this is most likely from the CLI upgrade, and installing the plugin again probably won't help.

It might be because your alias contains .'s in it which I didn't think worked in v6 either. Can you try to update your alias and see if that resolves it?

sfdx force:alias:set newAliasWithoutDots=<yourscratchorg>
sfdx force:config:set defaultusername=newAliasWithoutDots

Update:

Do not plugins:install salesforcedx. This is a common mispractice and should not be done, since the CLI is bundled with salesforcedx already. It just takes up more space on your machine. The only time you would need to manually install salesforcedx is if you need to tie to a specific version or pre-release. i.e.

sfdx plugins:install salesforcedx@pre-release

DO NOT try to install pre-release right now as we are not in pre-release season.

That missing @oclif/config is a known issue when installing salesforcedx in v7 and will be patched.

| improve this answer | |
  • So should we not install salesforcedx and uninstall it ? – Mohith Shrivastava Mar 28 '19 at 22:17
  • oh interesting. when I do this it looks like there are some files missing...I will post them in the question – Olivia Mar 28 '19 at 22:31
  • Do not install salesforcedx. There is no need to since it is bundled with the CLI and it is already the latest version. – Amphro Mar 28 '19 at 22:54
  • ah shoot. okay, so do you know of a work around until it is patched? Should I roll back to an older CLI version? – Olivia Mar 28 '19 at 23:15
  • The fix for the plugin:install has been promoted. The aliases with dots will not be fixed as quickly. I recommend not having dots in your aliases for the meantime. – Amphro Mar 29 '19 at 3:54
0

I ended up having to uninstall and reinstall sfdx. You can see my solution here:

Error: Cannot find module '@oclif/config'

I am going to mark Amphro's answer correct as it is the answer to the post. This answer is just one way of resolving my entire issue.

| improve this answer | |

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.