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

airspace

v0.1.8

Published

A fully-typed, atproto-native CMS toolkit, turning your PDS into your content layer.

Readme

airspace

npm version npm downloads Github Actions Codecov

The database you already have.

getair.space

Every ~~Bluesky~~ atmosphere account comes with a personal data server: a cms, login, file storage and a public API that you own.

  • you own your data. Records live in your own repo under your own schema. Switch tools or hosts – or even stop using airspace – and everything still works.
  • no database to run. Reads, writes, auth and images are all handled by your own PDS. airspace is a typed client.
  • drafts built in. Experimental permissioned spaces for private data, with a single call to publish.
  • typed from your schema. Define the model once. Records, keys, joins and OAuth scopes are inferred magically. ✨

example

// lexicons.ts
import { defineLexicons, field } from 'airspace/lexicon'

export default defineLexicons('dev.roe', {
  note: {
    title: field.text(),
    body: field.markdown(),
    createdAt: field.datetime(),
  },
})
// notes.ts
import { createAirspace, defineCollection, passwordSession } from 'airspace'
import lexicons from './lexicons.ts'

const notes = defineCollection(lexicons.note)

export const airspace = createAirspace({
  identity: 'roe.dev',
  collections: { notes },
  session: await passwordSession({ service: 'https://pds.example', identifier: 'roe.dev', password: process.env.PDS_APP_PASSWORD! }),
})

const published = await airspace.notes.list({ limit: 10 })
await airspace.notes.create({ title: 'Hello', body: '# hi', createdAt: new Date().toISOString() })

[!WARNING] Permissioned spaces, where drafts and private records live, are experimental. They need a PDS running prerelease software: atproto's permissioned-data branch, or the @atproto/pds spaces alpha. Hosted PDSes, including bsky.social, do not support them yet. The API may change.

docs

getair.space/docs.

examples

  • examples/nuxt: a Nitro plugin providing an airspace client + server routes +@comark/vue.
  • examples/astro: static generation + getStaticPaths + Astro actions for writing.
  • examples/sveltekit: load functions + form actions with field-level validation.
  • examples/node: a CLI with no framework and no build step.

The demo on getair.space is the same app, running against a sandbox account on a demo PDS.

development

  • Clone this repository
  • Install dependencies with pnpm install
  • Run the tests with pnpm dev. They run against a real PDS with permissioned spaces, booted in process with @atproto/dev-env
  • Run pnpm dev:pds for a PDS on port 2583 that stays up, printing dotenv-shaped credentials for two accounts
  • Run pnpm lex:build to regenerate src/lex from lexicons/
  • Run pnpm size to print the bundle size table in the docs

credits

Many thanks to @mkrl for the name idea 🙏

license

Made with ❤️

Published under MIT License.