Problem: Install source confusion: npm same-name package / other cc-switch projects —— Trove problem library

What you will run into

Searching "cc-switch" installs the wrong package - npm hosts a same-name package, but it is not this project; or after installing there is no cc-switch command at all.

Key fact: this project is a Tauri desktop app distributed via GitHub Release (deb/AppImage/rpm/win/mac), with no npm package.

Why this happens

This project = farion1231/cc-switch (Tauri desktop app), distributed via GitHub Release assets; the same-name cc-switch on npm is a different project. When you search "cc-switch", npm results rank first, so it's easy to install the wrong one.

"Same package name" does not mean "same thing" — the distribution channel is part of a project's identity: a Tauri desktop app ships via GitHub Release assets (deb/AppImage/etc.), while npm is the JS package ecosystem;

the two mechanisms are completely different.

npm install cc-switch installs the same-name JS package, which provides no cc-switch command — so "command not found after install" is the hard signal that you installed the wrong source.

Conversely, a correct install has two checkable hard evidences: the command surface (cc-switch --version prints) and the package metadata (Package/Version/Maintainer fields in dpkg-deb -I).

Search-result ranking (npm first) is just a traffic entrance, not identity evidence; identity is judged by "which ecosystem's install command you used + whether the resulting command surface/metadata matches".

Step by step

1. Trust the source — Required

• Repo: farion1231/cc-switch;
• Command/entry: cc-switch or the desktop icon;
• Always install from GitHub Release assets (or this marketplace's recorded deb path); do not npm install cc-switch.

2. Verify after installing — Required

cc-switch --version

command not found -> wrong source installed (the npm same-name package has no such command); uninstall and reinstall the Release asset.

3. Check the package metadata — Required

dpkg-deb -I cc-switch.deb | head -8

Package: cc-switch / Version: 3.20.0 / Maintainer: Jason Young - only if these match is it this project.

How to confirm it works

cc-switch --version && which cc-switch

The command exists and prints a version = success (measured: the command works after installing the Release deb).

Other environments

Symptom

Searching "cc-switch" installs the wrong package (a same-name npm package that isn't this project), or there is no cc-switch command after installing.

Cause

This project = farion1231/cc-switch (Tauri desktop app), distributed via GitHub Release (deb/AppImage/rpm/win/mac), no npm package; the npm same-name package is another project.

Solution

1. Trust the repo: farion1231/cc-switch; command/entry = cc-switch or the desktop icon.
2. Always install from GitHub Release assets (or this marketplace's recorded deb path); don't npm install cc-switch.