summaryrefslogtreecommitdiff
path: root/ext/node/polyfills
diff options
context:
space:
mode:
authorBartek IwaƄczuk <biwanczuk@gmail.com>2023-04-05 13:15:57 +0200
committerGitHub <noreply@github.com>2023-04-05 13:15:57 +0200
commitdb39855fcb9e90131432d1c03bd5c16263addb3e (patch)
tree09cd26c1c2fcee6ceb7a9872abca545a0110c651 /ext/node/polyfills
parent686fe477496cf6eee398eb8ac195692528d3f427 (diff)
tests: cleanup "node_compat_tests" (#18594)
A few drive-by cleanup while I'm working on the "crypto" module. It makes it easier and faster to debug the failing test case.
Diffstat (limited to 'ext/node/polyfills')
-rw-r--r--ext/node/polyfills/README.md19
1 files changed, 0 insertions, 19 deletions
diff --git a/ext/node/polyfills/README.md b/ext/node/polyfills/README.md
index ddad19dd6..11de64bd9 100644
--- a/ext/node/polyfills/README.md
+++ b/ext/node/polyfills/README.md
@@ -169,25 +169,6 @@ to pass certain tests. However, avoid doing such manual changes to the test
files, since that may cover up inconsistencies between the node library and
actual node behavior.
-### Working with child processes ? Use `DENO_NODE_COMPAT_URL`
-
-When working with `child_process` modules, you will have to run tests pulled
-from Node.js. These tests usually spawn deno child processes via the use of
-`process.execPath`. The `deno` executable will use its own embedded version of
-std modules, then you may get the impression your code is not really working as
-it should.
-
-To prevent this, set `DENO_NODE_COMPAT_URL` with the absolute path to your
-`deno_std` repo, ending with a trailing slash:
-
-```
-export DENO_NODE_COMPAT_URL=$PWD/
-# or
-export DENO_NODE_COMPAT_URL=file:///path/to/deno_std/dir/
-```
-
-Then, `deno` will use your local copy of `deno_std` instead of latest version.
-
### Best practices
When converting from promise-based to callback-based APIs, the most obvious way