[Heyykrishnna]

Summary

Clarify that the CLI copies editable component source into the application, while installed components still use their declared dependencies. Replace the stale component count with wording that stays accurate as the catalog grows.

Type of Change

• Documentation

Scope

README.md only; 4 additions and 2 deletions.

Validation

• Checked the installation wording against bin/cli.mjs and the existing installation guide.
• Confirmed only README.md changed and all links and code examples are unchanged.
• git diff --check passed.
• Application tests were not run for this prose-only change.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
component-library	Ready	Preview	Oct 19, 2026 4:19am UTC

[Yash121l]

Looks good. The new wording matches what bin/cli.mjs does, and dropping the hard-coded "59 components" means the README no longer goes stale every time a component is added. Lint, typecheck and the CodeQL analyses pass. The Vercel devclubcompo failure is the account block that also shows on main.

[Yash121l]

@Heyykrishnna this is approved, but main requires verified commit signatures and the commits here are unsigned, so it can't merge yet. Can you re-sign and force-push?

One-time setup (SSH signing):

git config --global gpg.format ssh
git config --global user.signingkey ~/.ssh/id_ed25519.pub
git config --global commit.gpgsign true

Add the same public key on GitHub under Settings → SSH and GPG keys → New SSH key with key type Signing Key. Also make sure the commit email (khandelwalyatharth39@gmail.com) is a verified email on your GitHub account, otherwise the signature shows as unverified.

Then on this branch:

git rebase --exec 'git commit --amend --no-edit -S' origin/main
git push --force-with-lease

Pushing dismisses the current approval (that's a ruleset setting), so I'll re-approve once the commits show Verified. Auto-merge is enabled, so it merges after that.