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
..
deno_json.rs	refactor: move deno json functionality to args module (#22710)	2024-03-05 15:45:44 -05:00
flags.rs	feat(cli/test): deno test --clean (#23519)	2024-05-23 03:04:12 +00:00
flags_net.rs	chore: update copyright to 2024 (#21753)	2024-01-01 19:58:21 +00:00
import_map.rs	fix(workspace): provide workspace members as 'imports' in import map (#23492)	2024-04-23 17:21:06 +02:00
lockfile.rs	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
mod.rs	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
package_json.rs	feat(lockfile): track JSR and npm dependencies in config file (#22004)	2024-01-22 22:31:12 +01:00