From 054d8bfbdb80b8d1b25dba96f0c0fb847336e636 Mon Sep 17 00:00:00 2001 From: Alan Agius Date: Thu, 13 Jun 2024 06:39:52 +0000 Subject: [PATCH] docs: update developers guide with correct commands `--yarn` was replaced with `--package-manager=yarn` --- docs/DEVELOPER.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/DEVELOPER.md b/docs/DEVELOPER.md index 57a626892b..1bd5f389be 100644 --- a/docs/DEVELOPER.md +++ b/docs/DEVELOPER.md @@ -88,7 +88,7 @@ You can find more info about debugging [tests with Bazel in the docs.](https://g - For a complete list of test targets use the following Bazel query: `yarn bazel query "tests(//tests/...)"` - Run a subset of the tests: `yarn bazel test //tests/legacy-cli:e2e_node18 --config=e2e --test_filter="tests/i18n/ivy-localize-*"` - Use `bazel run` to debug failing tests debugging: `yarn bazel run //tests/legacy-cli:e2e_node18 --config=e2e --test_arg="--glob=tests/basic/aot.ts"` -- Provide additional `e2e_runner` options using `--test_arg`: `--test_arg="--yarn"` +- Provide additional `e2e_runner` options using `--test_arg`: `--test_arg="--package-manager=yarn"` When running the debug commands, Node will stop and wait for a debugger to attach. You can attach your IDE to the debugger to stop on breakpoints and step through the code. Also, see [IDE Specific Usage](#ide-specific-usage) for a