DocsInstall

CLI messages

Every answer UpFork's registry can give the shadcn CLI, what it means, and what to do about it.

Updated This page as Markdown

When UpFork's registry can't hand the shadcn CLI a product, it answers with a short title and a sentence saying why and what to do, and the CLI prints both. Here is every title it can print, what it means, and what to do.

Before UpFork is asked

The CLI checks one thing itself: a @upfork install needs UPFORK_TOKEN set, since components.json sends it. Without it, the CLI stops with Registry "@upfork" requires the following environment variables. Put your token in .env.local (Install components), or, for a free product, install it by its address instead: npx shadcn@latest add https://upfork.dev/r/<name>.json, no token needed.

Your token

TitleWhenWhat to do
Token requiredThe command sent no token (installing by the product's address, or components.json doesn't pass it on), and the product isn't one that installs without: it's paidFollow Install components: create a token, put it in .env.local as UPFORK_TOKEN, and add UpFork to components.json. The message also says what the product needs: the buyer's token for a paid one. Free products never ask for a token.
Invalid tokenThe token isn't one of UpFork's (they start with upf_ and are 47 characters long), or it was deleted or mistyped. A token that's sent must work, even for a free productCopy it again, or create a new one, and put it in .env.local as UPFORK_TOKEN.
Account blockedThe account the token belongs to is blocked, so its tokens don't workContact UpFork to ask why.

The product

TitleWhenWhat to do
Not foundThere's no product called <name>. Names are lower-case letters, digits and hyphens: the last part of the product's addressCheck the name against the product's page, https://upfork.dev/products/<name>.
No longer availableThe product isn't on sale any moreIf you bought it, its code stays yours: download it from your purchases.
Not installableIt's a full-stack projectIt's downloaded, not installed: get it from its page (Templates and downloads).
Not a shadcn itemIt's plain HTML, CSS and JS, or a React Native component for Expo apps, not a shadcn componentDownload it, or copy its code, from its page. A mobile component goes into an Expo app: Install mobile components.
No codeIt's delivered as downloads onlyGet it from its page.

These are checked before your token, so you see them even with no token set up.

Buying

TitleWhenWhat to do
Not boughtThe product is paid, and the token's account hasn't bought itBuy it on its page, or use the token of the account that bought it, then run the command again.

Too many, or no answer

TitleWhenWhat to do
Too many requestsToo many installs from your address in a short timeWait a minute, then run the command again.
Registry unavailableUpFork's registry can't be reached right nowTry again in a minute.

For developers

If you sell on UpFork, two more can appear while you install your own product:

  • Not on sale: your product is a draft or archived, or UpFork took it off the site. Publish it in its editor's Publish step, then run the command again.
  • Not found for a draft is what everyone else sees; you see Not on sale instead.

To try an install before publishing, use the try link from your product's editor: see Selling on UpFork.