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

spark-html-dev-tls

v0.1.0

Published

Local HTTPS for spark-html dev servers. One command fronts your spark-ssr or spark-html-bun dev/preview server with a self-signed TLS reverse proxy, so secure-context browser APIs (camera, mic, geolocation, service workers) work when you open the app on a

Readme

spark-html-dev-tls

Local HTTPS for your spark-html dev server, so you can test secure-context browser APIs — camera, microphone, geolocation, service workers — from a real phone on your LAN. These APIs only work over https:// (or localhost), so a plain http://192.168.x.x:3000 dev URL can't use them. This wraps that dev server with a self-signed TLS reverse proxy.

It's a testing tool, and purely additive: your normal dev script is left exactly as it is (plain HTTP). You add a secure script that wraps it.

{
  "scripts": {
    "dev": "bun spark-ssr",
    "secure": "bun spark-html-dev-tls"
  }
}
bun run dev      # unchanged — http://localhost:3000
bun run secure   # https://<your-lan-ip>:3000  → open this on your phone

secure auto-detects the project (a spark.json / pages/ folder → spark-ssr; a spark.config.js → spark-html-bun), spawns that same dev server on a private port, and fronts it with HTTPS. It works the same for SSR, client-only, and prerender apps — an HTTP→HTTPS proxy doesn't care what's behind it.

What it handles

  • Plain requests stream straight through.
  • Live reload / live data (spark-ssr's /__spark/reload and /__spark/live Server-Sent Events) pass through as live streams.
  • Hot module reload (spark-html-bun's /__spark_hmr WebSocket) is relayed.
  • Secure cookies work — the proxy adds x-forwarded-proto: https, so the dev server marks session/flash cookies Secure correctly.

Requirements & options

openssl (a system tool, already on macOS/Linux and via Git-Bash/WSL on Windows) generates the certificate — no npm dependencies. The cert is cached in .spark/dev.{pem,key} with a SAN covering localhost, 127.0.0.1, and your LAN IPs, and reused until it nears expiry.

spark-html-dev-tls --port 8443            # pick the HTTPS port
spark-html-dev-tls --cert c.pem --key k   # bring your own cert (e.g. mkcert, for no warning)
spark-html-dev-tls -- bun spark-ssr       # skip auto-detect; wrap an explicit command

Self-signed certificates show a one-time browser warning (accept it, or install a mkcert cert and pass --cert/--key for a trusted, warning-free experience). This is a dev-only tool; production HTTPS is normally terminated by your host or a reverse proxy.