ENOENT error after uninstalling plugin-packaging

[gsbasso]

Note
Before you submit your issue, make sure that:

• You're using the latest version of Salesforce CLI.
• You've searched both open and closed issues for related posts.
• You've used the doctor command to diagnose common issues.
• You understand that GitHub Issues don't adhere to any agreement or SLA.
  • If you require immediate assistance, use official channels such as Salesforce Customer Support.

Summary

Recently upgraded CLI to 2.74.6 using npm and noticed that plugin-packaging is now part of the core install when previously it had not been (you had to install the plugin separately). As the core version was newer I ran npm uninstall @salesforce/plugin-packaging --global to remove the older version I had been using.

As evidenced by the output of sfdx version --verbose below you can see it is now using the core plugin (in contrast to the community plugin). However, now any command results in the ENOENT message shown (interestingly the numeric after node: is always different).

Functionally everything seems to be working (commands complete successfully) but I cannot figure out where the older plugin-packaging is being referenced. Any ideas?

Steps To Reproduce

1. Install any non-core plugin using npm
2. Uninstall plugin using npm
3. The plugin is still being referenced somewhere, resulting in an ENOENT error displaying for every command

Expected result

After removing non-core plugin no references should remain

Actual result

References to the uninstalled plugin persist and an ENOENT message is displayed when running any command

Additional information

System Information

 (node:24852) [ENOENT] Error Plugin: @salesforce/cli: ENOENT: no such file or directory, open 'C:\Users\blah\AppData\Roaming\npm\node_modules\@salesforce\plugin-packaging\package.json'
 module: @oclif/core@4.2.4
 plugin: @salesforce/cli
 root: C:\Users\blah\AppData\Roaming\npm\node_modules\@salesforce\cli
 See more details with DEBUG=*
 (Use `node --trace-warnings ...` to show where the warning was created)

  CLI Version:
         @salesforce/cli/2.74.6 published 21 days ago (Tue Jan 21 2025)
 
  Architecture:
         win32-x64
 
  Node Version:
         node-v20.12.2
 
  Plugin Version:
         @oclif/plugin-autocomplete 3.2.18 (core)
         @oclif/plugin-commands 4.1.17 (core)
         @oclif/plugin-help 6.2.22 (core)
         @oclif/plugin-not-found 3.2.37 (core)
         @oclif/plugin-plugins 5.4.26 (core)
         @oclif/plugin-search 1.2.19 (core)
         @oclif/plugin-update 4.6.26 (core)
         @oclif/plugin-version 2.2.20 (core)
         @oclif/plugin-warn-if-update-available 3.1.31 (core)
         @oclif/plugin-which 3.2.26 (core)
         @salesforce/cli 2.74.6 (core)
         apex 3.6.8 (core)
         api 1.3.3 (core)
         auth 3.6.87 (core)
         community 3.2.19 (link) C:\Users\blah\AppData\Roaming\npm\node_modules\@salesforce\plugin-community
         data 4.0.1 (core)
         deploy-retrieve 3.17.7 (core)
         info 3.4.32 (core)
         limits 3.3.44 (core)
         marketplace 1.3.7 (core)
         org 5.2.23 (core)
         packaging 2.9.12 (core)
         schema 3.3.46 (core)
         settings 2.4.10 (core)
         signups 2.3.12 (link) C:\Users\blah\AppData\Roaming\npm\node_modules\@salesforce\plugin-signups
         sobject 1.4.49 (core)
         telemetry 3.6.29 (core)
         templates 56.3.35 (core)
         trust 3.7.55 (core)
         user 3.6.6 (core)
 
  OS and Version:
         Windows_NT 10.0.22621
 

[github-actions]

Thank you for filing this issue. We appreciate your feedback and will review the issue as soon as possible. Remember, however, that GitHub isn't a mechanism for receiving support under any agreement or SLA. If you require immediate assistance, contact Salesforce Customer Support.

[github-actions]

Hello @gsbasso 👋 None of the versions of sf you shared match the latest release.

Shared: 2.74.6
Latest: 2.76.7

Update to the latest version of Salesforce CLI (docs) and confirm that you're still seeing your issue.
You can also try the rc and nightly releases! (docs)

After updating, share the full output of sf version --verbose --json

[gsbasso]

Updating to latest CLI produced the same result. I don't believe the issue is related to the version. Somewhere the previous plugin is still being referenced.

