mirror of
https://github.com/denoland/deno.git
synced 2024-11-26 16:09:27 -05:00
08813ea25e
<!-- Before submitting a PR, please read https://deno.com/manual/contributing 1. Give the PR a descriptive title. Examples of good title: - fix(std/http): Fix race condition in server - docs(console): Update docstrings - feat(doc): Handle nested reexports Examples of bad title: - fix #7123 - update docs - fix bugs 2. Ensure there is a related issue and it is referenced in the PR text. 3. Ensure there are tests that cover the changes. 4. Ensure `cargo test` passes. 5. Ensure `./tools/format.js` passes without changing files. 6. Ensure `./tools/lint.js` passes. 7. Open as a draft PR if your work is still in progress. The CI won't run all steps, but you can add '[ci]' to a commit message to force it to. 8. If you would like to run the benchmarks on the CI, add the 'ci-bench' label. --> Internally, `node-tap` spawns a child process with `stdio: [0, 1, 2]`. Whilst we don't support passing fd numbers as an argument so far, it turns out that `[0, 1, 2]` is equivalent to `"inherit"` which we already support. See: https://nodejs.org/api/child_process.html#optionsstdio Mapping it to `"inherit"` is fine for us and gets us one step closer in getting `node-tap` working. I'm now at the stage where already the coverage table is shown 🎉 |
||
|---|---|---|
| .. | ||
| node_modules/foo | ||
| add_global_property.js | ||
| add_global_property_run_main.js | ||
| binary_stdio.js | ||
| child_process_stdio.js | ||
| child_process_stdio_012.js | ||
| child_process_unref.js | ||
| exec_file_text_error.js | ||
| exec_file_text_output.js | ||
| infinite_loop.js | ||
| process_exit.ts | ||
| process_exit2.ts | ||
| process_really_exit.ts | ||
| process_stdin.ts | ||
| process_stdin_dummy.txt | ||
| rsa_private.pem | ||
| rsa_public.pem | ||
| worker_threads.mjs | ||