fast-glob vs glob vs glob-all vs globby vs node-glob
File System Glob Libraries
fast-globglobglob-allglobbynode-globSimilar Packages:

File System Glob Libraries

File system glob libraries in Node.js provide developers with tools to match files and directories using patterns, known as globs. These libraries allow for efficient file searching, filtering, and manipulation based on specified criteria, such as wildcards, character ranges, and more. They are particularly useful for tasks like file system traversal, build scripts, and automation tasks, where selecting files based on patterns is required. These libraries help streamline file-related operations, improve code readability, and enhance overall productivity in web development. fast-glob is a high-performance library that supports asynchronous operations and offers faster file matching, making it ideal for large projects. glob is a widely-used, simple library that provides basic globbing functionality with a straightforward API. glob-all extends glob by allowing multiple patterns to be matched simultaneously, which is useful for more complex file selection tasks. globby is a modern library built on top of fast-glob that offers a more user-friendly API, supports multiple patterns, and provides additional features like ignoring files and directories. node-glob is the original implementation of the globbing algorithm in Node.js, providing a reliable and efficient way to match files and directories based on patterns. It is the foundation for many other globbing libraries and is known for its stability and performance.

Npm Package Weekly Downloads Trend

3 Years

Github Stars Ranking

Stat Detail

Package
Downloads
Stars
Size
Issues
Publish
License
fast-glob02,80898.4 kB41a year agoMIT
glob08,7211.61 MB32 months agoBlueOak-1.0.0
glob-all05612.5 kB6-MIT
globby02,64191.9 kB0a month agoMIT
node-glob02-110 years agoBSD-3-Clause

Feature Comparison: fast-glob vs glob vs glob-all vs globby vs node-glob

Performance

  • fast-glob:

    fast-glob is designed for high performance, especially when dealing with large file systems. It uses optimized algorithms and supports asynchronous operations, making it faster than traditional globbing libraries.

  • glob:

    glob provides decent performance for basic file matching tasks, but it may not be as efficient as fast-glob for large directories or complex patterns. It is suitable for most everyday use cases.

  • glob-all:

    glob-all inherits the performance characteristics of glob but adds overhead when matching multiple patterns simultaneously. It is efficient for tasks that require combining multiple globs, but performance may vary depending on the complexity of the patterns.

  • globby:

    globby leverages fast-glob under the hood, providing high performance while offering a more user-friendly API. It is a good choice for projects that need both speed and ease of use.

  • node-glob:

    node-glob is a reliable and efficient implementation of the globbing algorithm, providing good performance for file matching tasks. It is optimized for typical use cases and is widely used in the Node.js ecosystem.

API Design

  • fast-glob:

    fast-glob provides a simple API for both synchronous and asynchronous file matching. It supports advanced features like ignoring files, deep directory traversal, and custom filters, making it versatile for various use cases.

  • glob:

    glob offers a straightforward API for matching files based on a single pattern. It is easy to use and well-documented, making it accessible for developers of all skill levels.

  • glob-all:

    glob-all extends the glob API to allow matching multiple patterns at once. It provides additional functionality while maintaining the simplicity of the original glob interface.

  • globby:

    globby offers a modern, intuitive API that supports multiple patterns, ignoring files, and other advanced features. It is designed to be easy to use while providing more functionality than traditional globbing libraries.

  • node-glob:

    node-glob provides a simple and efficient API for matching files based on patterns. It is the standard implementation of globbing in Node.js and is designed to be easy to use and integrate into other projects.

Multiple Patterns

  • fast-glob:

    fast-glob supports multiple patterns and allows for complex matching scenarios, including the ability to specify include and exclude patterns. This makes it flexible for a wide range of file matching tasks.

  • glob:

    glob primarily supports a single pattern for matching files. While it is possible to use multiple patterns by calling the function multiple times, it does not natively support matching multiple patterns simultaneously.

  • glob-all:

    glob-all is specifically designed to handle multiple patterns at once, allowing for more efficient matching of files based on a combination of patterns. This is its main advantage over the standard glob library.

  • globby:

    globby excels at handling multiple patterns, including support for both include and exclude patterns. It provides a clean and intuitive way to work with multiple globs, making it ideal for complex file matching tasks.

  • node-glob:

    node-glob supports multiple patterns by allowing the use of braces {} to specify a set of patterns within a single string. However, it does not provide advanced features for handling multiple patterns beyond this basic functionality.

