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

riq-babel-register

v1.1.0

Published

babel require hook with relative caching

Downloads

7

Readme

riq-babel-register

The require hook will bind itself to node's require and automatically compile files on the fly.

This fork of babel-require supports file cache paths relative to a cacheSourceRoot as well as optional logging.

Install

$ npm install riq-babel-register

Usage

require("riq-babel-register")({
  presets: ['es2015', 'stage-0'],
  plugins: [
    ['streamline', {
        extensions: ['._js'],
        runtime: 'fibers',
        verbose: true
    }]
  ],
  cacheSourceRoot: __dirname,
  projectName: 'my-server',
  extensions: ['.es6', '.es', '.jsx', '.js', '._js'],
  debug: console.log.bind(console),
  log: console.log.bind(console)
});

All subsequent files required by node with the extensions .es6, .es, .jsx, .js and ._js will be transformed by Babel.

See documentation for details.

Changes in behavior from babel-register

When both cacheSourceRoot and projectName are provided files will be cached with project relative paths (e.g. fileName: 'my-server:/services/support/db._js'). As these are intended to be use in conjunction with with Heroku's cachedDirectories feature and the BABEL_CACHE_PATH environment variable to preserve cached across deploys/restarts, the mtime of the file is ignored and an MD5 hash of the files contents is used instead.

The log or debug functions are optional and when provided, riq-babel-register will use the provided functions to log it's progress. When omitted, riq-babel-register will log nothing.

In the absence of a BABEL_CACHE_PATH environment variable, transformed files will be stored in $HOME-OR_TMP/riq-babel-register.json

Consistent behavior with babel-register that will change in future versions

As of version 0.1.0 subsequent calls to riq-babel-register will replace any existing hooks with hooks generated with the new configuration. This means that if multiple modules within a project call riq-babel-register, the last caller will 'win'. Future versions will take the projectName and cacheSourceRoot into account and chain project transformations together allowing each project to control the transformation settings of it's own files.