denoland-deno/tests/specs/lockfile/only_package_json/deno.lock.out at 4e4c96bf66111c6e8ba976ed24594edf7abfcbfb - foster/denoland-deno - Foster's Laboratory

foster/denoland-deno

mirror of https://github.com/denoland/deno.git synced 2024-11-25 15:29:32 -05:00

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

19 lines

330 B

Text

Raw Blame History

 {
   "version": "3",
   "packages": {
     "specifiers": {
       "npm:@denotest/esm-basic": "npm:@denotest/esm-basic@1.0.0"
     },
     "npm": {
       "@denotest/esm-basic@1.0.0": [WILDCARD]
     }
   },
   "remote": {},
   "workspace": {
     "packageJson": {
       "dependencies": [
         "npm:@denotest/esm-basic"
       ]
     }
   }
 }