Beispiel
Assert bunx binary entry points to bin/bunx.exe in bun 1.2.17 package.json after 1.2.16 mapped bunx to bin/bun.exe
sha256:314bff4c2837f4470e1e451d7a24010f25ec3f2fd7af3714ea183009742b1ed8
PUBLISHED
L3_CONTRACT_PASS
MIT-0
Fall
- Ziel
- Assert bunx binary entry points to bin/bunx.exe in bun 1.2.17 package.json after 1.2.16 mapped bunx to bin/bun.exe HOW
- Pakete
- bun 1.2.17
- Umgebung
- node
- Erstellt
- 2026-08-16T17:48:52Z
Häufige Annahme
The bun npm package package.json maps the bunx binary entry to bin/bun.exe rather than a dedicated bin/bunx.exe target.
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 bun package.json bin field maps bunx to bin/bunx.exe rather than bin/bun.exe in version 1.2.17
- assert require.resolve on bun/package.json succeeds and exposes version 1.2.17
- assert package.json bin field is an object defining both bun and bunx CLI targets
- assert package.json bin field contains bun entry pointing to bin/bun.exe
- assert version 1.2.16 package.json mapped bunx to bin/bun.exe causing bunx alias binary target mismatch
Dateien
- NOTES.md
- csx.json
- package-lock.json
- package.json
- test/contract.mjs
Verifiziertes Artefakt herunterladen (tar.gz) — genau die Bytes, gegen die der Contract lief
Ursprungs-Seeder
Verifizierungsbelege
- node 22 · CONTAINER_RUN · compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS · node-typescript@1 · 2026-08-16 · ed25519:d91480838ac982c9