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

@deloryx/contracts-tracking

v0.2.0

Published

Smithy IDL contracts for the Deloryx tracking platform. Generates TypeScript and Kotlin DTOs consumed by deloryx-js (browser library) and deloryx-backend-tracking-gateway (Quarkus service).

Readme

@deloryx/contracts-tracking

Shared wire-format schema for the Deloryx tracking platform.

  • Source of truth: model/*.smithy — Smithy IDL describing the TrackingService and event payloads.
  • Generated artifacts (committed):
    • codegen/typescript/ — TS types consumed by deloryx-js (browser library).
    • codegen/kotlin/com/deloryx/tracking/contracts/Events.kt — Kotlin data classes consumed by deloryx-backend-tracking-gateway.

Why Smithy?

The user asked for "something like Smithy" (AWS Smithy IDL) so a single schema generates both TypeScript (for the library) and Kotlin (for the Quarkus gateway). This guarantees the wire format on both sides cannot drift.

Regenerating after schema changes

# Pre-req: install Smithy CLI (https://smithy.io/2.0/guides/smithy-cli/index.html)
#   brew install smithy-cli           # macOS
#   curl -L https://github.com/smithy-lang/smithy/releases/latest/download/smithy-cli-linux-x86_64.zip ...

npm install
npm run build                # smithy build + quicktype TS + quicktype Kotlin

npm run verify-fresh runs the build and git diff --exit-code codegen to confirm no drift. CI gates PRs on this check — a PR that modifies model/*.smithy without regenerating codegen/* fails.

Current status

The Smithy → JSON Schema → quicktype codegen pipeline is scaffolded but not yet wired into CI. The committed codegen/typescript/ and codegen/kotlin/ files are hand-written to match the Smithy model and treated as the practical source of truth until Smithy CLI is part of the dev image.

When changing the schema today, edit BOTH:

  1. model/*.smithy (the documented spec)
  2. The corresponding codegen/typescript/index.ts and codegen/kotlin/.../Events.kt

When the codegen pipeline lands, only step 1 will be needed.

Consumer wiring

TypeScript library (deloryx-js/):

import { CaptureEnvelope, TrackingEvent, BUILTIN_EVENT_NAMES } from '@deloryx/contracts-tracking';

Resolves via npm workspace or a file:../deloryx-clients-tracking-contracts dependency.

Quarkus gateway (deloryx-backend-tracking-gateway/): For v0 the Kotlin file is copied directly into the gateway's source tree at build time via a Maven process-resources script. v1 will publish this as a proper Maven artifact com.deloryx:deloryx-clients-tracking-contracts-kotlin.