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

acquire

v0.4.0

Published

Require all modules from the node_modules directory, using Node module resolution algorithm to discover it

Downloads

13

Readme

npm

acquire

Build Status Dependency Status

Using Node module resolution algorithm, discover node_modules directory and require or require.resolve all modules in it.

API

acquire([opts])

Require all modules in node_modules, starting from opts.basedir.

Returns object of all the modules required:

{
  foo: require(path_to_foo),
  bar: require(path_to_bar)
}

| Option | Type | Required? | Default | | :----------- | :--------------- | :-------: | :---------- | | basedir | string | No | __dirname | | depth | number | No | 1 | | ignore | string/[string] | No | [] | | skipFailures | boolean/function | No | false |

If opts.depth is finite, it specifies the number of node_modules directories up the directory tree to traverse into. If opts.depth is Infinity, traversal ends at the file system root.

opts.ignore specifies module names to ignore.

If opts.skipFailures is true, modules that fail to require() (e.g. plugins for Grunt) are skipped. If opts.skipFailures is a function, it is called as opts.skipFailures(moduleName, modulePath) for each failure.

acquire.resolve([opts])

Require.resolve all modules in node_modules, starting from opts.basedir.

Returns object of all the modules and corresponding paths:

{
  foo: path_to_foo,
  bar: path_to_bar
}

Install

npm install acquire

License

MIT