
Security News
TeamPCP and BreachForums Launch $1,000 Contest for Supply Chain Attacks
TeamPCP and BreachForums are promoting a Shai-Hulud supply chain attack contest with a $1,000 prize for the biggest package compromise.
@backstage/plugin-signals-node
Advanced tools
Welcome to the Node.js library package for the signals plugin!
Signals plugin allows backend plugins to publish messages to frontend plugins.
In packages/backend/index.ts, add the signals backend:
backend.add(import('@backstage/plugin-signals-backend'));
To use signals in your plugin, add it as a dependency to my-plugin/plugin.ts:
import {
coreServices,
createBackendPlugin,
} from '@backstage/backend-plugin-api';
import { signalsServiceRef } from '@backstage/plugin-signals-node';
export const myPlugin = createBackendPlugin({
pluginId: 'my-plugin',
register(env) {
env.registerInit({
deps: {
httpRouter: coreServices.httpRouter,
signals: signalsServiceRef,
},
async init({ httpRouter, signals }) {
httpRouter.use(
await createRouter({
signals,
}),
);
},
});
},
});
Add SignalService to your plugin environment in packages/backend/src/types.ts:
import { SignalsService } from '@backstage/plugin-signals-node';
export type PluginEnvironment = {
// ...
signals: SignalsService;
};
Add it also to your makeCreateEnv to allow access from the other plugins:
import {
SignalsService,
DefaultSignalsService,
} from '@backstage/plugin-signals-node';
import { DefaultEventBroker } from '@backstage/plugin-events-backend';
function makeCreateEnv(config: Config) {
// ...
const eventBroker = new DefaultEventBroker(root.child({ type: 'plugin' }));
const signalsService = DefaultSignalsService.create({
eventBroker,
});
return (plugin: string): PluginEnvironment => {
const logger = root.child({ type: 'plugin', plugin });
return {
logger,
eventBroker,
signals: signalsService,
// ...
};
};
}
To allow connections from the frontend, you should also install the @backstage/plugin-signals-backend.
Once you have both of the backend plugins installed, you can utilize the signal service by calling the
publish method. This will publish the message to all subscribers in the frontend. To send message to
all subscribers, you can use broadcast type:
// Periodic sending example
setInterval(async () => {
await signals.publish({
recipients: { type: 'broadcast' },
channel: 'my_plugin',
message: {
message: 'hello world',
},
});
}, 5000);
To receive this message in the frontend, check the documentation of @backstage/plugin-signals and
@backstage/plugin-signals-react.
Other way to send signals is to utilize the EventBroker directly. This requires that the payload is correct for it
to work:
eventBroker.publish({
topic: 'signals',
eventPayload: {
recipients: { type: 'user', entityRef: 'user:default/user1' },
message: {
message: 'hello world',
},
channel: 'my_plugin',
},
});
FAQs
Node.js library for the signals plugin
We found that @backstage/plugin-signals-node demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 3 open source maintainers collaborating on the project.
Did you know?

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Security News
TeamPCP and BreachForums are promoting a Shai-Hulud supply chain attack contest with a $1,000 prize for the biggest package compromise.

Security News
Packagist urges PHP projects to update Composer after a GitHub token format change exposed some GitHub Actions tokens in CI logs.

Research
GemStuffer abuses RubyGems as an exfiltration channel, packaging scraped UK council portal data into junk gems published from new accounts.