Ignoring Files

  • fast-glob:

    fast-glob allows for ignoring files and directories using the ignore option. This feature is efficient and can be used to exclude specific paths or patterns from the matching process, helping to optimize performance and reduce unnecessary file traversal.

  • glob:

    glob supports ignoring files by using the ignore option, which allows you to specify patterns that should be excluded from the matching results. This feature is straightforward and integrates well with the overall globbing process.

  • glob-all:

    glob-all inherits the ignoring capabilities of glob and allows for more complex scenarios where multiple patterns are matched, and certain files or directories need to be excluded. It is useful for tasks that require fine-grained control over which files are included or excluded.

  • globby:

    globby provides a more advanced and user-friendly way to ignore files and directories. It supports multiple ignore patterns and integrates seamlessly with its API, making it easy to exclude files while matching others.

  • node-glob:

    node-glob supports ignoring files through the ignore option, which allows you to specify patterns that should be excluded from the results. This feature is simple and effective, making it easy to exclude unwanted files during the globbing process.

Ease of Use: Code Examples

  • fast-glob:

    fast-glob is easy to use, especially for developers familiar with asynchronous programming in Node.js. Its documentation is clear, and it provides examples for both simple and advanced use cases.

  • glob:

    glob is known for its simplicity and ease of use. Its API is straightforward, and it has extensive documentation and examples that make it easy for developers to get started quickly.

  • glob-all:

    glob-all builds on the simplicity of glob while adding functionality for multiple patterns. Its documentation provides clear examples of how to use the extended features, making it accessible to users.

  • globby:

    globby is designed to be user-friendly, with a clean API and comprehensive documentation. It provides examples that demonstrate how to use its features effectively, making it a good choice for developers looking for a modern globbing solution.

  • node-glob:

    node-glob has a simple and intuitive API that is well-documented. As the standard globbing implementation in Node.js, it is widely understood and used, making it easy for developers to integrate into their projects.

How to Choose: fast-glob vs glob vs glob-all vs globby vs node-glob

  • fast-glob:

    Choose fast-glob if you need high-performance file matching with support for asynchronous operations. It is particularly useful for projects with large file systems where speed is a concern.

  • glob:

    Choose glob if you need a simple and reliable solution for basic file matching tasks. It is easy to use and well-documented, making it a good choice for straightforward applications.

  • glob-all:

    Choose glob-all if you need to match multiple patterns simultaneously and want to extend the functionality of the glob library. It is useful for more complex file selection tasks that require combining multiple patterns.

  • globby:

    Choose globby if you want a modern, user-friendly API for file matching that supports multiple patterns, ignoring files, and other advanced features. It is built on top of fast-glob, so it offers good performance while being easy to use.

  • node-glob:

    Choose node-glob if you need a stable and efficient implementation of the globbing algorithm that is widely used and trusted. It is the foundation for many other libraries and provides reliable performance for file matching tasks.

README for fast-glob

fast-glob

It's a very fast and efficient glob library for Node.js.

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

Details

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.

Old and modern mode

This package works in two modes, depending on the environment in which it is used.

  • Old mode. Node.js below 10.10 or when the stats option is enabled.
  • Modern mode. Node.js 10.10+ and the stats option is disabled.

The modern mode is faster. Learn more about the internal mechanism.

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 the src directory (any level of nesting) that have the .js extension.
  • src/*.?? — matches all files in the src 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

:book: A few additional words about the advanced matching behavior.

Some examples:

  • src/**/*.{css,scss} — matches all files in the src 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(patterns, [options])
fg.async(patterns, [options])
fg.glob(patterns, [options])

Returns a Promise with an array of matching entries.

const fg = require('fast-glob');

const entries = await fg(['.editorconfig', '**/index.js'], { dot: true });

// ['.editorconfig', 'services/index.js']

Synchronous

fg.sync(patterns, [options])
fg.globSync(patterns, [options])

Returns an array of matching entries.

const fg = require('fast-glob');

const entries = fg.sync(['.editorconfig', '**/index.js'], { dot: true });

// ['.editorconfig', 'services/index.js']

Stream

fg.stream(patterns, [options])
fg.globStream(patterns, [options])

Returns a ReadableStream when the data event will be emitted with matching entry.

const fg = require('fast-glob');

