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 🙏

© 2026 – Pkg Stats / Ryan Hefner

globulesce

v2.0.0

Published

applies a glob pattern to a set of files *after* excluding specific subfolders

Readme

globulesce

Need a list of files matching a set of glob patterns? Need to exclude certain subfolders? Need it fast? Try globulesce! It's as fast as its name is gross.

[![Build Status][travis-image]][travis-url] [![Coverage Status][coveralls-image]][coveralls-url]

Fully async, promise-based API. Now with TypeScript support and ESM!

Requirements

  • Node.js 22+ (uses native ESM and modern JavaScript features)

Installation

npm install globulesce

API

scan(path, match, ignore, options)

Returns a Promise<string[]> containing absolute file paths matching the specified patterns.

Parameters:

  • path (string): The directory to start scanning in (inclusive)
  • match (string | string[], optional): A glob pattern or array of patterns to match files against. Defaults to ['**/*.*']
  • ignore (string[], optional): Directories to ignore. Defaults to ['.git', 'node_modules']. Pass an empty array to include these folders
  • options (ScanOptions, optional): Configuration options

Options (ScanOptions):

interface ScanOptions {
  directories?: boolean  // Return directories instead of files
  dot?: boolean         // Include dotfiles (default: true)
  nocase?: boolean      // Case-insensitive matching (default: true)
  matchBase?: boolean   // Match basename only (default: false)
}

TypeScript Usage

import { scan } from 'globulesce'

// Get all JavaScript files
const files = await scan('./', ['**/*.js'], ['.git', 'node_modules'])

// Get directories only
const dirs = await scan('./', ['*'], ['.git', 'node_modules'], { directories: true })

// With type safety
const results: string[] = await scan('./src', '**/*.ts')

JavaScript (ESM) Usage

import { scan } from 'globulesce'

const files = await scan('./', ['**/*.js'], ['.git', 'node_modules'])

Legacy CommonJS Migration

v2.0.0 is a breaking change. This library is now ESM-only and requires Node.js 22+.

If you're upgrading from v1.x:

// Old (v1.x - CommonJS)
const glob = require('globulesce')
glob('./', ['**/*.js']).then(files => { ... })

// New (v2.x - ESM)
import { scan } from 'globulesce'
const files = await scan('./', ['**/*.js'])

Migration Steps:

  1. Upgrade to Node.js 22 or higher
  2. Add "type": "module" to your package.json
  3. Change require() to import
  4. Use top-level await or keep using .then()

The ignore directory ignores all directories with a matching name regardless of depth

For my purposes, when I need to ignore a directory, I always want to ignore it. This may not be helpful. If you need different behavior, send a PR :D

Dependencies

This library does almost nothing and relies almost entirely on

  • minimatch

Why Reinvent The Wheel!?

I needed a way to scan a directory tree for files that wouldn't first eagerly scan .git and node_modules. There are several NPM libs that promise to do this but don't. The end result is that you wait a few seconds whilst they tear through an entire tree and then proceed to toss a bunch of results out (or don't even do that).

None of my specific use cases care about what are in .git or node_modules and are time sensitive.