xanosdk marketplace commands find one and change what your project has
installed.
Find one
The read commands need no login:details prints the tables, endpoints and functions the add-on adds, what you supply yourself,
and the registration to paste into xano/index.ts. --prompt prints the publisher’s wiring
instructions for a coding agent instead:
Install a workspace add-on
A workspace add-on adds def objects to the backend you deploy.@xano-sdk/auth, for
example, adds a user table and auth/signup, auth/login and auth/me endpoints.
xano/index.ts. Its register function takes your workspace() and returns
it, so you chain your own objects after it:
xano/routes.gen.ts like your own.
Install a toolchain add-on
A toolchain add-on extends the CLI instead and adds nothing to the workspace, so there is nothing to register.@xano-sdk/zod writes runtime validators into routes.gen.ts, and
@xano-sdk/xanoscript writes a XanoScript file per object on every export.
install asks the add-on’s questions and stores your answers in package.json under the
"xanosdk" key. To answer them again:
install prints which kind arrived, because the next step differs.
Remove one
remove uninstalls the package and drops its settings and the lines it contributed. Use it
rather than npm uninstall, which leaves those behind. It refuses to remove a workspace add-on
your backend still imports and names the files: drop the import and registration first.
Why not npm install
marketplace install runs npm for you and adds three things: it refuses to run outside a
project, it refuses a name the marketplace does not list (exit 8), and it configures any
toolchain add-on that arrived. You can also scaffold a project with add-ons already installed
and registered:
Next
- Every verb’s behavior, peer ranges and the reconcile rules: marketplace reference.
- Write your own add-on: module contract.
- Use zod with your routes: Typed frontend.