Glob文件匹配 - 编程技术参考——模具行业从业者必备知识手册

system 2

Match files using the patterns the shell uses, like stars and stuff.

This is a glob implementation in JavaScript. It uses the <code>minimatch</code>
library to do its matching.

!<a href="logo/glob.png">a fun cartoon logo made of glob characters</a>

<h3>Usage</h3>

Install with npm

<pre><code>
var glob = require("glob")

// options is optional
glob("/*.js", options, function (er, files) {
// files is an array of filenames.
// If the nonull option is set, and nothing
// was found, then files is ["/*.js"]
// er is an error object or null.
})
</code></pre>

<h3>Glob Primer</h3>

"Globs" are the patterns you type when you do stuff like <code>ls .js</code> on
the command line, or put <code>build/</code> in a <code>.gitignore</code> file.

Before parsing the path part patterns, braced sections are expanded
into a set. Braced sections start with <code>{</code> and end with <code>}</code>, with any
number of comma-delimited sections within. Braced sections may contain
slash characters, so <code>a{/b/c,bcd}</code> would expand into <code>a/b/c</code> and <code>abcd</code>.

The following characters have special magic meaning when used in a
path portion:

<ul>
<li><code></code> Matches 0 or more characters in a single path portion</li>
<li><code>?</code> Matches 1 character</li>
<li><code>[...]</code> Matches a range of characters, similar to a RegExp range.</li>
</ul>
 If the first character of the range is <code>!</code> or <code>^</code> then it matches
 any character not in the range.
<ul>
<li><code>!(pattern|pattern|pattern)</code> Matches anything that does not match</li>
</ul>
 any of the patterns provided.
<ul>
<li><code>?(pattern|pattern|pattern)</code> Matches zero or one occurrence of the</li>
</ul>
 patterns provided.
<ul>
<li><code>+(pattern|pattern|pattern)</code> Matches one or more occurrences of the</li>
</ul>
 patterns provided.
<ul>
<li><code>(a|b|c)</code> Matches zero or more occurrences of the patterns provided</li>
<li><code>@(pattern|pat*|pat?erN)</code> Matches exactly one of the patterns</li>
</ul>
 provided
<ul>
<li><code>**</code> If a "globstar" is alone in a path portion, then it matches</li>
</ul>
 zero or more directories and subdirectories searching for matches.
 It does not crawl symlinked directories.

If a file or directory path portion has a <code>.</code> as the first character,
then it will not match any glob pattern unless that pattern's
corresponding path part also has a <code>.</code> as its first character.

For example, the pattern <code>a/.*/c</code> would match the file at <code>a/.b/c</code>.
However the pattern <code>a//c</code> would not, because <code></code> does not start with
a dot character.

You can make glob treat dots as normal characters by setting
<code>dot:true</code> in the options.

<h4>Basename Matching</h4>

If you set <code>matchBase:true</code> in the options, and the pattern has no
slashes in it, then it will seek for any file anywhere in the tree
with a matching basename. For example, <code>*.js</code> would match
<code>test/simple/basic.js</code>.

<h4>Empty Sets</h4>

If no matching files are found, then an empty array is returned. This
differs from the shell, where the pattern itself is returned. For
example:

$ echo asdf
 asdf

To get the bash-style behavior, set the <code>nonull:true</code> in the options.

<ul>
<li><code>man sh</code></li>
<li><code>man bash</code> (Search for "Pattern Matching")</li>
<li><code>man 3 fnmatch</code></li>
<li><code>man 5 gitignore</code></li>
<li><a href="https://github.com/isaacs/minimatch">minimatch documentation</a></li>
</ul>

<h3>glob.hasMagic(pattern, [options])</h3>

Returns <code>true</code> if there are a

<hr>
踩过坑的来评论区说说。