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

@kb-labs/marketplace-core

v2.34.0

Published

Marketplace service — unified install/uninstall/enable/disable for all entity types

Downloads

2,432

Readme

@product-name/package-name

Baseline library package inside KB Labs Product Template.

Vision & Purpose

@product-name/package-name is a minimal example library shipped with kb-labs-product-template.
It shows how a typical package is structured (source, tests, types) and is intended to be renamed or removed when creating a real product.

Core Goals

  • Demonstrate the standard KB Labs package layout (src/types/tests/build tooling)
  • Provide a simple, testable function (hello) as a starting point
  • Act as a safe playground for verifying DevKit configs (tsup, Vitest, ESLint)

Package Status

  • Version: 0.1.0
  • Stage: Template / Example
  • Status: Not for Production ⚠️

Architecture

Structure

packages/package-name/
├── src/
│   ├── index.ts        # Public entrypoint
│   └── types/          # Shared types and re-exports
│       ├── types.ts
│       └── index.ts
├── index.test.ts       # Vitest example
└── tsup.config.ts      # Build configuration

The default implementation is intentionally tiny:

export const hello = (name = 'KB Labs') => `Hello, ${name}!`;

Dependencies

Runtime

None by default — this is a pure TypeScript example.

Development

  • @kb-labs/devkit: shared TS/ESLint/Vitest/TSUP presets
  • tsup, vitest, tsx, typescript

Scripts

From the kb-labs-product-template root:

pnpm --filter @product-name/package-name build
pnpm --filter @product-name/package-name test
pnpm --filter @product-name/package-name lint

How to Adapt for a Real Package

When using the product template for your own project:

  1. Rename the package in package.json (e.g. @kb-labs/my-product-core).
  2. Replace the hello function with your actual public API.
  3. Update tests in index.test.ts to cover real behaviour.
  4. Adjust types/ to expose the correct public types.

This package is meant as a scaffold only; don’t ship it as-is to production.