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

@pie-players/pie-context

v0.3.12

Published

Framework-agnostic Context Protocol helpers for PIE web components

Readme

@pie-players/pie-context

Framework-agnostic Context Protocol helpers for PIE web components.

This package implements the Web Components community context-request protocol so orchestration/runtime dependencies can be shared without prop drilling.

Included APIs

  • createContext<T>(key) for typed context keys
  • ContextRequestEvent and ContextProviderEvent
  • ContextProvider and provideContext(...)
  • ContextConsumer, consumeContext(...), and requestContext(...)
  • ContextRoot for late-provider replay of pending subscribing requests

Design notes

  • Events are emitted with bubbles: true and composed: true.
  • Provider matching uses strict key identity (===).
  • ContextRequestEvent.subscribe defaults to false (one-shot request).
  • Providers call stopPropagation() when they satisfy a matching request.
  • Providers re-dispatch existing subscriptions when a nested provider for the same context announces itself.
  • Subscriptions are opt-in (subscribe: true) and include unsubscribe callbacks.
  • ContextRoot only tracks subscribing requests to avoid unnecessary retention.
  • ContextRoot dedupes pending replay by (requestor, callback) pair.

See LIT_PARITY_CHECKLIST.md for the parity checklist used to align semantics with ../lit/packages/context core APIs.

Svelte usage pattern

Keep Svelte reactivity for internal state and use this package for ambient runtime dependencies between components:

import { onMount } from "svelte";
import { ContextConsumer, createContext } from "@pie-players/pie-context";

const toolkitContext = createContext<{ assessmentId: string }>(
  Symbol("toolkit-runtime"),
);

let host: HTMLElement;
let assessmentId = "";
let consumer: ContextConsumer<typeof toolkitContext>;

onMount(() => {
  consumer = new ContextConsumer(host, {
    context: toolkitContext,
    subscribe: true,
    onValue: (value) => {
      assessmentId = value.assessmentId;
    },
  });
  consumer.connect();
  return () => consumer.disconnect();
});