npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details


  • User packages



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.


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 🙏

© 2021 – Pkg Stats / Ryan Hefner




An experiment to bundle the entire CDK into a single module




monocdk Experiment


An experiment to bundle all of the CDK into a single module.

:warning: Please don't use this module unless you are interested in providing feedback about this experience.



To try out monocdk replace all references to CDK Construct Libraries (most @aws-cdk/* packages) in your package.json file with a single entrey referring to monocdk.

You also need to add a reference to the constructs library, according to the kind of project you are developing:

  • For libraries, model the dependency under devDependencies and peerDependencies
  • For apps, model the dependency under dependencies only

Use in your code

Classic import

You can use a classic import to get access to each service namespaces:

import { core, aws_s3 as s3 } from 'monocdk';

const app = new core.App();
const stack = new core.Stack(app, 'MonoCDK-Stack');

new s3.Bucket(stack, 'TestBucket');

Barrel import

Alternatively, you can use "barrel" imports:

import { App, Stack } from 'monocdk';
import { Bucket } from 'monocdk/aws-s3';

const app = new App();
const stack = new Stack(app, 'MonoCDK-Stack');

new Bucket(stack, 'TestBucket');