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

oasbox

v0.2.3

Published

In-project CLI for obsidian-arrow projects — generate, validate, test.

Downloads

621

Readme

oasbox

The in-project CLI for Obsidian Arrow projects — a small, deterministic generator and validator for components, views, and stories. Package-manager agnostic (pnpm / npm / bun / yarn) and installed as a local devDependency by create-obsidian-arrow, so its behavior is pinned and reproducible for humans and agents alike.

Install

Scaffolds created with create-obsidian-arrow already include oasbox as a devDependency. To add it manually:

pnpm add -D oasbox     # or: npm i -D oasbox / bun add -d oasbox

Commands

| Command | What it does | |---|---| | oasbox generate component <Name> [--css] | Scaffold a component (primitive or composed) → src/components/<Name>/. Parent/Child → view-scoped component under src/views/<Parent>/. | | oasbox generate view <Name> [--editor] | Scaffold a full-pane view (+ story), born with the portable 3-zone oas-shell-view (pinned header, scrolling body, pinned footer). --editor → body capped at readableWidth: true (readable line width). | | oasbox generate story <Name> [--kind view\|component] | Story file only, for existing source. | | oasbox validate [--json] | Run CSS-orphan / scope / import checks + typecheck. --json for machine-readable output. | | oasbox test / oasbox dev | Pass-throughs to the project's package manager (auto-detected from the lockfile). |

Run via the local bin (oasbox …) or your package manager: pnpm oasbox … · npx oasbox … · bunx oasbox ….

What generate produces

oasbox generate view Notes            oasbox generate component Badge --css
└─ src/views/Notes/                    └─ src/components/Badge/
   ├─ Notes.ts                            ├─ Badge.ts
   ├─ Notes.css                           └─ Badge.css
   └─ state.ts                         └─ stories/components/Badge.stories.ts
└─ stories/views/Notes.stories.ts
   (kind: "view")
flowchart LR
  M["command flags"] --> K{"kind ?"}
  K -- "component" --> C["src/components/… + story"]
  K -- "view" --> S{"--editor ?"}
  S -- "no" --> P["view · full-bleed"]
  S -- "yes" --> E["view · readableWidth (oas-readable-width)"]

License

MIT