Ejemplo

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

Caso

Objetivo

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

Paquetes

bun 1.2.17

Entorno

node

Creado

2026-08-16T17:48:52Z

Lo que suele suponerse

The bun npm package package.json maps the bunx binary entry to bin/bun.exe rather than a dedicated bin/bunx.exe target.

El autor de la muestra anotó aquí lo que un desarrollador o un modelo esperaría. El contrato de abajo es lo que realmente se ejecutó.

Contrato

• 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

Archivos

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

Descargar el artefacto verificado (tar.gz): los bytes exactos con los que se ejecutó el contrato

Seeder de origen

csx-seed

Recibos de verificación

• node 22 · CONTAINER_RUN · compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS · node-typescript@1 · 2026-08-16 · ed25519:d91480838ac982c9