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

derive-pkg

v1.0.0

Published

A helper utility for publishing transpiled code to npm

Downloads

7

Readme

derive-pkg

build status coverage status dependencies status npm version

A helper utility for publishing transpiled code to npm

Turn require('your-module/lib/submodule') into require('your-module/submodule')

What is this for?

The standard convention when publishing code transpiled with Babel is to place source code into src/ and transpiled code into lib/. Unfortunately, this makes consuming individual submodules inconvenient because they don't exist at the root of the package, e.g. one must require('the-module/lib/some-submodule.js').

This utility derives npm package metadata from your root directory and copies it to your build directory so you can publish it instead. Now lib/ is the root of your package!

derive-pkg does the following:

  • Copies package.json from root with the changes below
    • Rebase main, bin, and browser field entry paths from lib/ to /
    • Omit devDependencies
  • Copies files from root that npm will never ignore and should be included when publishing (e.g. readme, license, and changelog)
  • Copies .gitignore/.npmignore from root as .npmignore

Install

npm install derive-pkg --save-dev

Quick Example

babel-cli src -d lib
derive-pkg -d lib
npm publish lib

Usage

Usage: derive-pkg [directory] [options]

Options:
      directory   The base directory containing the package.json (default: ".")

  --out-dir, -d   The output directory for the derived package.json

     --name, -n   Override the name field of the derived package.json

  --version, -v   Override the version field of the derived package.json

FAQ

Couldn't this just be a shell script?

Yep, but derive-pkg is cross-platform and has unit tests.