const stream = fg.stream(['.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]

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]

See Options section.

isDynamicPattern(pattern, [options])

Returns true if the passed pattern is a dynamic pattern.

:1234: What is a static or dynamic pattern?

fg.isDynamicPattern('*'); // true
fg.isDynamicPattern('abc'); // false
pattern
  • Required: true
  • Type: string

Any correct pattern.

[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

concurrency

  • Type: number
  • Default: os.cpus().length

Specifies the maximum number of concurrent requests from a reader to read directories.

:book: The higher the number, the higher the performance and load on the file system. If you want to read in quiet mode, set the value to a comfortable number or 1.

More details

In Node, there are two types of threads: Event Loop (code) and a Thread Pool (fs, dns, …). The thread pool size controlled by the UV_THREADPOOL_SIZE environment variable. Its default size is 4 (documentation). The pool is one for all tasks within a single Node process.

Any code can make 4 real concurrent accesses to the file system. The rest of the FS requests will wait in the queue.

:book: Each new instance of FG in the same Node process will use the same Thread pool.

But this package also has the concurrency option. This option allows you to control the number of concurrent accesses to the FS at the package level. By default, this package has a value equal to the number of cores available for the current Node process. This allows you to set a value smaller than the pool size (concurrency: 1) or, conversely, to prepare tasks for the pool queue more quickly (concurrency: Number.POSITIVE_INFINITY).

So, in fact, this package can only make 4 concurrent requests to the FS. You can increase this value by using an environment variable (UV_THREADPOOL_SIZE), but in practice this does not give a multiple advantage.

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.sync('dir/**', { onlyFiles: false, deep: 1 }); // ['dir/one']
fg.sync('dir/**', { onlyFiles: false, deep: 2 }); // ['dir/one', 'dir/one/two']

// With cwd option
fg.sync('**', { onlyFiles: false, cwd: 'dir', deep: 1 }); // ['one']
fg.sync('**', { 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.sync(['*.json', '!package-lock.json']);            // ['package.json']
fg.sync('*.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.sync('*.js', { absolute: false }); // ['index.js']
fg.sync('*.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.sync('*', { onlyFiles: false, markDirectories: false }); // ['index.js', 'controllers']
fg.sync('*', { onlyFiles: false, markDirectories: true });  // ['index.js', 'controllers/']

objectMode

  • Type: boolean
  • Default: false

Returns objects (instead of strings) describing entries.

fg.sync('*', { objectMode: false }); // ['src/index.js']
fg.sync('*', { 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 of fs.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.sync('*', { onlyDirectories: false }); // ['index.js', 'src']
fg.sync('*', { onlyDirectories: true });  // ['src']

:book: If true, the onlyFiles option is automatically false.

onlyFiles

  • Type: boolean
  • Default: true

Return only files.

fg.sync('*', { onlyFiles: false }); // ['index.js', 'src']
fg.sync('*', { onlyFiles: true });  // ['index.js']

stats

  • Type: boolean
  • Default: false

Enables an object mode with an additional field:

  • stats (fs.Stats) — instance of fs.Stats
fg.sync('*', { stats: false }); // ['src/index.js']
fg.sync('*', { stats: true });  // [{ name: 'index.js', path: 'src/index.js', dirent: <fs.Dirent>, stats: <fs.Stats> }]

:book: Returns fs.stat instead of fs.lstat for symbolic links when the followSymbolicLinks option is specified.

:warning: Unlike object mode this mode requires additional calls to the file system. On average, this mode is slower at least twice. See old and modern mode for more details.

unique

  • Type: boolean
  • Default: true

Ensures that the returned entries are unique.

fg.sync(['*.json', 'package.json'], { unique: false }); // ['package.json', 'package.json']
fg.sync(['*.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.sync('a{b,c}d', { braceExpansion: false }); // ['a{b,c}d']
fg.sync('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.sync('file.txt', { caseSensitiveMatch: false }); // ['file.txt', 'File.txt']
fg.sync('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.sync('*', { dot: false }); // ['package.json']
fg.sync('*', { dot: true });  // ['.editorconfig', 'package.json']

extglob

  • Type: boolean
  • Default: true

Enables Bash-like extglob functionality.

:1234: Syntax description.

dir/
├── README.md
└── package.json
fg.sync('*.+(json|md)', { extglob: false }); // []
fg.sync('*.+(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.sync('**', { onlyFiles: false, globstar: false }); // ['a']
fg.sync('**', { 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.sync('*.md', { baseNameMatch: false }); // []
fg.sync('*.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 the extglob option)
  • {…,…}, {…..…} (respects the braceExpansion 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.sync(['(special-*file).txt']) // []

Refers to Bash. You need to escape special characters:

fg.sync(['\\(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.sync(['**/*.md', '!**/second']);                 // ['first/file.md']
fg.sync(['**/*.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.sync('*', { cwd: '\\\\?\\C:\\Python27' /* or //?/C:/Python27 */ });
fg.sync('Python27/*', { cwd: '\\\\?\\C:\\' /* or //?/C:/ */ });

// .convertPathToPattern
fg.sync(fg.convertPathToPattern('\\\\?\\c:\\Python27') + '/*');

Compatible with node-glob?

node-globfast-glob
cwdcwd
root
dotdot
nomount
markmarkDirectories
nosort
nouniqueunique
nobracebraceExpansion
noglobstarglobstar
noextextglob
nocasecaseSensitiveMatch
matchBasebaseNameMatch
nodironlyFiles
ignoreignore
followfollowSymbolicLinks
realpath
absoluteabsolute

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.