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

dist-es6

v0.2.5

Published

Utilities to support development of npm packages in ES6+

Downloads

8,257

Readme

dist-es6

Build Status

Utilities to support development of npm packages in ES6+.

While developing, dist-es6 modifies the Node.js module search path so that you can import files by module name as a user of your package would, instead of having to figure out relative paths.

When you're ready to publish your package, dist-es6 compiles ES6+ code from the src directory, copies the package.json, and copies other whitelisted files (from the files field in package.json) into the dist directory; it then publishes the dist directory, ensuring that users only deal with the compiled code.

Installing

dist-es6 is available as an npm package.

Usage

In your package.json, run the dist-es6 command from the prepublish script as follows:

{
  "name": "project",
  "scripts": {
    "prepublish": "dist-es6"
  }
}

Then, run npm install.

Note that your project must have all of its JavaScript inside of the src directory. The main and bin fields must only refer to files inside of the src directory:

{
  "name": "project",
  "main": "src/index.js",
  "bin": {
    "project": "src/bin/project.js"
  },
  "scripts": {
    "prepublish": "dist-es6"
  }
}

For executables written in ES6+, do not add a shebang to the file; dist-es6 will automatically add a shebang after compilation or linking. For executables not written in ES6+ (that can run as is via node), you still need to add a shebang.

Remember to run npm install after any changes to package.json.

Now, you'll be able to directly run executables from the current project on the command line. You'll also be able to require files from the current project via module path instead of relative path:

import code from 'project/lib/code';

For publishing, files outside of the src directory that need to be published must be whitelisted in the files field as follows:

{
  "name": "project",
  "files": ["LICENSE", "README.md", "docs"],
  "main": "src/index.js",
  "bin": {
    "project": "src/bin/project.js"
  },
  "scripts": {
    "prepublish": "dist-es6"
  },
}

Note that a dependency on the babel-runtime will be added to the compiled version of the package.

To publish the compiled version of the package:

npm publish

The above will compile the package into the dist directory and run npm publish on the dist directory. Note that as an implementation detail, the command will return code 143, which will probably cause deployment scripts to fail. You need to explicitly check the error code.

Development

Getting Started

The application requires the following external dependencies:

  • Node.js

The rest of the dependencies are handled through:

npm install

Run tests with:

npm test