deno/cli/tests/testdata/run/auto_discover_lockfile/deno.lock

{
  "version": "2",
  "remote": {
    "http://localhost:4545/subdir/mod2.ts": "cae1d3e9f3c38cd415ff52dff854be8f3d17d35f8d7b3d285e813fb0f6393a2f",
    "http://localhost:4545/subdir/print_hello.ts": "foobar"
  }
}
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			`{`
			`"version": "2",`
			`"remote": {`
			`"http://localhost:4545/subdir/mod2.ts": "cae1d3e9f3c38cd415ff52dff854be8f3d17d35f8d7b3d285e813fb0f6393a2f",`
			`"http://localhost:4545/subdir/print_hello.ts": "foobar"`
			`}`
			`}`