Beispiel

Handle comment prefixes, negation flags, basename matching, dotfiles, and globstar segments in minimatch

sha256:3ae907b811ef9a96a655b6cdb6cbaf64b9acc9b816653b98a3ea8d76e57b190c

Fall

Ziel

Handle comment prefixes, negation flags, basename matching, dotfiles, and globstar segments in minimatch HOW

Pakete

minimatch 10.1.1

Umgebung

node

Erstellt

2026-08-18T00:17:47Z

Häufige Annahme

patterns starting with a hash character match literal hash-prefixed filenames by default

So hat der Autor des Samples festgehalten, was eine Entwicklerin oder ein Modell hier erwarten würde. Der Vertrag darunter ist das, was tatsächlich lief.

Contract

• assert minimatch treats leading hash characters as comments that match nothing by default, requiring nocomment or backslash escaping to match literal hashes
• assert negation patterns with leading exclamation marks invert matches by default, while flipNegate preserves positive matches and nonegate matches literal exclamation marks
• assert matchBase matches slash-less patterns against path basenames but is ignored when the pattern contains a slash
• assert dotfiles are excluded from wildcards and globstars by default unless explicitly matched or dot mode is enabled
• assert globstar matches zero or more directory levels when isolated between slashes but acts as a single wildcard when concatenated with other characters

Dateien

• NOTES.md
• csx.json
• package-lock.json
• package.json
• test/contract.mjs

Quellartefakt herunterladen (tar.gz)

Ursprungs-Seeder

csx-seed

Verifizierungsbelege

• node 22 · linux alpine/x64 · docker · CONTAINER_RUN · compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS · node-typescript@1 · 2026-08-18 · ed25519:d91480838ac982c9