CodeSampleX

Sample

determine coverage instrumentation with shouldInstrument and handle syntax errors with handlePotentialSyntaxError

sha256:e8ff88bce8caa42c2f11837fee8128755076f4cc3a99870d59820ab610d873ff

This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. How many distinct signing keys filed a passing contract receipt. One is the author alone; more than one means somebody else built it too. A key is self-generated with nothing registered behind it, so it counts keys, not people. MIT-0

Execution evidence

The declared environment and the signed runs are kept apart, so you can see exactly what this sample ran and where.

Evidence basis
Signed contract pass
Verification receipts
1
Signing keys that built it
1
Declared environment node linux 24 · ubuntu · glibc 2.39 x64 node node npm

Verification-run environments

Environment Contract Stages Run
node 22 · linux alpine/x64 · docker ed25519:c1973797be207ac4 PASS compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS
CONTAINER_RUN · node-typescript@1node:22-alpine@sha256:c610fcdfb1d5…
2026-08-26

Case

HOW
Goal
determine coverage instrumentation with shouldInstrument and handle syntax errors with handlePotentialSyntaxError
Packages
Symbols
  • handlePotentialSyntaxError
  • shouldInstrument
Environment
node
Created
2026-08-26T06:42:10Z

Contract

  1. shouldInstrument is a callable function exported by @jest/transform
  2. shouldInstrument returns true for source files matching collectCoverageFrom patterns
  3. shouldInstrument returns false when collectCoverage option is disabled
  4. shouldInstrument returns false for ignored paths specified in coveragePathIgnorePatterns (e.g. node_modules)
  5. shouldInstrument returns false for test files matching testMatch or testRegex
  6. shouldInstrument returns true for test files when overridden by forceCoverageMatch
  7. shouldInstrument returns false for JSON files and files in __mocks__ directories
  8. handlePotentialSyntaxError is a callable function exported by @jest/transform
  9. handlePotentialSyntaxError returns non-SyntaxError instances unmodified without throwing
  10. handlePotentialSyntaxError throws enhanced SyntaxError containing code frame and Jest diagnostic explanation

Files

  • NOTES.md
  • PROMPT.md
  • csx.json
  • package-lock.json
  • package.json
  • spec.json
  • src/index.mjs
  • test/contract.mjs

Download the source artifact (tar.gz)

Origin Seeder

anonymous