Skip to content

Commit 302a4a7

Browse files
committed
docs(jest): explain TypeScript source mapping in print output
Document that print_pcs and print_funcs map back to TypeScript files when source maps are available and fall back to generated JavaScript locations when they are not.
1 parent 771914e commit 302a4a7

File tree

1 file changed

+6
-0
lines changed

1 file changed

+6
-0
lines changed

docs/jest-integration.md

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -145,6 +145,12 @@ enable source map generation in the TypeScript compiler options:
145145

146146
These settings should be enough to start writing Jest fuzz tests in TypeScript.
147147

148+
With source maps enabled, libFuzzer outputs such as `-print_pcs` and
149+
`-print_funcs` are also mapped back to original TypeScript files and line
150+
numbers whenever mappings are available. If a location cannot be mapped (for
151+
example, downlevel helper code), Jazzer.js falls back to the generated
152+
JavaScript location.
153+
148154
**Note**: Using custom hooks written in TypeScript is currently not supported,
149155
as those are not pre-processed by Jest.
150156

0 commit comments

Comments
 (0)