Remove the cct binary
Requested by Daniel · project thread
What this PR does
Removes the cct entry from bin in both package.json files and their lockfile roots. This implements Daniel's decision on question 16 of the traction plan (initiative 6, item 6).
cct only worked after a global install, and npx cct never ran it, because npm downloads the unrelated cct package owned by another account instead. With this change the package no longer claims that name.
Anyone who ran cct from a global install has to switch to claude-code-templates. The CHANGELOG entry under Unreleased says so. The legacy static site (docs/js/script.js) also showed cct --<type> as the usage line, and it now shows npx claude-code-templates@latest.
This takes effect in the next npm release (1.33.1 or 1.34).
Type
- New component
- Change to an existing component
- CLI (
cli-tool/src,cli-tool/bin) - Website (
dashboard/) - Docs or other
How I tested it
npm test(root) passes.npm packand an install of the tarball in a scratch folder:node_modules/.binnow has onlyclaude-code-templates, and--versionworks.
Generated by Claude Code
Summary by cubic
Removes the cct binary from the CLI package and the legacy docs usage line, since npx cct never resolved to this package (npm installs an unrelated cct package) and cct only worked after a global install.
Affects the CLI (cli-tool/package.json) and docs site (docs/js/script.js).
- Removes
cctfrom thebinmaps in the root andcli-toolpackage.json files and lockfiles. - Updates the docs site usage line to
npx claude-code-templates@latest --<type>. - Adds a CHANGELOG entry directing global-install users to
claude-code-templates.
No new components were added, so the catalog (docs/components.json) needs no regeneration, and no new environment variables or secrets are required.