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

node-require-async

v0.2.0

Published

A require function in node, but an asynchronous one.

Downloads

52

Readme

node-require-async

Build Status Coverage Status install size

A require function in node, but an asynchronous one.

This library is built on top of node's builtin Module, so it shares the module cache with require (It is not a wrapper function around builtin require).

Installation

npm install node-require-async

Example

entry.js

const requireAsync = require("node-require-async")(module);

requireAsync(require.resolve("./foo"))
  .then(foo => {
    foo.foo();
  });

foo.js

module.exports = {foo: () => console.log("foo")};
$ node entry.js
foo

API reference

This module exports a single function.

requireAsyncFactory(parentModule?): requireAsync function

You usually pass module as the parentModule parameter. requireAsync would help you setup parentModule.children when a module is loaded.

requireAsync(filename, extension?): moduleExports

Note that this function accepts a filename instead of a moduleId, which means that you have to resolve the moduleId into a filename before passing it to requireAsync:

const filename = require.resolve("./foo"); // "/path/to/foo.js"
requireAsync(filename).then(...)

Since builtin require.resolve is blocking, you may need other libraries to resolve filename asynchronously.

If parentModule exists, filename would be resolved as:

path.resolve(path.dirname(parentModule.filename), filename)

extension decides how to compile the file. If extension is .json then use JSON.parse. If extension is .js then use module._compile. Default: path.extname(filename).

Changelog

  • 0.2.0 (Jun 26, 2018)

    • Add: support JSON files.
    • Add: extension argument in requireAsync. It decides how to compile the content.
  • 0.1.2 (May 25, 2018)

    • Add: support relative path when parentModule is set.
  • 0.1.1 (May 22, 2018)

    • Fix: use files array.
  • 0.1.0 (May 22, 2018)

    • First release.