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

@north-light/applet-sdk

v1.7.0

Published

The ESM-only Core and Cloudflare contract for Northlight applets. It is intentionally split into four environment-specific subpaths and has no root export:

Downloads

1,117

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Maintainers

austin02202016austin02202016captaincrouton89captaincrouton89chaz_plonskichaz_plonskimb6611mb6611

Keywords

Readme

@north-light/applet-sdk

The ESM-only Core and Cloudflare contract for Northlight applets. It is intentionally split into four environment-specific subpaths and has no root export:

  • @north-light/applet-sdk/server — Worker bindings, platform operations, jobs, device events, visitor reads, the legacy runtime schema helper, Core proxy, and platform routes.
  • @north-light/applet-sdk/client — dependency-free browser conversation, artifact, activity, revision, repair, and host-message protocol.
  • @north-light/applet-sdk/theme — the dependency-free pre-paint theme contract.
  • @north-light/applet-sdk/build — the Workers Vite SSR block and manifest reader.

Ambient modules

Importing @north-light/applet-sdk/server brings the declarations for cloudflare:workers and node:async_hooks into your TypeScript program, so import { env } from 'cloudflare:workers' resolves with no @cloudflare/workers-types or @types/node installed — both of those packages' global libs clash with the DOM lib React needs. An applet must therefore not declare either module itself: two ambient declarations of the same module are a duplicate-identifier error. The binding shapes (AppletEnv, D1Database, R2Bucket, and friends) are ordinary exported types on /server, not globals.

nl-applet snapshot and nl-applet upload run from an applet repository's current working directory. snapshot produces snapshot.json and publish-meta.json, retaining src/server/schema.sql at database/schema.sql so deployment can apply it before activation; upload sends an existing verified snapshot to the applet source bucket.

The package uses tsc per-module ESM output instead of this monorepo's sibling-package tsup dual-format convention. Applet Vite builds inline this package under workerd conditions; a CJS entry can select Node interop and break the one-file Worker upload.

Core compatibility — major 1

Deployments bundle this SDK permanently. Core must preserve the meaning of every wire surface emitted by every published 1.x release:

  • POST /v1/cli/invoke
  • POST /v1/artifacts
  • GET /v1/artifacts/:id/content
  • the allow-listed five /v1/crouter/conversations* calls: create, deliver, stop, follow, and result
  • the x-nl-credential header in both directions
  • the /__nl/ready, /__nl/jobs, and /__nl/events routes and response shapes Core calls into an applet
  • the applet-v1 snapshot envelope and its digest arithmetic

There is no runtime version negotiation. A breaking Core change requires redeploying every live applet and is a product decision, not an SDK fallback.