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

@justai/cim

v0.1.0

Published

City in Motion as data — the typed client for api.cityinmotion.nl, read at build time.

Readme

@justai/cim

City in Motion as data — the typed client for api.cityinmotion.nl, read at build time.

Why it is a package

It was cim-location/src/lib/city.ts until guess-back reached for the same stops() and the same panoUrl(). Two consumers is the ecosystem's promotion trigger, and the tell is that you are about to copy rather than to import.

cim-location still carries its own copy and moves onto this at its next touch. The lockfile decides which persona a package reaches, and a fleet wave to land a refactor nobody is waiting for costs more than it buys.

The two halves, and the line between them

| export | what it is for | |---|---| | stops() | the 38 standpoints — name, identity sentence, coordinates, and the pose an editor set | | panoUrl(pose) | a still of that pose, through the graph-gated proxy |

panoUrl is the thumbnail surface, and naming it that matters now there is a second way to show a panorama. A persona that fills the screen with one embeds Google's live StreetViewPanorama and drives it with @justai/pano; this is for the picture in a list, in a card, in a choice.

It is read while the site is being built

Nothing here runs in a visitor's browser, and that was decided by the acceptance interview rather than by preference — item 37 ⛔ (it opens in airplane mode) and items 65/66 ⛔ (four Lighthouse numbers). A page that fetches its content on load fails the first outright and spends its budget on the second.

The honest cost, stated rather than discovered: content changes need a redeploy.