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

My testing files do not reference std/0.165std/0.165 and my import-map.jsonimport-map.json is pinned to std/0.177std/0.177. When I use deno rundeno run everything works fine. When I use deno testdeno test for some reason std/0.165std/0.165 is added to my deno.lockdeno.lock file and then I get errors about core.runMicrotasks is not a functioncore.runMicrotasks is not a function.

How do I keep deno testdeno test from adding an older version of stdstd to the deno.lockdeno.lock file?

Deno•4y ago•

8 replies

texasranger

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?

Continue the conversation

Join the Discord to ask follow-up questions and connect with the community

Deno

Chat about Deno, a modern runtime for JavaScript and TypeScript.

20,934 Members

Join