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

bruco

v1.1.1

Published

Find all require'd and imported npm packages in a file or array of files, both .js and .jsx

Downloads

8

Readme

bruco

Italian for "caterpillar"; a tree walker.

Use this module when you want to find all the packages loaded via require or import in either .js or .jsx(React) files. Native Node package names are ignored, as are packages with names not conforming to current npm naming standards (all lowercase, for example), as are local packages (e.g. require('./config.js')). Useful for doing things like checking whether you are using all the dependencies defined in your package.json file.

Install

npm install bruco

Test

npm test

Usage

let bruco = require('bruco');

Searching a single file

let packages = bruco('/path/to/someFile.js');
// packages now an Array of npm package names, e.g. ['lodash','express']

let packages = bruco('/path/to/someFile.jsx');
// packages now an Array of npm package names, e.g. ['react','react-dom','lodash']

Searching an array of files

let packages = bruco([
    '/path/to/file1.js',
    '/path/to/file2.js',
    '/path/to/file3.jsx'
    ...
]);

Recursively searching a directory

If a String path to a directory (instead of a file) is sent all files under that directory will be searched:

let packages = bruco('./')

You can nest these search kinds

let packages = bruco([
    '/path/to/dir', [
        '/nestedArr/1.js',
        '/another/dir',
        '/nestedArr/2.jsx'
    ],
    '/just/a/single/file.js'
    ...
]);

Options

All options are...optional:

  • ignore [Array or String] : Standard glob ignore rules.
  • all [Function] : Will receive an Array of all String literals found within require or import calls, including the ones that were not included in the final collection. This can be used to build a larger view of package loading across your application, for instance. Things like ../../utils.js or $anIllegalNpmPaCkAgEname.
let packages = bruco('/path/to/dir', {
    ignore : [
        '**/node_modules/**'
    ],
    all : a => debug('ALL:', a)
});