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

@instructure/platform-components

v0.2.0

Published

Shared presentational components for platform-ui packages.

Readme

@instructure/platform-components

Shared presentational components for platform-ui packages.

What this is

This package is a pilot program. Components here are built the way InstUI itself builds components — the same architecture, the same theming system, the same accessibility bar — with the goal of graduating proven ones into InstUI for wider use. Until (if) that happens, treat everything here as experimental.

Accessibility and design review follow InstUI's own process, just accelerated — a component belongs here only if it would pass InstUI's actual bar, not a lighter one. What genuinely differs is the release contract: this isn't a stable design-system package yet. Breaking changes can land here more often than you'd expect from something under the @instructure scope, because these components are still being proven out. Pin versions and read changesets before upgrading.

What belongs here

Shared presentational components. Anything with its own data fetching or domain logic gets its own package instead — see docs/adr/shared-components.md.

Components

Run pnpm storybook for the current component catalog — usage examples, prop tables, and each component's design rationale live there, generated from source, so they can't drift out of sync with the code the way a hand-maintained list here would.