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

@inverted-tech/fragments

v0.19.0

Published

Types and JS runtime for Inverted protocol buffers (Fragments)

Readme

Fragments

Monorepo folder for the IT WebServices protocol buffer definitions and generated artifacts.

This directory contains the canonical .proto files, generation scripts, and the npm package @inverted-tech/fragments built from these sources.

Layout

  • Protos/ — protobuf sources organized by domain (Authentication, Authorization, Comment, Content, CreatorDashboard, Generic, Notification, Page, Settings)
  • buf.yaml / buf.gen.v2.yaml — Buf configuration and codegen pipeline
  • generate-ts.mjs — TypeScript generation entrypoint
  • ts-gen/ — intermediate TypeScript barrels (source for the package build)
  • dist/ — build output (created during package builds)

Code Generation

  • C# code: handled by Grpc.Tools via project csproj includes elsewhere in the repo
  • TypeScript/JS package: built from the protos using Buf + TS generators

Common tasks (from Fragments/):

npm run build      # build TS types and ESM outputs
npm run rebuild    # clean and rebuild
npm run gen        # regenerate TS barrels from protos

Validation

We annotate protos using ProtoValidate where useful to enforce shapes (e.g., string.min_len, string.email, repeated.unique). See files under Protos/ (for example Settings protos) for current annotations.

NPM Package Usage

For TypeScript/JavaScript import patterns and subpath exports, see README.PACKAGE.md in this folder. That document covers how to consume @inverted-tech/fragments.

Releases (Changesets)

We use Changesets for versioning and publishing of the npm package.

Prereqs:

  • npm login with access to the @inverted-tech scope
  • 2FA if required (npm profile enable-2fa auth-and-writes)

Workflow:

npm run changeset           # author a changeset
npm run release:version     # apply versions
npm run release:publish     # build and publish