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

@ui-manifest-json/core

v0.5.0

Published

Shared JSON schema types and framework-agnostic helpers for ui-manifest extractors.

Readme

@ui-manifest-json/core

The shared UiManifest schema — as TypeScript types — plus the framework-agnostic helpers every extractor builds on.

You don't usually install this directly. @ui-manifest-json/angular and @ui-manifest-json/react depend on it. Install it on its own when you're consuming manifests and want the types, or writing an extractor for another framework.

npm install @ui-manifest-json/core

What's in it

import type { UiManifest, RouteNode, ComponentNode, DomNode } from '@ui-manifest-json/core';

const manifest: UiManifest = JSON.parse(await readFile('ui-manifest.json', 'utf8'));

The full shape is documented field by field in docs/schema.md. The types are the source of truth; that page is the tour.

Three runtime helpers ship alongside the types:

| Export | What it does | |---|---| | resolveRouteDependencyTree | Splices each component's template into its parent's where the child's tag appears, recursively, with component-boundary and cycle markers. Framework-agnostic: you supply a matchFn that decides which tag maps to which component. | | resolveFullPaths | Walks a nested route tree and annotates each node with the full path a URL must have to reach it, baseHref applied. | | collectRepoProvenance / generatorProvenance | Reads the commit, remote, branch, dirty state and app root out of the git working tree, and the build id out of CI. Best-effort: outside a git tree every field is simply absent, which means the manifest is unpinned rather than that anything failed. |

Schema version

SCHEMA_VERSION is "2.0". A manifest carries it as schemaVersion, and it is the one field to check before trusting the rest — v2 made app.baseHref and app.routerMode required, and without those a route path cannot be matched against a real URL at all.

License

MIT — see LICENSE.