denoland-deno/tests/specs/lockfile/only_package_json/__test__.jsonc at 04ff5c731d55f2402e7b08e378eaf6e5a5a4d961 - foster/denoland-deno - Foster's Laboratory

foster/denoland-deno

mirror of https://github.com/denoland/deno.git synced 2024-11-30 16:40:57 -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

16 lines

265 B

Text

Raw Blame History

 {
   "tempDir": true,
   "steps": [
     {
       "args": "cache index.js",
       "output": "cache.out"
     },
     {
       "args": [
         "eval",
         "console.log(Deno.readTextFileSync('./deno.lock').trim())"
       ],
       "output": "deno.lock.out"
     }
   ]
 }