Plugin Environment
FreshArchitecture Overview
Stream Deck plugins run entirely on the user's local machine. All hardware communication is managed by the Stream Deck app.
Runtime Layers
| Layer | Runtime | Purpose |
|---|---|---|
| Backend | Node.js | Main plugin logic, event handling, API calls |
| Frontend | Chromium + DOM | Property Inspector UI for user configuration |
Current Runtime Versions (Stream Deck 7.3)
| Component | Version |
|---|---|
| Node.js | 20.20.0, 24.13.1 |
| Chromium | 130.0.0.0 |
Auto-Updates
From Stream Deck 7.1, Node.js versions are automatically updated to the latest versions supported by Stream Deck.
Manifest File
The manifest (*.sdPlugin/manifest.json) is the central configuration defining your plugin:
- Plugin metadata (name, author, version)
- Actions and their properties
- SDK version and compatibility
- Supported operating systems (macOS 10.15+, Windows 10+)
- Node.js configuration
Plugin Lifecycle
Stream Deck manages:
- Plugin initialization and startup
- Automatic failure recovery and restart
- Communication between backend and frontend layers
Security
Plugins distributed via Marketplace can use DRM protection and the Secrets API for handling sensitive credentials securely.
Verification Checklist
- [ ] Understand two-layer architecture (Node.js backend + Chromium frontend)
- [ ] Know where the manifest file lives (
.sdPlugin/manifest.json) - [ ] Understand the plugin lifecycle and event flow