The Node.js process that runs Escalated plugins.
Your backend's bridge starts it and talks to it over JSON-RPC 2.0 on stdio.
Website · Docs · Cloud · Releases
A plugin written with the Plugin SDK is all the runtime needs:
import { definePlugin } from '@escalated-dev/plugin-sdk'
export default definePlugin({
name: 'my-plugin',
version: '1.0.0',
actions: {
'ticket.created': async (event, ctx) => {
ctx.log.info('New ticket!', event)
},
},
})
It finds plugins in node_modules/@escalated-dev/plugin-*, routes hooks to them, and proxies their ctx.* calls back to your backend.
|
Your backend's bridge starts it on the first hook and restarts it with backoff after a crash. While it is down, filters return values unchanged. |
|
Loading
|
Dispatch
|
Resilience (via the bridge)
|
|
Protocol
|
Active plugins
|
Real-time
|
npm install @escalated-dev/plugin-runtimeInstall it next to the plugins you want to use. Your backend's bridge spawns it, so you don't run it yourself. See installation and usage.
- Installation and usage · Architecture and broadcasting · Protocol
- Releasing this package
- Plugin SDK for writing plugins
- Escalated docs · Docs source · Shared frontend
MIT. Copyright (c) Escalated.dev. See LICENSE.
