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

@khalido/home

v0.2.4

Published

home.ts: small, typed home automation for TypeScript: Hue, Daikin, Enphase, Google Cast, AirPrint printers and a Spotify Soloist speaker on the local network; Amber prices, Up Bank spending and the weather from the cloud.

Readme

home.ts

Small, typed home automation for TypeScript, starting with the devices in my house: Philips Hue, a Daikin AC, Enphase solar, Google Cast speakers and screens, AirPrint printers and a Spotify Soloist speaker on the local network, plus Amber Electric's live prices, Up Bank spending and the weather. One small library, published as @khalido/home, and a home command. No server, no cloud of its own.

  • Read every device into one typed snapshot, kept current by event stream or on a timer.
  • Turn lights on, set the AC, change speaker volume. Writes are spaced and merged, so a burst never floods a device.
  • Find what answers on your network, and check it read-only from the terminal.
  • Combine solar, grid and price into one energy figure.

Install

bun add @khalido/home     # or: npm install @khalido/home

The library runs on Bun 1.4+ and Node 24+, and is ESM only. The home command needs Bun on your PATH; in a project that added the package, run it as bunx home.

Pointing a coding agent at it? Give it llms.txt: what to call and where each doc is. Using it from an app is the same for people.

Try it

From a clone:

bun install
bun test        # runs on fixtures, no device needed
bun link        # puts `home` on your PATH
home discover   # what answers on this network, and which of it this package supports
home probe      # read-only checks, no keys
home            # each connector: connected, or what it still needs
home devices    # every device, one line each

Copy .env.example to .env and fill in the connectors you have, or describe the home in a config file (example).

Use it from code

Weather needs no key or device, so this runs anywhere:

import { createHome } from "@khalido/home";
import { weather } from "@khalido/home/weather";

const home = createHome(
  [weather({ latitude: -33.87, longitude: 151.21 })],
  (snapshot) => console.log(snapshot),
);
home.start(new AbortController().signal); // connects, reads, keeps reading, reconnects
home.part("weather")?.state; // typed by name, read from memory, never from the device

The library never reads your environment or a file: you pass addresses, keys and a fetch. Under Node, Hue and Enphase take the fetches in @khalido/home/node. From a clone, run bun run build first: the package's entry points resolve to dist/. Health, change events, writes and the energy helpers are in using it from an app.

Connectors

| Connector | Reads | Writes | | --------------------------------------------- | ----------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | hue | lights, rooms, scenes, over the bridge's event stream | lights, rooms, scenes | | daikin | the AC, over its local API | power, mode, setpoint, fan | | enphase | solar production and consumption from the IQ Gateway | none | | cast | every Cast device and speaker group | volume, mute, stop, announcements | | printers | AirPrint printers over IPP: state, toner, paper | none | | spotify | a Spotify Soloist speaker: what is playing, volume, shuffle, over its local WebSocket | activate, play a link, pause, resume, skip, seek, volume (capped), queue, shuffle, repeat, each confirmed by what the speaker reports; turn down or pause around an announcement; a stalled stream noticed and, if asked, restarted | | amber | live import and feed-in prices | none | | up | household spending by category, what still needs one | a category or tag on a transaction | | weather | now, forecast by the hour and by part of the day, rain soon, the sun, from BOM, Open-Meteo and Google | none |

Each connector's README says what has run against a real device and what has not. This covers only the devices I own; Home Assistant is the inspiration and the reference for every protocol.

More

I use it from jaldi, a Mac launcher, and chota-bot, a family bot on a Raspberry Pi, both on Bun; the docs name both.

Licence

MIT. Each connector's README lists its sources and their licences. Two Daikin sources are GPL-3.0 and are read for facts only, never copied.