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

@exactjs/component-library

v0.7.1

Published

Inert participation marker for eXact component libraries

Readme

@exactjs/component-library

This package is the inert participation marker for published eXact component libraries. It tells eXact build adapters that a package intentionally follows component-library packaging and provenance protocol 1.

Usage

Component-library authors add @exactjs/component-library to production dependencies and publish compiler-generated static build facts through exactComponentLibrary.build in their package manifest. Those facts map each public package export to the target-specific compiled module that owns the component. Applications do not import this package.

Declare shared framework runtimes as compatible peerDependencies, with development dependencies for the library's own build and tests. Keep this participation marker in dependencies. exactc build-library reports any undeclared runtime packages needed by its generated artifacts. The Vite, Bun, and Webpack adapters share the application's installed framework instances with linked libraries. Peer installation checks compatible ranges, and the consumer's server policy still determines which component and enhancement providers may execute.

The marker contains no JavaScript entry point, lifecycle, registration, configuration, or trust grant. Server execution remains subject to the consuming application's component-library policy.

Documentation | Source on GitHub