/usr/lib/node_modules/pnpm/dist/node_modules/minimatch/dist/commonjs
NameSizeModeActions
assert-valid-pattern.d.ts.map1990644editdlrm
assert-valid-pattern.js4920644editdlrm
assert-valid-pattern.js.map8020644editdlrm
ast.d.ts.map8680644editdlrm
ast.js228220644editdlrm
ast.js.map400210644editdlrm
brace-expressions.d.ts.map3040644editdlrm
brace-expressions.js57630644editdlrm
brace-expressions.js.map103710644editdlrm
escape.d.ts.map2440644editdlrm
escape.js9680644editdlrm
escape.js.map13780644editdlrm
index.d.ts.map31940644editdlrm
index.js405570644editdlrm
index.js.map716310644editdlrm
package.json250644editdlrm
unescape.d.ts.map2540644editdlrm
unescape.js9730644editdlrm
unescape.js.map14030644editdlrm
Edit: /usr/lib/node_modules/pnpm/dist/node_modules/minimatch/dist/commonjs/escape.js (968B)
"use strict"; Object.defineProperty(exports, "__esModule", { value: true }); exports.escape = void 0; /** * 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. */ 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, '\\$&'); }; exports.escape = escape; //# sourceMappingURL=escape.js.map