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

pick-components

v1.0.9

Published

A tiny lifecycle-focused framework for building reactive web components

Readme

A lightweight, reactive web components framework for TypeScript and modern browser ESM.
Business logic stays in services. Components are pure presentation.

Spanish quick entry: README.es.md

Try the live playground: https://pick-components.github.io/pick-components/

npm License: MIT TypeScript


Features

  • Signal-based reactivity — Per-property signals; only bindings that depend on changed state re-run.
  • Component intent signals — Typed one-shot actions like save, refresh, or mode change, kept separate from render state.
  • No virtual DOM — Direct subscriptions update text nodes and attributes in place.
  • Two authoring styles — Inline @Pick for compact components; class-based @PickRender for explicit structure.
  • Built-in UI primitives<pick-for>, <pick-select>, <pick-action>, <pick-link>, and <pick-router> cover lists, branching, actions, and navigation.
  • Native slot projection — Named and default <slot> elements for composable layouts via Shadow DOM.
  • Factory-first DI — Explicit dependency injection through factory functions; no hidden service construction.
  • Security-first expression evaluator — Deterministic AST pipeline; no eval or new Function. Whitelisted read-only method calls only.
  • SEO-friendly prerender adoption — HTML-first delivery with compatible prerendered markup adopted on the client.
  • Tiny footprint — Zero runtime dependencies.
  • Browser-ready ESM releases — GitHub release artifacts can be loaded directly with <script type="module">.

Why Pick Components Exists

The full origin story is now documented in docs/WHY-PICK-COMPONENTS.md.

Short version: this framework was created to keep native Web Components explicit, predictable, and maintainable, with strict template safety and a smaller runtime surface.


Installation

npm install pick-components

Quickstart (npm + bundler)

import { bootstrapFramework, Services, Pick } from "pick-components";

await bootstrapFramework(Services);

@Pick("hello-card", (ctx) => {
  ctx.state({ name: "world" });
  ctx.html(`<p>Hello {{name}}</p>`);
})
class HelloCard {}

This is the fastest path when using Vite, Rollup, Webpack, esbuild, or similar toolchains.

Quickstart (no decorators)

import {
  bootstrapFramework,
  Services,
  definePick,
} from "pick-components";

const helloDef = definePick<{ name: string }>("hello-card", (ctx) => {
  ctx.state({ name: "world" });
  ctx.html(`<p>Hello {{name}}</p>`);
});

await bootstrapFramework(Services, {}, {
  components: [helloDef],
});

You can register components without @Pick/@PickRender by using definePick and defineComponent descriptors through the components option.

Copilot AI Setup (Optional)

Want Copilot to follow Pick Components conventions for components, DI, tests, and templates?

See the full setup guide in docs/USAGE-GUIDE.md#copilot-ai-setup-optional.


Start Paths

Run Locally

npm install
npm run build
npm run serve:dev

Playground: http://localhost:3000


Documentation


License

MIT © janmbaco