Skip to main content

Node.js Plugin Guide

Fastest route for most developers

If you are comfortable with JavaScript or TypeScript, the Node.js SDK is the quickest way to build a custom Logi Options+ plugin.

1. Current public status​

The current Logitech docs describe the Node.js SDK as:

  • available for Windows and macOS,
  • beta for plugin developers,
  • TypeScript-first by default,
  • compatible with Logi Options+ and Logi Plugin Service.

The docs also note:

  • Node.js plugin support was new in Plugin API 6.2.3,
  • macOS support was added in Plugin API 6.3.

2. Create a plugin​

npx @logitech/plugin-toolkit create my-logi-plugin
cd my-logi-plugin
npm install
npm run watch

The official docs say:

  • the scaffold uses TypeScript by default,
  • add --javascript if you want plain JavaScript,
  • npm run watch builds, links, and reloads the plugin,
  • npm run link links a non-watch build,
  • npm run unlink removes the linked plugin,
  • npm run build:pack builds a distributable .lplug4.

3. Why Node.js is a good fit​

Choose Node.js when:

  • the plugin talks to REST or WebSocket APIs,
  • you want fast iteration,
  • you already live in TypeScript,
  • you want npm packages,
  • the integration is mostly service orchestration.

4. Good plugin ideas​

  • trigger CI/CD actions,
  • open or switch tools,
  • drive Philips Hue or BusyLight from Actions Ring,
  • integrate ticketing or chat systems,
  • trigger internal HTTP endpoints,
  • control local helper apps.

5. Typical architecture​

my-logi-plugin/
├── src/
│   ├── actions/
│   ├── services/
│   ├── assets/
│   └── plugin.ts
├── dist/
└── package.json

Keep plugin actions small and move service logic into separate modules.

6. When Node.js is the wrong choice​

Use C# instead when:

  • the integration depends on mature .NET code,
  • you need tighter Windows desktop integration,
  • the team is strongly C#-oriented,
  • the plugin needs a more native desktop architecture.