fix(lock): autodiscovery of lockfile (#16498)

This commit adds autodiscovery of lockfile. 

This only happens if Deno discovers the configuration file (either 
"deno.json" or "deno.jsonc"). In such case Deno tries to load
"deno.lock"
file that sits next to the configuration file, or creates one for user
if
the lockfile doesn't exist yet.

As a consequence, "--lock" and "--lock-write" flags had been updated.
"--lock" no longer requires a value, if one is not provided, it defaults
to "./deno.lock" resolved from the current working directory.
"--lock-write"
description was updated to say that it forces to overwrite a lockfile.

Autodiscovery is currently not handled by the LSP.
This commit is contained in:
Bartek Iwańczuk 2022-11-02 16:32:30 +01:00 committed by GitHub
parent 630abb58b0
commit 5dea510b02
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
15 changed files with 283 additions and 60 deletions

View file

@ -2916,6 +2916,8 @@ impl Inner {
..Default::default()
},
self.maybe_config_file.clone(),
// TODO(#16510): add support for lockfile
None,
);
cli_options.set_import_map_specifier(self.maybe_import_map_uri.clone());