snpmv2026.1.7

Troubleshooting

Common issues and how to fix them

Solutions to common problems with snpm.

Installation Issues

Rust Not Installed

Problem: Can't build snpm from source.

Solution: Install Rust from rustup.rs:

curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh

Restart your terminal and try again.

Build Fails

Problem: Compilation errors when building.

Solution: Update Rust to the latest version:

rustup update stable

Then rebuild:

cargo install --path snpm-cli

Binary Not in PATH

Problem: snpm: command not found after installation.

Solution: Add Cargo's bin directory to your PATH:

# Add to ~/.bashrc or ~/.zshrc
export PATH="$HOME/.cargo/bin:$PATH"

Restart your terminal.

Runtime Issues

Permission Denied

Problem: Permission errors when installing packages.

Solution: Check that you have write access to the global store. The location is platform-specific:

  • macOS: ~/Library/Application Support/io.snpm.snpm
  • Linux: ~/.local/share/snpm
# Linux
ls -la ~/.local/share/snpm

If needed, fix permissions:

# Linux
sudo chown -R $USER ~/.local/share/snpm

Lockfile Out of Sync

Problem: --frozen-lockfile fails in CI.

Solution: The lockfile needs updating. Locally run:

snpm install
git add snpm-lock.yaml
git commit -m "Update lockfile"

Package Not Found

Problem: snpm can't find a package.

Solution: Check the package name and version:

# Verify package exists
npm view <package-name>

If using a private registry, ensure you're authenticated:

snpm login --registry https://npm.mycompany.com

Slow Installs

Problem: Installs are slower than expected.

Solution:

  1. Check your network connection
  2. Increase registry concurrency:
export SNPM_REGISTRY_CONCURRENCY=128
  1. Ensure the global store isn't on a slow disk

Workspace Not Detected

Problem: snpm doesn't recognize your workspace.

Solution: Ensure you have snpm-workspace.yaml or pnpm-workspace.yaml in the root:

snpm-workspace.yaml
packages:
  - 'packages/*'
  - 'apps/*'

Catalog Not Working

Problem: Catalog versions aren't being used.

Solution: Ensure snpm-catalog.yaml is in the workspace root and you're using the correct syntax:

package.json
{
  "dependencies": {
    "react": "catalog:"
  }
}

Getting Help

If you're still stuck:

GitHub Issues - Report bugs at github.com/binbandit/snpm/issues

When reporting issues, include:

  • snpm version (snpm --version)
  • Operating system
  • Steps to reproduce
  • Error messages

On this page