1
0
Fork 0
mirror of https://github.com/denoland/deno.git synced 2024-12-27 17:49:08 -05:00
denoland-deno/tests/specs/install/future_install_local_deno
Nathan Whitaker 5de30c5323
fix(cli): Support deno.lock with only package.json present + fix DENO_FUTURE install interactions with lockfile (#23918)
Fixes #23571.

Previously, we required a `deno.json` to be present (or the `--lock`
flag) in order for us to resolve a `deno.lock` file. This meant that if
you were using deno in an npm-first project deno wouldn't use a
lockfile.

Additionally, while I was fixing that, I discovered there were a couple
bugs keeping the future `install` command from using a lockfile.

With this PR, `install` will actually resolve the lockfile (or create
one if not present), and update it if it's not up-to-date. This also
speeds up `deno install`, as we can use the lockfile to skip work during
npm resolution.
2024-05-23 12:31:05 -07:00
..
__test__.jsonc fix(cli): Support deno.lock with only package.json present + fix DENO_FUTURE install interactions with lockfile (#23918) 2024-05-23 12:31:05 -07:00
deno.json FUTURE: deno install changes (#23498) 2024-05-08 12:34:46 -07:00
deno.lock.out fix(cli): Support deno.lock with only package.json present + fix DENO_FUTURE install interactions with lockfile (#23918) 2024-05-23 12:31:05 -07:00
install.out perf(jsr): download metadata files as soon as possible and in parallel (#23836) 2024-05-16 00:58:57 +02:00
main.js FUTURE: deno install changes (#23498) 2024-05-08 12:34:46 -07:00