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

@devicesdk/core

v1.4.0

Published

Core TypeScript types and device abstractions for DeviceSDK IoT applications.

Readme

@devicesdk/core

Core TypeScript types and device abstractions for DeviceSDK IoT applications.

Installation

npm install @devicesdk/core

Usage

Device entrypoints

Extend the DeviceEntrypoint class to write device scripts. Your script runs in a sandboxed serverless runtime — not on the microcontroller and not in Node.js. It receives events from the device over WebSocket and can issue commands back through this.env.DEVICE.

import { DeviceEntrypoint, type DeviceResponse } from "@devicesdk/core";

export class MyDevice extends DeviceEntrypoint {
  // Called when the physical device connects via WebSocket
  async onDeviceConnect() {
    console.log("Device connected!");
    // Light up the onboard LED (virtual pin 99 on Pico W and ESP32 boards)
    await this.env.DEVICE.setGpioState(99, "high");
  }

  // Called when a response/event is received from the device.
  // `message` is a discriminated union — narrow on `message.type`.
  async onMessage(message: DeviceResponse) {
    if (message.type === "pin_state_update") {
      console.log(`Pin ${message.payload.pin} = ${message.payload.value}`);
    }
  }

  // Called when the device disconnects
  onDeviceDisconnect() {}

  // Optional: define named cron schedules (UTC)
  crons = { daily: "0 8 * * *" };

  // Called when a named cron fires
  async onCron(name: string) {
    console.log(`Cron fired: ${name}`);
  }
}

I2C peripherals

Import I2C device abstractions for sensors and displays:

import { BME280 } from "@devicesdk/core/i2c";

Pico device types

Import Raspberry Pi Pico-specific pin and peripheral types:

import { type PicoDeviceApi } from "@devicesdk/core/devices/pico";

License

Copyright (c) 2026 DeviceSDK. All rights reserved. See LICENSE for details.

Documentation

Full documentation at devicesdk.com/docs.