The official Node.js SDK for creating Stream Deck plugins.
npm install @elgato/streamdeckbash
npm install -g @elgato/cli@latest
`
2. Once installed, run the create command to initialize the creation wizard.
`bash
streamdeck create
`
š File Structure
After creating a plugin with streamdeck create you'll be provided with a local environment for building a plugin.
`
/
āāā *.sdPlugin/
ā āāā bin/
ā āāā imgs/
ā āāā logs/
ā āāā ui/
ā ā āāā increment-counter.html
ā āāā manifest.json
āāā src/
ā āāā actions/
ā ā āāā increment-counter.ts
ā āāā plugin.ts
āāā package.json
āāā rollup.config.mjs
āāā tsconfig.json
`
The package.json provides two scripts for building the plugin.
- npm run build - builds the plugin.
- npm run watch - continuously watches for changes, and hot-reloads the plugin after build.
šļø Actions
Actions are the star of the show and enable users to interact with your plugin. Actions are represented as classes that inherit from SingletonAction, enabling your plugin to receive events from Stream Deck, for example key down, dial rotate, etc.
The following is an example of an action that listens for the keyDown event, and then sets the title of the source action.
`typescript
import { action, KeyDownEvent, SingletonAction } from "@elgato/streamdeck";
@action({ UUID: "com.elgato.hello-world.say-hello" })
export class SayHelloAction extends SingletonAction {
/**
* Listen for the key down event that occurs when a user presses
* a Stream Deck button, and change the title of the action.
*/
async onKeyDown(ev: KeyDownEvent) {
await ev.action.setTitle("Hello world");
}
}
`
š Debugging
Plugins can be debugged using any Node.js debugger, for example Visual Studio Code, Chrome, etc., and by default will have debugging enabled when created with the Stream Deck CLI streamdeck create command.
You can configure debugging within the manifest's Node.js configuration.
`jsonc
{
// ...
"Nodejs": {
"Version": "20",
"Debug": "enabled"
},
}
`
There are four available options when configuring the Debug property within the manifest:
- "enabled" - the plugin will run with --inspect allowing debuggers to connect.
- "break" - the plugin will launch with --inspect-brk and will await a debugger attaching before running.
- string - a collection of CLI arguments supplied to the plugin.
- undefined - debugging is disabled.
> When running the plugin in either debug mode "enabled" or "break", a random available port will be allocated to the debug listener each time the plugin launches. If you wish to listen on a specific port, the Debug value can be set to a string of CLI arguments, for example to listen on port 12345, the Debug value would be --inspect=127.0.0.1:12345`.