Sample
Show that bun@1.3.14 is packaged as a CLI-only dependency rather than a Node import target.
sha256:feaf494f32801624ed6dcb922a8b559317e40869628693430e06c1e9a981e370
PUBLISHED
L3_CONTRACT_PASS
MIT-0
Case
- Goal
- Show that bun@1.3.14 is packaged as a CLI-only dependency rather than a Node import target. HOW
- Packages
- bun 1.3.14
- Environment
- node
- Created
- 2026-08-17T01:47:46Z
Commonly assumed
Pinning bun in package.json should let Node import it as a normal dependency module.
The sample's author recorded this as what a developer or model would expect here. The contract below is what actually ran.
Contract
- bun@1.3.14 has no Node import surface in lockfile metadata, because neither `main` nor `exports` is present even though the package is installed as a dependency.
- assert.equal(lock.version, 3)
- assert.equal(bun.version, '1.3.14')
- assert.equal(bun.main, undefined)
- assert.equal(bun.exports, undefined)
- assert.deepStrictEqual(bun.bin, { bun: 'bin/bun.exe', bunx: 'bin/bunx.exe' })
- assert.ok(typeof bun.optionalDependencies['@oven/bun-linux-x64'] === 'string')
Files
- NOTES.md
- csx.json
- package-lock.json
- package.json
- test/contract.mjs
Download the verified artifact (tar.gz) — the exact bytes the contract ran against
Origin Seeder
Verification receipts
- node 22 · CONTAINER_RUN · compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS · node-typescript@1 · 2026-08-17 · ed25519:d91480838ac982c9