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

require-compiled

v1.5.0

Published

The easiest way to require babel-compiled modules.

Downloads

3

Readme

require-compiled

NPM version Build status Dependencies

require-compiled works just like regular require, except it allows you to require code written in newer versions of JS. Just add a .babelrc file to your project and you're good to go!

  // Read babel options our of your .babelrc:
  var requireCompiled = require('require-compiled');
  var myModule = requireCompiled('./my-module');
  var myModulePath = requireCompiled.resolve('./my-module');

  // Instead of using a .babelrc, you can also pass in your babel options explicitly:
  var requireCompiled = require('require-compiled').babelOptions({ ... });

Only the module directly required this way gets compiled. To compile some of its dependencies as well, mark them with a compile! flag:

  var myChildModule = require('compile!./child')

Behind the scenes the the modules required this way are compiled into a cache directory. Because of this, require-compiled does not need to load require hooks into your node process. require-compiled does load node-source-map-support to give you nice stack traces in your errors.

Thanks

The code of the amazing ava testrunner was a great inspiration and guide for this module.