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

jukebox-types

v0.1.4

Published

Types for Jukebox

Downloads

44

Readme

Jukebox Types

Interface Standards

All models have the following fields:

// Default fields for all models
interface IModel {
  id: number
  created_at: string
  updated_at: string
}

For a model Example, the following types would be (with sample documentation):

/**
 * Base object, has all fields from database
 */
interface IExample extends IModel {}

/**
 * Fields used to create object
 *
 * @see {@link IExample}
 */
interface IExampleCreate extends ICreate<IExample> {}

/**
 * Fields used to update object
 *
 * @see {@link IExample}
 */
interface IExampleUpdate extends IUpdate<IExample> {}

// ====================
// Optional Interfaces
// ====================
/**
 * Aggregate related data for object
 *
 * @see {@link IExample}
 */
interface IExampleDetails extends IExample {}

Conventions

For a model Example, abide by the following:

  • Objects generated from ORMs or Schemas would be called Example
  • Interfaces called IExample
  • All fields in object are snake case, regardless of the tech stack used. This should be especially enforced in REST APIs.
  • For sub interfaces of the main interface, include @see {@link IExample} to allow easier access to the the main interfaces docs in the editor. The @see is used to notate an additional reference, and @link creates a hyperlink to the original object. The brackets are used to combine the decorators properly.