/usr/lib/node_modules/pnpm/dist/node_modules/minimatch/dist/esm
NameSizeModeActions
assert-valid-pattern.d.ts.map1990644editdlrm
assert-valid-pattern.js3360644editdlrm
assert-valid-pattern.js.map7850644editdlrm
ast.d.ts.map8680644editdlrm
ast.js225880644editdlrm
ast.js.map400360644editdlrm
brace-expressions.d.ts.map3040644editdlrm
brace-expressions.js56310644editdlrm
brace-expressions.js.map103550644editdlrm
escape.d.ts.map2440644editdlrm
escape.js8480644editdlrm
escape.js.map13640644editdlrm
index.d.ts.map31940644editdlrm
index.js390980644editdlrm
index.js.map716570644editdlrm
package.json230644editdlrm
unescape.d.ts.map2540644editdlrm
unescape.js8470644editdlrm
unescape.js.map13890644editdlrm
Edit: /usr/lib/node_modules/pnpm/dist/node_modules/minimatch/dist/esm/escape.js (848B)
/** * Escape all magic characters in a glob pattern. * * If the {@link windowsPathsNoEscape | GlobOptions.windowsPathsNoEscape} * option is used, then characters are escaped by wrapping in `[]`, because * a magic character wrapped in a character class can only be satisfied by * that exact character. In this mode, `\` is _not_ escaped, because it is * not interpreted as a magic character, but instead as a path separator. */ export const escape = (s, { windowsPathsNoEscape = false, } = {}) => { // don't need to escape +@! because we escape the parens // that make those magic, and escaping ! as [!] isn't valid, // because [!]] is a valid glob class meaning not ']'. return windowsPathsNoEscape ? s.replace(/[?*()[\]]/g, '[$&]') : s.replace(/[?*()[\]\\]/g, '\\$&'); }; //# sourceMappingURL=escape.js.map