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

@lumate/lumo-sdk

v1.1.0

Published

Typed SDK for Lumo mini-programs — a thin wrapper over the injected window.Lumo bridge.

Readme

@lumate/lumo-sdk

The typed SDK for Lumo mini-programs. It's a thin wrapper over the window.Lumo bridge the Lumo app injects into every mini-program's WebView — so you develop against a real import with full autocomplete instead of poking at window.

npm i @lumate/lumo-sdk
import Lumo from '@lumate/lumo-sdk'

const { openId, user } = await Lumo.login()
const info = await Lumo.getSystemInfo()
const res = await Lumo.request({ url: 'https://api.example.com/data' })
await Lumo.storage.set('key', 'value')

When run outside the Lumo app (e.g. previewing a page in a desktop browser), calls throw a clear error. Guard with isLumoAvailable() if you need to degrade gracefully:

import Lumo, { isLumoAvailable } from '@lumate/lumo-sdk'
if (isLumoAvailable()) await Lumo.showToast('hi')

Plain-HTML developers (no bundler) can keep using the injected global directly — it's typed too:

<script>
  const info = await window.Lumo.getSystemInfo()
</script>

Available capabilities depend on your manifest.json permissions (and, for request(), your requestDomains). Calling a method whose scope wasn't granted rejects with an error. Full API, manifest spec and permission scopes: https://www.lumate.my/developers.