expand-braces
Advanced tools
Wrapper for [braces] to enable brace expansion for arrays of patterns.
Wrapper for [braces] to enable brace expansion for arrays of patterns.
Install with npm
$ npm i expand-braces --save
var expand = require('expand-braces');
Pass an array or list of strings:
expand('{foo,bar}', '{baz,quux}');
// or
expand(['{foo,bar}', '{baz,quux}']);
// both yield => [ 'foo', 'bar', 'baz', 'quux' ];
Pass a function as the last argument to customize output:
expand(['{a..e}', '{f..h}'], function (str) {
return '_' + str;
});
//=> ['_a', '_b', '_c', '_d', '_e', '_f', '_g', '_h']
true if the given string looks like a glob pattern or an extglob pattern.… more | homepageInstall dev dependencies:
$ npm i -d && npm test
Pull requests and stars are always welcome. For bugs and feature requests, please create an issue.
Jon Schlinkert
Copyright © 2015 Jon Schlinkert Released under the MIT license.
This file was generated by verb-cli on October 31, 2015.
FAQs
Wrapper for [braces] to enable brace expansion for arrays of patterns.
The npm package expand-braces receives a total of 131,639 weekly downloads. As such, expand-braces popularity was classified as popular.
We found that expand-braces demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Research
The Socket Research Team breaks down a malicious wrapper package that uses obfuscation to harvest credentials and exfiltrate sensitive data.
Research
Security News
Attackers used a malicious npm package typosquatting a popular ESLint plugin to steal sensitive data, execute commands, and exploit developer systems.
Security News
The Ultralytics' PyPI Package was compromised four times in one weekend through GitHub Actions cache poisoning and failure to rotate previously compromised API tokens.