Kit MarketplaceSign in with GitHub

Publish it

Publishing is from your terminal, with the kit command. Each version is read by a person before it's listed.

Get the kit command

The marketplace serves it, one small file, with nothing else to install. It needs Node 20 or newer.

npm install -g https://market.taile506df.ts.net/kit.tgz

Or run it each time without installing: npx https://market.taile506df.ts.net/kit.tgz in place of kit below.

Sign in once

kit market login

It shows a code and a link. Open the link, sign in with GitHub, check the code matches, and press Allow. Your terminal keeps a token in ~/.config/kit/market.json, readable by you alone. Your plugins lists your signed-in terminals; revoke one there, or with kit market logout.

Send a version

kit publish ./ticket-numbers.kit-code.json

It checks the file as Kit does, then sends it with its readme and the pictures it names, read from beside it. Before it reaches anyone, the marketplace runs its code once in Kit’s sandbox: it must load, and set each hook it declares.

  • Its link is made from its name (/p/ticket-numbers); --slug picks another.
  • Its version goes up by one each time; --version 1.2.0 picks one, and it can’t go back.
  • --readme README.md sends that file as its readme.

Review

Each version waits for a person to read its code and what it asks for. You’ll see where it stands on Your plugins and with kit market plugins. If changes are asked for, the note says what to change: fix it, and send a new version. What we look for is in What we review.

Once it’s listed, Kits that read the marketplace show it in their store, and Kits that added an earlier version are offered the new one. Its new code still waits for their approval.

In CI

KIT_MARKET_TOKEN gives a token without signing in, and KIT_MARKET_URL another marketplace.