Skip to main content

TagadaPay Plugin CLI

Latest Version

v3.0.3@tagadapay/plugin-cli
A command-line tool for deploying React apps, static websites, and plugins on TagadaPay with routing, domain management, and instance management.
The CLI installs two binary aliases: tgd (short) and tgdcli (long). All examples below use tgd.

Quick Start

1

Login

Opens your browser for secure authentication. Defaults to production.
2

Deploy your plugin

The CLI reads plugin.manifest.json, creates a ZIP of your dist/ folder, uploads it, and deploys.

Interactive Mode

The easiest way to manage everything — deploy, mount, install, manage domains:
Interactive mode provides store selection, config variant picking, real-time upload progress, and guided workflows.

Commands

Authentication

Deploy

--overwrite permanently deletes the existing deployment (record, instances, routes) and replaces it. This is not reversible.
After deploying, the CLI auto-syncs config templates if a config/ folder exists (presets, schema, uiSchema).

Archive

Create a local ZIP without deploying:

List

Instance Management

Domain Management

Domain commands authenticate via your login session. They do not require --store-id.

Plugin Manifest

Every plugin requires a plugin.manifest.json. The CLI validates it before deploying.

Required Fields

All Manifest Fields

Page Features

Simple string features:
Features with requirements (for pages that need data):
Feature types: landing, checkout, thankyou, product-page, catalog, upsell, post-purchase, static Requirements: payment, shipping, customer, order, cart, inventory

Environments

The CLI supports three built-in environments: You can also pass a custom URL:

Workflow Examples

Deploy & Mount

1

Build your plugin

2

Deploy

Note the deployment ID from the output.
3

Install (create instance)

Select the deployment, optionally configure it.
4

Mount to alias

Select the instance and choose an alias path.

Update a Plugin

A/B Testing

Deploy two variants and mount them via the A/B testing API:
Then configure split testing via the API or CRM.

Custom Domain

Troubleshooting

Ensure plugin.manifest.json exists in your current directory and is valid JSON:
Build your plugin before deploying:
A deployment already exists for this plugin ID + version. Either:
  • Bump the version in your manifest
  • Use --overwrite to replace the existing deployment
DNS can take up to 48 hours to propagate. Check status:

Verbose Mode

For detailed API request/response logs:

Support