From 44b2b950fd20e59fca1e6dddf522d456d2fd622f Mon Sep 17 00:00:00 2001 From: Roj Date: Thu, 8 Dec 2022 02:13:45 +0300 Subject: feat(cli): support configuring the lock file in the config file (#16781) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit This allows the user to completely opt out from the lock file or rename it without having to use `--no-lock` and/or `--lock` in all commands. ## Don’t Use Lock File ```json { "lock": false } ``` ## Use Lock File With a Different Name ```json { "lock": "deno2.lock" } ``` The CLI args `--no-lock` and `--lock` will always override what is in the config file. Co-authored-by: David Sherret --- cli/tests/testdata/run/config_file_lock_path.out | 3 +++ 1 file changed, 3 insertions(+) create mode 100644 cli/tests/testdata/run/config_file_lock_path.out (limited to 'cli/tests/testdata/run/config_file_lock_path.out') diff --git a/cli/tests/testdata/run/config_file_lock_path.out b/cli/tests/testdata/run/config_file_lock_path.out new file mode 100644 index 000000000..97d35337f --- /dev/null +++ b/cli/tests/testdata/run/config_file_lock_path.out @@ -0,0 +1,3 @@ +[WILDCARD]The source code is invalid, as it does not match the expected hash in the lock file. + Specifier: http://localhost:4545/subdir/mt_text_ecmascript.j3.js + Lock file: [WILDCARD]lock_check_err2.json -- cgit v1.2.3