npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@radicalbit/helicon-node-sdk

v4.0.2

Published

This module contains the NodeJs sdk for Helicon _publish_ and _subscribe_ operations.

Readme

Helicon node sdk

This module contains the NodeJs sdk for Helicon publish and subscribe operations.

Helicon is a simple, scalable, robust, code-free and generic platform to enable and productise the next generation of "online modified", real-time event stream ML/AI models.

Publish

publish operations can be performed by using the HeliconWriteClient class exported by the library.

To initialize a new HeliconWriteClient instance, the user is tasked to fill all the required parameters of the constructor such as:

  • The address where the Host is located
  • The port to which the Host is bind (OPTIONAL: default value is 443, can be omitted)
  • The http protocol to which the Host is available (OPTIONAL: default value is https, can be omitted)
  • The rest of the authentication parameters such as Client Secret, clientId and Tenant

Each of these parameters can be found (pre-filled) in the "Setup" section of a newly created stream.

After a HeliconWriteClient has been initialized, the user can send data to the stream thanks to the write(streamName, payload) method; An usage example is shown below:

const { HeliconWriteClient } = require("@radicalbit/helicon-node-sdk");

const host = "<host>";
const port = 0;
const clientId = "<client-id>";
const clientSecret = "<client-secret>";
const tenant = "<tenant-name>";
const protocol = "<http-protocol>";

const payload = {
	"name": "record",
	"temperature": "29"
};

const heliconWriteClient = new HeliconWriteClient(host, clientId, clientSecret, tenant, port, protocol);

heliconWriteClient.write("<streamName>", payload).then(
	() => console.log("payload published!"),
	(errorMessage) => console.error(errorMessage)
);

In case port and/or protocol are equal to the default values they can be omitted in this way: Both omitted

const heliconWriteClient = new HeliconWriteClient(host, clientId, clientSecret, tenant);

Protocol omitted

const heliconWriteClient = new HeliconWriteClient(host, clientId, clientSecret, tenant, port);

Port omitted (must be set as undefined because of the order of the optional fields)

const heliconWriteClient = new HeliconWriteClient(host, clientId, clientSecret, tenant, undefined, protocol);

Subscribe

subscribe operations can be performed by using the HeliconSubscribeClient class exported by the library.

To initialize a new HeliconSubscribeClient instance, the user is tasked to fill all the required parameters of the constructor such as:

  • The address where the Host is located
  • The port to which the Host is bind (OPTIONAL: default value is 443, can be omitted)
  • The http protocol to which the Host is available (OPTIONAL: default value is https, can be omitted)
  • The rest of the authentication parameters such as Client Secret, clientId and Tenant

Each of these parameters can be found (pre-filled) in the "Setup" section of a newly created stream.

After a HeliconSubscribeClient has been initialized, the user can receive the events from the stream thanks to the subscribe(streamDisplaName) method; An usage example is shown below:

const { HeliconSubscribeClient } = require("@radicalbit/helicon-node-sdk");

const host = "<host>";
const port = 0;
const clientId = "<client-id>";
const clientSecret = "<client-secret>";
const tenant = "<tenant-name>";
const protocol = "<http-protocol>";

const heliconSubscribeClient = new HeliconSubscribeClient(host, clientId, clientSecret, tenant, port, protocol);

heliconSubscribeClient.subscribe("<streamName>").onData(
  (data) => console.log(data)
);

In case port and/or protocol are equal to the default values they can be omitted in this way: Both omitted

const heliconSubscribeClient = new HeliconSubscribeClient(host, clientId, clientSecret, tenant);

Protocol omitted

const heliconSubscribeClient = new HeliconSubscribeClient(host, clientId, clientSecret, tenant, port);

Port omitted (must be set as undefined because of the order of the optional fields)

const heliconSubscribeClient = new HeliconSubscribeClient(host, clientId, clientSecret, tenant, undefined, protocol);

Support

We're always happy to help with any other questions you might have! Send us an email.