Why does `deno test` add an older version of the `std` library to my deno.lock?

texasranger · 2023-02-25T01:04:05.867Z

My testing files do not reference `std/0.165` and my `import-map.json` is pinned to `std/0.177`. When I use `deno run` everything works fine. When I use `deno test` for some reason `std/0.165` is added to my `deno.lock` file and then I get errors about `core.runMicrotasks is not a function`. How do I keep `deno test` from adding an older version of `std` to the `deno.lock` file?

My testing files do not reference

std/0.165

std/0.165

std/0.165

std/0.165 and my

import-map.json

import-map.json

import-map.json

import-map.json is pinned to

std/0.177

std/0.177

std/0.177

std/0.177. When I use

deno run

deno run

everything works fine. When I use

deno test

deno test

deno test

deno test for some reason

std/0.165

std/0.165

std/0.165

std/0.165 is added to my

deno.lock

deno.lock

file and then I get errors about

core.runMicrotasks is not a function

core.runMicrotasks is not a function

core.runMicrotasks is not a function

core.runMicrotasks is not a function.

How do I keep

deno test

deno test

deno test

deno test from adding an older version of

std

std

std

std to the

deno.lock

deno.lock

file?

Why does `deno test` add an older version of the `std` library to my deno.lock?

Similar Threads