{
  "architecture": "win32-x64",
  "cliVersion": "@salesforce/cli/2.74.6",
  "nodeVersion": "node-v20.12.2",
  "osVersion": "Windows_NT 10.0.22621",
  "rootPath": "C:\\Users\\blah\\AppData\\Roaming\\npm\\node_modules\\@salesforce\\cli",
  "shell": "powershell",
  "pluginVersions": [
    "@oclif/plugin-autocomplete 3.2.18 (core)",
    "@oclif/plugin-commands 4.1.17 (core)",
    "@oclif/plugin-help 6.2.22 (core)",
    "@oclif/plugin-not-found 3.2.37 (core)",
    "@oclif/plugin-plugins 5.4.26 (core)",
    "@oclif/plugin-search 1.2.19 (core)",
    "@oclif/plugin-update 4.6.26 (core)",
    "@oclif/plugin-version 2.2.20 (core)",
    "@oclif/plugin-warn-if-update-available 3.1.31 (core)",
    "@oclif/plugin-which 3.2.26 (core)",
    "@salesforce/cli 2.74.6 (core)",
    "apex 3.6.8 (core)",
    "api 1.3.3 (core)",
    "auth 3.6.87 (core)",
    "community 3.2.19 (link) C:\\Users\\blah\\AppData\\Roaming\\npm\\node_modules\\@salesforce\\plugin-community",      
    "data 4.0.1 (core)",
    "deploy-retrieve 3.17.7 (core)",
    "info 3.4.32 (core)",
    "limits 3.3.44 (core)",
    "marketplace 1.3.7 (core)",
    "org 5.2.23 (core)",
    "packaging 2.9.12 (core)",
    "schema 3.3.46 (core)",
    "settings 2.4.10 (core)",
    "signups 2.3.12 (link) C:\\Users\\blah\\AppData\\Roaming\\npm\\node_modules\\@salesforce\\plugin-signups",
    "sobject 1.4.49 (core)",
    "telemetry 3.6.29 (core)",
    "templates 56.3.35 (core)",
    "trust 3.7.55 (core)",
    "user 3.6.6 (core)"
  ]
}

[github-actions]

Hello @gsbasso 👋 None of the versions of sf you shared match the latest release.

Shared: 2.74.6, 2.74.6
Latest: 2.76.7

Update to the latest version of Salesforce CLI (docs) and confirm that you're still seeing your issue.
You can also try the rc and nightly releases! (docs)

After updating, share the full output of sf version --verbose --json

[shetzel]

Recently upgraded CLI to 2.74.6 using npm ...
How old was the version you upgraded from? There was about a 3 week period of time long ago where the packaging plugin was removed from the core bundled plugins and made "JIT" (the plugin installs upon first use). It was moved back to the core bundled plugins and has been that way ever since. Especially if upgrading from a very old CLI version I suggest to completely uninstall the CLI following these docs and install fresh: https://developer.salesforce.com/docs/atlas.en-us.sfdx_setup.meta/sfdx_setup/sfdx_setup_uninstall.htm

[gsbasso]

I used sf doctor to help me figure out where the plugin was being referenced. Turns out it was in a file named package.json in the folder %userprofile%\AppData\Local\sf. Once I removed the reference the problem went away. I`ve copied the original file (before removing reference) below.

My feeling is I needed to first somehow unlink the package before uninstalling (after I originally installed I ran sf plugins link).

{
  "name": "@salesforce/cli",
  "dependencies": {},
  "oclif": {
    "plugins": [
      {
        "name": "@salesforce/plugin-packaging",
        "root": "C:\\Users\\blah\\AppData\\Roaming\\npm\\node_modules\\@salesforce\\plugin-packaging",
        "type": "link"
      },
      {
        "name": "@salesforce/plugin-community",
        "root": "C:\\Users\\blah\\AppData\\Roaming\\npm\\node_modules\\@salesforce\\plugin-community",
        "type": "link"
      },
      {
        "name": "@salesforce/plugin-signups",
        "root": "C:\\Users\\blah\\AppData\\Roaming\\npm\\node_modules\\@salesforce\\plugin-signups",
        "type": "link"
      }
    ],
    "schema": 1
  },
  "private": true
}

[shetzel]

Glad you were able to find the cause and that sf doctor helped!