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 🙏

© 2026 – Pkg Stats / Ryan Hefner

silk-babel-run

v1.14.5

Published

Misc utilities for running babel / mocha

Readme

Babel Run utils

This folder contains various pieces to make using Babel with our Babel preset easier, without the need for Babel configurations in every module.

CLI

You can run scripts written in ES6 directly from the command line:

$ ../babel-run/babel-node my_script.js

The babel-node wrapper modifies CLI arguments as if node were executing the script directly. If you need to run the script without altered arguments (for e.g. cluster.fork() expects unaltered arguments) you may want to use babel-node-allargs wrapper:

$ ../babel-run/babel-node-allargs my_script.js

Shebang

Both babel-node and babel-node-allargs can be used in a shebang line so you can directly create executable scripts written in ES6:

#! /usr/bin/env ../pub/babel-run/babel-node

console.log(`This is ES6 Code`);

Custom wrapper scripts

If you need to do additional things besides Babelifying the code, you may want to write your own wrapper script rather than using babel-node or babel-node-allargs.

#!/usr/bin/env node

'use strict';

require('../babel-run/node')();
doAdditionalStuff();
require('./myscript');

Mocha:

For example you can use the node.js file to setup a mocha environment, by adding a your-module/test/mocha.opts file:

--require ../../babel-run/mocha

Alternatively, you can refer to a dedicated JS module to set up the node environment if you wish to do additional stuff:

--require test/setup.js

test/setup.js would look similar to a CLI wrapper script:

require('../../babel-run/node')();
doAdditionalStuff();