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 🙏

© 2024 – Pkg Stats / Ryan Hefner

smartbundle

v0.4.2

Published

zero-config bundler for npm packages

Downloads

178

Readme

SmartBundle - zero-config bundler for npm packages

How to use

  1. Create package.json like
{
  "name": "my-package",
  "version": "1.0.0",
  "private": true, // required for avoiding the accidental publishing
  "type": "module",
  "exports": {
    ".": "./src/index.ts" // entrypoint list for building the package
  }
}
  1. Run
npx smartbundle
  1. Go to the dist folder and publish your package to the npm registry. The total package.json will be generated automatically.

Features

  • generate the most compatible package.json for any bundlers(webpack, rollup, esbuild, vite, etc) or runtimes(node, bun, deno, etc)
  • validate package.json for common errors
  • do not require any configuration files like tsconfig.json, eslintrc.json, etc
  • but if you need to use them, you can use them by creating them manually like for the parcel bundler
  • generate esm and cjs entrypoints for the package
  • generate typescript typings for the package
  • require only minimal package.json fields

Known issues:

  • does not generate fully compatible cjs typings for the entrypoints (#9)
  • supports only type: module right now. It will be fixed before v1.0.0 release.

Motivation

Almost every npm package have the same build pipeline: build code, generate typescript typings, validate package.json, generate correct package.json for the bundlers and runtimes, blah-blah, etc.

I really like the microbundle project, but it requires a lot of extra configuration and is not zero-config. And more, the project is not maintained and does not support a lot of modern js features.

So I decided to create my own project to automate the build pipeline and save the developer's time for building packages.