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

@novominteractive/ase-transport-aws-iot

v1.0.0-rc.2

Published

AWS IoT transport for [`@novominteractive/anyware-stateless-client`](https://www.npmjs.com/package/@novominteractive/anyware-stateless-client). Connects to AWS IoT Core over MQTT via WebSocket using a custom authorizer.

Readme

@novominteractive/ase-transport-aws-iot

AWS IoT transport for @novominteractive/anyware-stateless-client. Connects to AWS IoT Core over MQTT via WebSocket using a custom authorizer.

Installation

yarn add @novominteractive/anyware-stateless-client @novominteractive/ase-transport-aws-iot

Peer dependencies

| Package | Required | Notes | |---------|----------|-------| | @novominteractive/anyware-stateless-client | Yes | Core client |

Usage

import ASEClient from '@novominteractive/anyware-stateless-client';
import { AwsIotTransport } from '@novominteractive/ase-transport-aws-iot';

const client = new ASEClient({
  licenseKey: 'your-license-key',
  rootTopic: 'myProject/production',
  transport: new AwsIotTransport({
    authorizerName: 'AnywareAuthorizer-production',
    endpoint: 'xxxxx.iot.ca-central-1.amazonaws.com',
  }),
});

await client.connect(signedJwt);

Both authorizerName and endpoint are optional — they default to the Novom production values.

Token format

The AWS IoT transport expects a signed HS256 JWT. Use signAwsIotToken from @novominteractive/anyware-server-auth to issue one server-side:

import { signASEToken } from '@novominteractive/anyware-server-auth';

const token = await signASEToken({
  transport: 'aws-iot',
  payload: {
    subscribeTopics: ['myProject/events'],
    publishTopics:   ['myProject/commands'],
    ttlSeconds: 3600,
  },
  config: {
    secretKey:  process.env.SECRET_KEY!,
    licenseKey: 'your-license-key',
  },
});

The license key and the secret key will be issued by Novom Interactive.

Configuration

interface AwsIotTransportConfig {
  /**
   * Name of the AWS IoT custom authorizer Lambda.
   * Defaults to `'AnywareAuthorizer-production'`.
   */
  authorizerName?: string;
  /**
   * AWS IoT endpoint (`<prefix>.iot.<region>.amazonaws.com`).
   * Defaults to the Novom production endpoint.
   */
  endpoint?: string;
  /** Lifecycle event callbacks for the MQTT connection. */
  connectionHandlers?: IotConnectionHandlers;
  /**
   * MQTT last will message, published by AWS IoT if the client disconnects
   * unexpectedly. The connection token is injected under the `token` key
   * at connect time.
   */
  lastWill?: LastWillConfig;
}

interface IotConnectionHandlers {
  onInterrupt?: (error: CrtError) => any;
  onResume?: (returnCode: number, sessionPresent: boolean) => any;
  onDisconnect?: () => any;
  onError?: (error: CrtError) => any;
}

interface LastWillConfig {
  /** Full topic path for the last will message. */
  topic: string;
  /** Extra fields merged into the payload. The `token` key is reserved. */
  payload?: Record<string, string>;
}

Last will example

const transport = new AwsIotTransport({
  authorizerName: 'AnywareAuthorizer-production',
  endpoint: 'xxxxx.iot.ca-central-1.amazonaws.com',
  lastWill: {
    topic: 'myProject/production/clientDisconnected',
    payload: { clientName: 'myClient' },
  },
});