@pklaschka/xd-deploy NPM

xd-deploy

npx @pklaschka/xd-deploy <command>

A toolbelt for easy and quick, iterative plugin development for Adobe XD allowing quick deployment to multiple test machines, making testing your plugin super easy.

GIF demonstrating the tool

Installation

npm install -g @pklaschka/xd-deploy

yarn add -g @pklaschka/xd-deploy

resulting in the xd-deploy binary getting addet to the PATH.

Concept

There are three parts:

The "Server" serves the plugins to test machines from a folder. This can, but doesn't have to be the development machine, but must be accessible via the network. The server can be any machine, i.e., run under macOS, Windows or Linux.
The "Dev Client" can get used when the server isn't the development machine. It automates "deploying" to the server, which then distributes the plugin to all clients. The developer client can also run on any machine, allowing XD plugin development on Linux machines, too.
The "Clients" run on test machines with XD installed. It connects to the server and keeps all plugins in sync with the server version. Furthermore, whenever an update for a plugin gets distributed by the server, the client automatically installs it and Reloads the plugins inside XD, making it extremely easy to test after making changes. The client can get run on macOS, WIndows, and the Windows Subsystem for Linux (WSL). It requires XD to be installed on the machine.

Deployment examples

Example 1 (minimalistic)

In the first example, server and client run on the same machine. This would be a fesible workflow when you, e.g., want to work on a Linux machine and only test on Windows (no, why do you say I'm talking about myself? :stuck_out_tongue_winking_eye:).

example deployment diagram 1

Example 2 (rather complex)

The second example features two clients (representative of any number of clients) for testing machines, e.g., one running Windows and the other macOS, a central server (this may even be accessible via the WWW, meaning remote plugin development becomes possible) and multiple dev-clients deploying different plugins. This could be the workflow of an agency working on plugins, for example:

example deployment diagram 2