deno/tools
Bartek Iwańczuk 8579e93ae2 chore: use lock file for tooling scripts (#14253)
This commit adds lock file for maintenance scripts in "tools/"
directory. 

The lock file is stored in "tools/deno.lock.json".
2022-04-14 13:17:25 -04:00
..
bench chore: use local copy of std in tools/bench/ scripts (#14251) 2022-04-14 13:17:24 -04:00
release chore: use lock file for tooling scripts (#14253) 2022-04-14 13:17:25 -04:00
wpt disable flakes (#13962) 2022-03-15 11:19:59 -04:00
build_benchmark_jsons.js
cut_a_release.md chore: update release instructions based on 1.20.5 release (#14239) 2022-04-14 13:17:24 -04:00
deno.lock.json chore: use lock file for tooling scripts (#14253) 2022-04-14 13:17:25 -04:00
flamebench.js
format.js chore: use rustfmt cli via dprint for faster format (#13735) 2022-02-21 12:47:08 -05:00
lint.js
README.md
update_typescript.md docs: information about updating TypeScript version (#13810) 2022-03-03 13:08:01 +11:00
upload_wptfyi.js
util.js
wgpu_sync.js
wpt.ts

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

wgpu_sync.js

wgpu_sync.js streamlines updating deno_webgpu from gfx-rs/wgpu.

It essentially vendors the deno_webgpu tree with a few minor patches applied on top, somewhat similar to git subtree.

  1. Update COMMIT or V_WGPU in ./tools/wgpu_sync.js
  2. Run ./tools/wgpu_sync.js
  3. Double check changes, possibly patch
  4. Commit & send a PR with the updates