Skip to main content

Troubleshooting

Login does not complete​

  • confirm browser sign-in succeeded
  • confirm the account is workspace-enabled
  • retry the authorization flow:
package-ninja login

Policy fetch fails​

  • validate connectivity to the control-plane URL
  • inspect local auth state:
package-ninja auth status
  • clear and re-authenticate if needed:
package-ninja logout
package-ninja login

Local runtime residue​

Use full reset only for recovery:

package-ninja factory-reset --yes

Command blocked unexpectedly​

  • read the CLI blocking reason
  • inspect the matching event in the dashboard audit stream
  • verify the rule source (workspace, team, user, or global)
  • if emergency continuity is needed, use the approved break-glass path with audit trail

Node runtime mismatch​

Package Ninja tooling expects Node 22+ for consistent dashboard, docs, and functions behavior.

Check version:

node -v
npm -v

If needed, switch with nvm (Windows):

nvm install 22.17.1
nvm use 22.17.1
node -v