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

@fynd-design-engineering/jcp

v0.0.1

Published

JCP

Readme

Your Project

Note: This README is a starting point.
Update it with your project-specific details, file explanations, and logic descriptions to make it more informative and maintainable.

This project was generated using CDN-Starter — a modern template for building and deploying TypeScript/JavaScript code to Webflow or any CDN environment.
You can now customize it with your own scripts, utilities, and design logic.


Getting Started

1. Install Dependencies

Run the following command inside your project folder:

pnpm install

This will install all required development and build dependencies.


2. Update package.json

After installation, open the package.json file and fill in your own details:

{
  "name": "your-project-name",
  "version": "0.0.0",
  "description": "brief description of your project",
  "homepage": "your-project-homepage",
  "license": "MIT",
  "keywords": [],
  "author": {
    "name": "your-name",
    "url": "your-website-or-profile"
  }
}

Only update the above fields.
Other configurations are pre-optimized for TypeScript builds, linting, and npm releases.


3. Edit Source Files

All editable files are inside the src/ folder.
This is where you add your scripts, components, utilities, and styles.

Example workflow:

  • Modify src/index.ts or create new folders like src/home/ or src/utils/.
  • Whenever you add a new file, include it in bin/build.js under ENTRY_POINTS.
const ENTRY_POINTS = [
  "src/index.ts",
  "src/styles/global.css",
  "src/home/index.ts"
];

Any file listed here will be automatically compiled into the dist/ folder when you build.


Available Commands

Development

Start a local development environment:

pnpm dev

This command compiles your code in real time and serves it at: http://localhost:3000


Build for Production

Generate optimized and minified builds:

pnpm build

Output files are created inside the dist/ directory.
These are the files you can upload to your CDN or include in Webflow.


Linting and Formatting

Maintain code consistency and quality:

pnpm lint        # Check for lint issues
pnpm lint:fix    # Auto-fix lint issues
pnpm format      # Format code using Prettier
pnpm check       # Type check using TypeScript

Versioning and Releasing

Handle versioning and publishing to npm:

pnpm changeset
pnpm changeset version
pnpm release

Run these sequentially to version and release your package.


Generate CDN Links

After publishing, run:

pnpm cdn

This displays ready-to-use <script> or <link> tags pointing to the latest version of your npm package.

Example:

<script defer src="https://cdn.jsdelivr.net/npm/your-package-name@latest/dist/index.js"></script>

Folder Structure

your-project/
├── src/             # All editable source files
│   ├── index.ts
│   ├── styles/
│   │   └── global.css
│   └── home/
│       └── index.ts
├── bin/             # Build configuration (edit ENTRY_POINTS here)
│   └── build.js
├── dist/            # Generated build output (do not edit)
├── package.json
├── tsconfig.json
├── eslint.config.js
└── README.md

Important:
Every file you create inside src/ must be listed in bin/build.js under ENTRY_POINTS to be compiled into dist/.


Notes

  • Keep editable files limited to the src/ directory.
  • Avoid manual edits in dist/ — it’s auto-generated.
  • Use semantic versioning (major.minor.patch) for clear release cycles.
  • Always commit changes before running a release.

License

This project is licensed under the MIT License.


Built using CDN-Starter.