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

cherry-pick

v0.5.0

Published

🍒⛏📦 Build tool to generate proxy directories.

Downloads

3,653

Readme

cherry-pick 🍒⛏📦

Build tool to generate proxy directories with package.json files such as this:

{
  "name": "redux-saga/effects",
  "private": true,
  "main": "../lib/effects.js",
  "module": "../es/effects.js"
}

Why?

When it comes to "main" entry points of our libraries we have an easy way for supporting both CJS & ESM files with respectively "main" and "module" fields in package.json. This allows resolution algorithms to chose a file with the best format automatically. However if we have multiple files in a package and we want all of them to be importable we often suggest to users doing it like this:

import module from "package/lib/module";

There are problems with this approach:

  • it is often encouraging people to import files authored in CJS format, which if produced with tools like babel has i.e. interop helper functions deoptimizing imported file size when comparing to the same file authored in ESM format. Also webpack just bails out on CJS files when trying to optimize your application size with techniques such as tree-shaking & scope hoisting (a.k.a module concatenation).
  • it is exposing internal directory structure to the user. Why lib is in the requested path? If you ship both CJS & ESM directories to npm and if users would like to import appropriate file depending on the tool they are "forced" to remember this and switch between importing the same thing with paths like package/lib/module and package/es/module. This is a mental overhead that can be avoided.

This technique was also described by me in more details in this article.

CLI Options

default

cherry-pick [input-dir]

Create proxy directories

Commands:
  cherry-pick [input-dir]        Create proxy directories              [default]
  cherry-pick clean [input-dir]  Cleanup generated directories

Options:
  --help, -h     Show help                                             [boolean]
  --version, -v  Show version number                                   [boolean]
  --cjs-dir                                                     [default: "lib"]
  --esm-dir                                                      [default: "es"]
  --types-dir
  --cwd                                                           [default: "."]
  --input-dir                                                   [default: "src"]

clean

cherry-pick clean [input-dir]

Cleanup generated directories

Options:
  --help, -h     Show help                                             [boolean]
  --version, -v  Show version number                                   [boolean]
  --cwd                                                           [default: "."]
  --input-dir                                                   [default: "src"]

JS API

cherry-pick exports a default method which creates proxy directories and clean which removes them. Both accepts the same options as corresponding CLI commands, only they are camelCased.

const { default: cherryPick, clean } = require("cherry-pick");

cherryPick({ inputDir: "source" })
  .then(cherryPicked =>
    console.log(`Created proxy directories: ${cherryPicked.join(", ")}`)
  )
  .then(() => clean({ inputDir: "source" }))
  .then(removed =>
    console.log(`Removed proxy directories: ${Removed.join(", ")}`)
  );