Skip to main content
Everything the market gets from you goes through spd. These commands work from any folder inside a project, and read the package name and version from its manifest.json. Writing code: spd new, spd watch, spd build and the rest are on Getting started.

​
Account

​
login


Opens spurdoverse.app/cli with a code; press Allow there and the terminal gets a key. The request lives 10 minutes. The key is stored in the Windows Credential Manager and doesn’t expire. SPD_TOKEN overrides the stored key, for CI. Create one for it in the editor: Branches & versions → How to release → CLI keys. An account has 10 keys at most, the ones spd login made included: revoke old ones there.
The Allow page asks to confirm your email first if it isn’t confirmed. Without that, there’s no key.

​
logout and whoami


spd logout revokes the stored key and removes it. spd whoami prints the account, the key’s id, its scopes and your package scope (@yournick); it exits with code 1 when you’re not signed in.

​
Versions

​
publish


Checks the project, uploads its sources and follows the server build to the end. The version is the one in manifest.json; the release notes are --notes, or the section for this version in CHANGELOG.md.
The first publish creates the market item as a draft and prints the link to its editor. The whole walkthrough: Publishing a script.

​
version


Raises the version in manifest.json and package.json, as npm version does.
A prerelease becomes its release: 1.5.0-beta.2 → 1.5.0 with minor or patch.

​
rollback


Points a branch (stable by default) at a version published earlier, from any branch. Nothing is rebuilt or deleted: buyers on that branch get that version from now on, as a normal update.

​
promote


Puts a published version on another branch as it is, without a rebuild. Typically: a beta that proved itself goes to stable. Stable only takes releases, so publish 1.5.0 to beta first, not 1.5.0-beta.3.

​
yank


Withdraws a version: new buyers don’t get it, and the registry marks it deprecated with your reason. Branches that pointed at it move to the newest live version of their branch. The number is never published again. Only a moderator can delete a version.

​
Libraries and forks

​
add


npm install plus a warning when a spurdo! library needs ffi or filesystem: its permissions become your script’s, and your versions go to a moderator.

​
fork


Makes your own project from an open script or library you own: renamed to your scope, displayName "<original> (моя версия)", version 1.0.0, and "forkOf" in the manifest naming the original. It gets no automatic updates. You can publish a fork on the market only if the original’s author allows it; otherwise spd publish refuses with fork-not-allowed. Keep such a copy local.

​
upstream


In a fork. spd upstream (or spd fork status) says whether the original has a new version, diff shows its changes since the version your fork is based on, apply merges them into your files: three-way, with conflict markers where you both changed the same lines.

​
Checks

​
doctor


Checks Node.js, npm, the login, the scripts directory, the shared types and the current project (manifest, bundling). Run it first when spd publish fails before uploading.