deno/tools
2022-01-21 10:16:57 +01:00
..
bench tools(bench): rebootstrap (#12281) 2021-10-01 00:42:24 +02:00
release chore: update copyright year (#13434) 2022-01-20 16:10:16 +09:00
wpt chore: update copyright year (#13434) 2022-01-20 16:10:16 +09:00
build_benchmark_jsons.js chore: update copyright to 2022 (#13306) 2022-01-07 22:09:52 -05:00
cut_a_release.md chore: update cut_a_release.md (#13444) 2022-01-21 10:16:57 +01:00
flamebench.js chore: update copyright to 2022 (#13306) 2022-01-07 22:09:52 -05:00
format.js chore: update copyright to 2022 (#13306) 2022-01-07 22:09:52 -05:00
lint.js Add LSP benchmark mimicking the one on quick-lint-js (#13365) 2022-01-18 06:58:50 -05:00
README.md revert(#13402): experiment: wgpu sync (#13439) 2022-01-20 15:23:53 +01:00
upload_wptfyi.js chore(ci): update dependency for upload_wptfyi (#12587) 2021-10-29 16:29:37 +11:00
util.js chore: update copyright to 2022 (#13306) 2022-01-07 22:09:52 -05:00
wpt.ts chore: update copyright year (#13434) 2022-01-20 16:10:16 +09:00

Tools

Documentation for various tooling in support of Deno development.

format.js

This script will format the code (currently using dprint, rustfmt). It is a prerequisite to run this before code check in.

To run formatting:

deno run --allow-read --allow-write --allow-run --unstable ./tools/format.js

lint.js

This script will lint the code base (currently using dlint, clippy). It is a prerequisite to run this before code check in.

To run linting:

deno run --allow-read --allow-write --allow-run --unstable ./tools/lint.js

Tip: You can also use cargo to run the current or pending build of the deno executable

cargo run -- run --allow-read --allow-write --allow-run --unstable ./tools/<script>

flamebench.js

flamebench.js facilitates profiling and generating flamegraphs from benchmarks.

General usage:

 ./tools/flamebench.js
flamebench <bench_name> [bench_filter]

Available benches:
op_baseline
ser
de

To profile the op_baseline bench, run ./tools/flamebench.js op_baseline, this will run all 3 benches in `op_baseline.

Often when profiling/optimizing, you'll want to focus on a specific sub-bench, flamebench supports a bench/test filter arg like the regular cargo commands. So you can simply run ./tools/flamebench.js op_baseline bench_op_async or ./tools/flamebench.js op_baseline bench_op_nop to profile specific benches.

Tip: the [bench_filter] argument doesn't have to be an exact bench name, you can use a shorthand or a partial match to profile a group of benches, e.g: ./tools/flamebench.js de v8