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

yieldify

v0.0.3

Published

Compiler for ES6 with no runtime component

Readme

yieldify

Transpiler for ES6 to ES5 with no runtime component. The design goals of this project are:

  1. Use the esprima parser rather than writing a custom parser. Using the harmony branch gives pretty good support, and if it turns out to be lacking, it can be patched.
  2. Produce output code that is as readable as possible.
  3. Produce output code that is as performant as the input code where possible.

Non goals include:

  1. Performance of the conversion, unless it gets unreasonably slow.
  2. Supporting features that can be "polyfilled"
  3. Supporting the entirety of ES6

In short, this gives you those helpful syntactic shortcuts without the bloat that often acompanies transpilers.

Build Status Dependency Status NPM version

Features supported

  • template strings I am a ${"template"} string
  • classes class Dog extends Animal { constructor() { super('Dog') }}
  • arrow functions var squares = [1, 2, 3, 4].map(x => x * x)

Ironically not yield a this stage :(

Installation

npm install yieldify

CLI

To compile from the CLI you can use a number of methods:

$ yieldify input.js > output.js
$ yieldify < input.js > output.js
$ yieldify input.js output.js
$ yieldify input.js | uglify-js --minify > output.js

You can also compile an entire directory

$ yieldify input output

API

Individual files:

var compile = require('yieldify')

fs.writeFileSync('output.js', compile('input.js', fs.readFileSync('input.js', 'utf8')))

Entire direcotries:

var compile = require('yieldify')

compile.folder(input, output)

License

MIT