Beispiel

Evaluate custom usage statistics with browserslist popularity queries and coverage calculations

sha256:7e171def787155f4d02c9678ffc6da566dc6a24d7d76f837c207d0e4df2bdc03

Fall

Ziel

Evaluate custom usage statistics with browserslist popularity queries and coverage calculations HOW

Pakete

browserslist 4.28.8

Umgebung

node

Erstellt

2026-08-17T12:46:26Z

Häufige Annahme

passing custom usage statistics via opts.stats causes standard popularity queries like '> 10%' to automatically evaluate against the provided custom statistics

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

• browserslist('> 10%', { stats }) evaluates against global caniuse-lite usage data and ignores opts.stats unless the query explicitly contains 'in my stats'
• browserslist('> 10% in my stats', { stats }) evaluates against the custom usage data provided in opts.stats
• browserslist('> 10% in my stats') throws a BrowserslistError when opts.stats is omitted
• browserslist.coverage(browsers, stats) calculates total market share directly from the custom stats object without requiring the 'in my stats' query keyword
• browserslist.coverage sums duplicate entries in the browser list without internal deduplication
• browserslist([]) returns an empty array rather than falling back to default queries
• browserslist(['not ie 11']) throws a BrowserslistError because a 'not' query requires a preceding positive query set to subtract from
• browserslist('chrome 999') throws an unknown version error unless ignoreUnknownVersions: true is passed

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-17 · ed25519:d91480838ac982c9