denoland-deno/cli/tests/testdata/run/auto_discover_lockfile/main.out at ea0694bbfd6368d30cb8eaa3dd87f739eb60f8d2 - foster/denoland-deno - Foster's Laboratory

foster/denoland-deno

mirror of https://github.com/denoland/deno.git synced 2024-11-23 15:16:54 -05:00

Bartek Iwańczuk 5dea510b02

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.

2022-11-02 16:32:30 +01:00

5 lines

313 B

Text

Raw Blame History

 Download http://localhost:4545/subdir/mod2.ts
 Download http://localhost:4545/subdir/print_hello.ts
 error: The source code is invalid, as it does not match the expected hash in the lock file.
   Specifier: http://localhost:4545/subdir/print_hello.ts
   Lock file: [WILDCARD]auto_discover_lockfile[WILDCARD]deno.lock