Top Related Projects
glob functionality for node.js
Highly optimized wildcard and glob matching library. Faster, drop-in replacement to minimatch and multimatch. Used by square, webpack, babel core, yarn, jest, ract-native, taro, bulma, browser-sync, stylelint, nyc, ava, and many others! Follow micromatch's author: https://github.com/jonschlinkert
User-friendly glob matching
Quick Overview
fast-glob is a high-performance Node.js library for searching file system paths using glob patterns. It provides a fast and efficient way to find files and directories that match specific patterns, making it useful for tasks like file processing, build systems, and more.
Pros
- Extremely fast performance compared to other glob libraries
- Supports multiple glob patterns and negative patterns (exclusions)
- Provides both synchronous and asynchronous APIs
- Highly configurable with various options for fine-tuning behavior
Cons
- Limited to Node.js environments (not suitable for browser use)
- May have a steeper learning curve for users unfamiliar with glob patterns
- Some advanced features might require additional configuration
Code Examples
Finding all JavaScript files in a directory:
const fg = require('fast-glob');
const jsFiles = fg.sync(['**/*.js'], { cwd: 'src' });
console.log(jsFiles);
Excluding node_modules and using async API:
const fg = require('fast-glob');
(async () => {
const files = await fg(['**/*', '!**/node_modules/**']);
console.log(files);
})();
Using stream API for memory-efficient processing:
const fg = require('fast-glob');
const stream = fg.stream(['**/*.txt']);
stream.on('data', (entry) => {
console.log(entry);
});
stream.once('error', (error) => {
console.error(error);
});
Getting Started
To use fast-glob in your project, follow these steps:
-
Install the package:
npm install fast-glob
-
Import and use in your code:
const fg = require('fast-glob'); // Synchronous usage const files = fg.sync(['**/*.js', '!**/node_modules/**']); console.log(files); // Asynchronous usage (async () => { const asyncFiles = await fg(['**/*.js', '!**/node_modules/**']); console.log(asyncFiles); })();
This basic setup allows you to start using fast-glob for file searching in your Node.js projects. Refer to the project's documentation for more advanced usage and configuration options.
Competitor Comparisons
glob functionality for node.js
Pros of node-glob
- More established and widely used in the Node.js ecosystem
- Extensive documentation and community support
- Supports advanced features like
ignore
patterns andfollow
symlinks
Cons of node-glob
- Generally slower performance compared to fast-glob
- Less frequent updates and maintenance
- Larger package size and more dependencies
Code Comparison
node-glob:
const glob = require('glob');
glob('**/*.js', (err, files) => {
console.log(files);
});
fast-glob:
const glob = require('fast-glob');
(async () => {
const files = await glob('**/*.js');
console.log(files);
})();
Key Differences
- fast-glob is designed for performance and is generally faster than node-glob
- node-glob uses callbacks by default, while fast-glob uses Promises and supports async/await
- fast-glob has a smaller package size and fewer dependencies
- node-glob has more advanced features and options for complex use cases
- fast-glob supports streaming, which can be beneficial for handling large datasets
Both libraries serve similar purposes, but fast-glob is optimized for speed and modern JavaScript practices, while node-glob offers more advanced features and has a longer history in the Node.js ecosystem. The choice between them depends on specific project requirements, performance needs, and preferred coding style.
Highly optimized wildcard and glob matching library. Faster, drop-in replacement to minimatch and multimatch. Used by square, webpack, babel core, yarn, jest, ract-native, taro, bulma, browser-sync, stylelint, nyc, ava, and many others! Follow micromatch's author: https://github.com/jonschlinkert
Pros of micromatch
- More comprehensive pattern matching capabilities, including support for extended globbing syntax
- Highly customizable with numerous options for fine-tuning matching behavior
- Extensive documentation and examples for various use cases
Cons of micromatch
- Generally slower performance compared to fast-glob, especially for large file sets
- Higher memory usage due to its more complex matching engine
- Steeper learning curve for advanced features and options
Code Comparison
micromatch:
const micromatch = require('micromatch');
const result = micromatch(['file.txt', 'dir/subdir/file.js'], '**/*.js');
console.log(result); // ['dir/subdir/file.js']
fast-glob:
const fg = require('fast-glob');
const result = await fg('**/*.js', { cwd: process.cwd() });
console.log(result); // ['dir/subdir/file.js']
Both libraries provide glob pattern matching functionality, but fast-glob is primarily designed for file system operations, while micromatch offers more general-purpose string matching capabilities. fast-glob is optimized for performance and is often preferred for tasks involving large file sets or frequent file system scans. micromatch, on the other hand, provides more advanced pattern matching features and is suitable for a wider range of string matching scenarios beyond just file paths.
User-friendly glob matching
Pros of globby
- More feature-rich, offering additional functionality like
.gitignore
support and multiple patterns - Better documentation and examples
- Actively maintained with frequent updates
Cons of globby
- Slightly slower performance compared to fast-glob
- Larger package size due to additional features
Code Comparison
fast-glob:
const fg = require('fast-glob');
(async () => {
const entries = await fg(['**/*.js', '!**/node_modules/**']);
console.log(entries);
})();
globby:
const globby = require('globby');
(async () => {
const paths = await globby(['**/*.js', '!**/node_modules/**']);
console.log(paths);
})();
Both libraries offer similar basic functionality for glob pattern matching. The main differences lie in the additional features and performance characteristics. fast-glob focuses on speed and simplicity, while globby provides a more comprehensive set of features at the cost of slightly lower performance and a larger package size. The choice between the two depends on the specific requirements of your project, such as the need for advanced features or prioritizing speed.
Convert designs to code with AI
Introducing Visual Copilot: A new AI model to turn Figma designs to high quality code using your components.
Try Visual CopilotREADME
fast-glob
This package provides methods for traversing the file system and returning pathnames that matched a defined set of a specified pattern according to the rules used by the Unix Bash shell with some simplifications, meanwhile results are returned in arbitrary order. Quick, simple, effective.
Table of Contents
Highlights
- Fast. Probably the fastest.
- Supports multiple and negative patterns.
- Synchronous, Promise and Stream API.
- Object mode. Can return more than just strings.
- Error-tolerant.
Pattern syntax
:warning: Always use forward-slashes in glob expressions (patterns and
ignore
option). Use backslashes for escaping characters.
There is more than one form of syntax: basic and advanced. Below is a brief overview of the supported features. Also pay attention to our FAQ.
:book: This package uses
micromatch
as a library for pattern matching.
Basic syntax
- An asterisk (
*
) â matches everything except slashes (path separators), hidden files (names starting with.
). - A double star or globstar (
**
) â matches zero or more directories. - Question mark (
?
) â matches any single character except slashes (path separators). - Sequence (
[seq]
) â matches any character in sequence.
:book: A few additional words about the basic matching behavior.
Some examples:
src/**/*.js
â matches all files in thesrc
directory (any level of nesting) that have the.js
extension.src/*.??
â matches all files in thesrc
directory (only first level of nesting) that have a two-character extension.file-[01].js
â matches files:file-0.js
,file-1.js
.
Advanced syntax
- Escapes characters (
\\
) â matching special characters ($^*+?()[]
) as literals. - POSIX character classes (
[[:digit:]]
). - Extended globs (
?(pattern-list)
). - Bash style brace expansions (
{}
). - Regexp character classes (
[1-5]
). - Regex groups (
(a|b)
).
:book: A few additional words about the advanced matching behavior.
Some examples:
src/**/*.{css,scss}
â matches all files in thesrc
directory (any level of nesting) that have the.css
or.scss
extension.file-[[:digit:]].js
â matches files:file-0.js
,file-1.js
, â¦,file-9.js
.file-{1..3}.js
â matches files:file-1.js
,file-2.js
,file-3.js
.file-(1|2)
â matches files:file-1.js
,file-2.js
.
Installation
npm install fast-glob
API
Asynchronous
fg.glob(patterns, [options])
fg.async(patterns, [options])
Returns a Promise
with an array of matching entries.
const fg = require('fast-glob');
const entries = await fg.glob(['.editorconfig', '**/index.js'], { dot: true });
// ['.editorconfig', 'services/index.js']
Synchronous
fg.globSync(patterns, [options])
Returns an array of matching entries.
const fg = require('fast-glob');
const entries = fg.globSync(['.editorconfig', '**/index.js'], { dot: true });
// ['.editorconfig', 'services/index.js']
Stream
fg.globStream(patterns, [options])
fg.stream(patterns, [options])
Returns a ReadableStream
when the data
event will be emitted with matching entry.
const fg = require('fast-glob');
const stream = fg.globStream(['.editorconfig', '**/index.js'], { dot: true });
for await (const entry of stream) {
// .editorconfig
// services/index.js
}
patterns
- Required:
true
- Type:
string | string[]
Any correct pattern(s).
:1234: Pattern syntax
:warning: This package does not respect the order of patterns. First, all the negative patterns are applied, and only then the positive patterns. If you want to get a certain order of records, use sorting or split calls.
[options]
- Required:
false
- Type:
Options
See Options section.
Helpers
generateTasks(patterns, [options])
Returns the internal representation of patterns (Task
is a combining patterns by base directory).
fg.generateTasks('*');
[{
base: '.', // Parent directory for all patterns inside this task
dynamic: true, // Dynamic or static patterns are in this task
patterns: ['*'],
positive: ['*'],
negative: []
}]
patterns
- Required:
true
- Type:
string | string[]
Any correct pattern(s).
[options]
- Required:
false
- Type:
Options
See Options section.
isDynamicPattern(pattern, [options])
Returns true
if the passed pattern is a dynamic pattern.
fg.isDynamicPattern('*'); // true
fg.isDynamicPattern('abc'); // false
pattern
- Required:
true
- Type:
string
Any correct pattern.
[options]
- Required:
false
- Type:
Options
See Options section.
escapePath(path)
Returns the path with escaped special characters depending on the platform.
- Posix:
*?|(){}[]
;!
at the beginning of line;@+!
before the opening parenthesis;\\
before non-special characters;
- Windows:
(){}[]
!
at the beginning of line;@+!
before the opening parenthesis;- Characters like
*?|
cannot be used in the path (windows_naming_conventions), so they will not be escaped;
fg.escapePath('!abc');
// \\!abc
fg.escapePath('[OpenSource] mrmlnc â fast-glob (Deluxe Edition) 2014') + '/*.flac'
// \\[OpenSource\\] mrmlnc â fast-glob \\(Deluxe Edition\\) 2014/*.flac
fg.posix.escapePath('C:\\Program Files (x86)\\**\\*');
// C:\\\\Program Files \\(x86\\)\\*\\*\\*
fg.win32.escapePath('C:\\Program Files (x86)\\**\\*');
// Windows: C:\\Program Files \\(x86\\)\\**\\*
convertPathToPattern(path)
Converts a path to a pattern depending on the platform, including special character escaping.
- Posix. Works similarly to the
fg.posix.escapePath
method. - Windows. Works similarly to the
fg.win32.escapePath
method, additionally converting backslashes to forward slashes in cases where they are not escape characters (!()+@{}[]
).
fg.convertPathToPattern('[OpenSource] mrmlnc â fast-glob (Deluxe Edition) 2014') + '/*.flac';
// \\[OpenSource\\] mrmlnc â fast-glob \\(Deluxe Edition\\) 2014/*.flac
fg.convertPathToPattern('C:/Program Files (x86)/**/*');
// Posix: C:/Program Files \\(x86\\)/\\*\\*/\\*
// Windows: C:/Program Files \\(x86\\)/**/*
fg.convertPathToPattern('C:\\Program Files (x86)\\**\\*');
// Posix: C:\\\\Program Files \\(x86\\)\\*\\*\\*
// Windows: C:/Program Files \\(x86\\)/**/*
fg.posix.convertPathToPattern('\\\\?\\c:\\Program Files (x86)') + '/**/*';
// Posix: \\\\\\?\\\\c:\\\\Program Files \\(x86\\)/**/* (broken pattern)
fg.win32.convertPathToPattern('\\\\?\\c:\\Program Files (x86)') + '/**/*';
// Windows: //?/c:/Program Files \\(x86\\)/**/*
Options
Common options
cwd
- Type:
string
- Default:
process.cwd()
The current working directory in which to search.
deep
- Type:
number
- Default:
Infinity
Specifies the maximum depth of a read directory relative to the start directory.
For example, you have the following tree:
dir/
âââ one/ // 1
âââ two/ // 2
âââ file.js // 3
// With base directory
fg.globSync('dir/**', { onlyFiles: false, deep: 1 }); // ['dir/one']
fg.globSync('dir/**', { onlyFiles: false, deep: 2 }); // ['dir/one', 'dir/one/two']
// With cwd option
fg.globSync('**', { onlyFiles: false, cwd: 'dir', deep: 1 }); // ['one']
fg.globSync('**', { onlyFiles: false, cwd: 'dir', deep: 2 }); // ['one', 'one/two']
:book: If you specify a pattern with some base directory, this directory will not participate in the calculation of the depth of the found directories. Think of it as a
cwd
option.
followSymbolicLinks
- Type:
boolean
- Default:
true
Indicates whether to traverse descendants of symbolic link directories when expanding **
patterns.
:book: Note that this option does not affect the base directory of the pattern. For example, if
./a
is a symlink to directory./b
and you specified['./a**', './b/**']
patterns, then directory./a
will still be read.
:book: If the
stats
option is specified, the information about the symbolic link (fs.lstat
) will be replaced with information about the entry (fs.stat
) behind it.
fs
- Type:
FileSystemAdapter
- Default:
fs.*
Custom implementation of methods for working with the file system. Supports objects with enumerable properties only.
export interface FileSystemAdapter {
lstat?: typeof fs.lstat;
stat?: typeof fs.stat;
lstatSync?: typeof fs.lstatSync;
statSync?: typeof fs.statSync;
readdir?: typeof fs.readdir;
readdirSync?: typeof fs.readdirSync;
}
ignore
- Type:
string[]
- Default:
[]
An array of glob patterns to exclude matches. This is an alternative way to use negative patterns.
dir/
âââ package-lock.json
âââ package.json
fg.globSync(['*.json', '!package-lock.json']); // ['package.json']
fg.globSync('*.json', { ignore: ['package-lock.json'] }); // ['package.json']
suppressErrors
- Type:
boolean
- Default:
false
By default this package suppress only ENOENT
errors. Set to true
to suppress any error.
:book: Can be useful when the directory has entries with a special level of access.
throwErrorOnBrokenSymbolicLink
- Type:
boolean
- Default:
false
Throw an error when symbolic link is broken if true
or safely return lstat
call if false
.
:book: This option has no effect on errors when reading the symbolic link directory.
Output control
absolute
- Type:
boolean
- Default:
false
Return the absolute path for entries.
fg.globSync('*.js', { absolute: false }); // ['index.js']
fg.globSync('*.js', { absolute: true }); // ['/home/user/index.js']
:book: This option is required if you want to use negative patterns with absolute path, for example,
!${__dirname}/*.js
.
markDirectories
- Type:
boolean
- Default:
false
Mark the directory path with the final slash.
fg.globSync('*', { onlyFiles: false, markDirectories: false }); // ['index.js', 'controllers']
fg.globSync('*', { onlyFiles: false, markDirectories: true }); // ['index.js', 'controllers/']
objectMode
- Type:
boolean
- Default:
false
Returns objects (instead of strings) describing entries.
fg.globSync('*', { objectMode: false }); // ['src/index.js']
fg.globSync('*', { objectMode: true }); // [{ name: 'index.js', path: 'src/index.js', dirent: <fs.Dirent> }]
The object has the following fields:
- name (
string
) â the last part of the path (basename) - path (
string
) â full path relative to the pattern base directory - dirent (
fs.Dirent
) â instance offs.Dirent
:book: An object is an internal representation of entry, so getting it does not affect performance.
onlyDirectories
- Type:
boolean
- Default:
false
Return only directories.
fg.globSync('*', { onlyDirectories: false }); // ['index.js', 'src']
fg.globSync('*', { onlyDirectories: true }); // ['src']
:book: If
true
, theonlyFiles
option is automaticallyfalse
.
onlyFiles
- Type:
boolean
- Default:
true
Return only files.
fg.globSync('*', { onlyFiles: false }); // ['index.js', 'src']
fg.globSync('*', { onlyFiles: true }); // ['index.js']
stats
- Type:
boolean
- Default:
false
Enables an object mode with an additional field:
- stats (
fs.Stats
) â instance offs.Stats
fg.globSync('*', { stats: false }); // ['src/index.js']
fg.globSync('*', { stats: true }); // [{ name: 'index.js', path: 'src/index.js', dirent: <fs.Dirent>, stats: <fs.Stats> }]
:book: Returns
fs.stat
instead offs.lstat
for symbolic links when thefollowSymbolicLinks
option is specified.
unique
- Type:
boolean
- Default:
true
Ensures that the returned entries are unique.
fg.globSync(['*.json', 'package.json'], { unique: false }); // ['package.json', 'package.json']
fg.globSync(['*.json', 'package.json'], { unique: true }); // ['package.json']
If true
and similar entries are found, the result is the first found.
Matching control
braceExpansion
- Type:
boolean
- Default:
true
Enables Bash-like brace expansion.
:1234: Syntax description or more detailed description.
dir/
âââ abd
âââ acd
âââ a{b,c}d
fg.globSync('a{b,c}d', { braceExpansion: false }); // ['a{b,c}d']
fg.globSync('a{b,c}d', { braceExpansion: true }); // ['abd', 'acd']
caseSensitiveMatch
- Type:
boolean
- Default:
true
Enables a case-sensitive mode for matching files.
dir/
âââ file.txt
âââ File.txt
fg.globSync('file.txt', { caseSensitiveMatch: false }); // ['file.txt', 'File.txt']
fg.globSync('file.txt', { caseSensitiveMatch: true }); // ['file.txt']
dot
- Type:
boolean
- Default:
false
Allow patterns to match entries that begin with a period (.
).
:book: Note that an explicit dot in a portion of the pattern will always match dot files.
dir/
âââ .editorconfig
âââ package.json
fg.globSync('*', { dot: false }); // ['package.json']
fg.globSync('*', { dot: true }); // ['.editorconfig', 'package.json']
extglob
- Type:
boolean
- Default:
true
Enables Bash-like extglob
functionality.
:1234: Syntax description.
dir/
âââ README.md
âââ package.json
fg.globSync('*.+(json|md)', { extglob: false }); // []
fg.globSync('*.+(json|md)', { extglob: true }); // ['README.md', 'package.json']
globstar
- Type:
boolean
- Default:
true
Enables recursively repeats a pattern containing **
. If false
, **
behaves exactly like *
.
dir/
âââ a
âââ b
fg.globSync('**', { onlyFiles: false, globstar: false }); // ['a']
fg.globSync('**', { onlyFiles: false, globstar: true }); // ['a', 'a/b']
baseNameMatch
- Type:
boolean
- Default:
false
If set to true
, then patterns without slashes will be matched against the basename of the path if it contains slashes.
dir/
âââ one/
âââ file.md
fg.globSync('*.md', { baseNameMatch: false }); // []
fg.globSync('*.md', { baseNameMatch: true }); // ['one/file.md']
FAQ
What is a static or dynamic pattern?
All patterns can be divided into two types:
- static. A pattern is considered static if it can be used to get an entry on the file system without using matching mechanisms. For example, the
file.js
pattern is a static pattern because we can just verify that it exists on the file system. - dynamic. A pattern is considered dynamic if it cannot be used directly to find occurrences without using a matching mechanisms. For example, the
*
pattern is a dynamic pattern because we cannot use this pattern directly.
A pattern is considered dynamic if it contains the following characters (â¦
â any characters or their absence) or options:
- The
caseSensitiveMatch
option is disabled \\
(the escape character)*
,?
,!
(at the beginning of line)[â¦]
(â¦|â¦)
@(â¦)
,!(â¦)
,*(â¦)
,?(â¦)
,+(â¦)
(respects theextglob
option){â¦,â¦}
,{â¦..â¦}
(respects thebraceExpansion
option)
How to write patterns on Windows?
Always use forward-slashes in glob expressions (patterns and ignore
option). Use backslashes for escaping characters. With the cwd
option use a convenient format.
Bad
[
'directory\\*',
path.join(process.cwd(), '**')
]
Good
[
'directory/*',
fg.convertPathToPattern(process.cwd()) + '/**'
]
:book: Use the
.convertPathToPattern
package to convert Windows-style path to a Unix-style path.
Read more about matching with backslashes.
Why are parentheses match wrong?
dir/
âââ (special-*file).txt
fg.globSync(['(special-*file).txt']) // []
Refers to Bash. You need to escape special characters:
fg.globSync(['\\(special-*file\\).txt']) // ['(special-*file).txt']
Read more about matching special characters as literals. Or use the .escapePath
.
How to exclude directory from reading?
You can use a negative pattern like this: !**/node_modules
or !**/node_modules/**
. Also you can use ignore
option. Just look at the example below.
first/
âââ file.md
âââ second/
âââ file.txt
If you don't want to read the second
directory, you must write the following pattern: !**/second
or !**/second/**
.
fg.globSync(['**/*.md', '!**/second']); // ['first/file.md']
fg.globSync(['**/*.md'], { ignore: ['**/second/**'] }); // ['first/file.md']
:warning: When you write
!**/second/**/*
it means that the directory will be read, but all the entries will not be included in the results.
You have to understand that if you write the pattern to exclude directories, then the directory will not be read under any circumstances.
How to use UNC path?
You cannot use Uniform Naming Convention (UNC) paths as patterns (due to syntax) directly, but you can use them as cwd
directory or use the fg.convertPathToPattern
method.
// cwd
fg.globSync('*', { cwd: '\\\\?\\C:\\Python27' /* or //?/C:/Python27 */ });
fg.globSync('Python27/*', { cwd: '\\\\?\\C:\\' /* or //?/C:/ */ });
// .convertPathToPattern
fg.globSync(fg.convertPathToPattern('\\\\?\\c:\\Python27') + '/*');
Compatible with node-glob
?
node-glob | fast-glob |
---|---|
cwd | cwd |
root | â |
dot | dot |
nomount | â |
mark | markDirectories |
nosort | â |
nounique | unique |
nobrace | braceExpansion |
noglobstar | globstar |
noext | extglob |
nocase | caseSensitiveMatch |
matchBase | baseNameMatch |
nodir | onlyFiles |
ignore | ignore |
follow | followSymbolicLinks |
realpath | â |
absolute | absolute |
Benchmarks
You can see results here for every commit into the main
branch.
- Product benchmark â comparison with the main competitors.
- Regress benchmark â regression between the current version and the version from the npm registry.
Changelog
See the Releases section of our GitHub project for changelog for each release version.
License
This software is released under the terms of the MIT license.
Top Related Projects
glob functionality for node.js
Highly optimized wildcard and glob matching library. Faster, drop-in replacement to minimatch and multimatch. Used by square, webpack, babel core, yarn, jest, ract-native, taro, bulma, browser-sync, stylelint, nyc, ava, and many others! Follow micromatch's author: https://github.com/jonschlinkert
User-friendly glob matching
Convert designs to code with AI
Introducing Visual Copilot: A new AI model to turn Figma designs to high quality code using your components.
Try Visual Copilot