How to add lock file in deno.json?

[DrSensor]

Hi, is there a way to specify the lock file so that all tasks (deno task) in deno.json will use that lock file automatically?

Or at least I can specify it in the command line explicitly for specific task.
For example: deno --lock=lock.json task build

my config

---

deno.json

{
  "importMap": "import_map.json",
  "tasks": {
    "lume": "deno eval \"import 'lume/task.ts'\" --",
    "build": "deno task lume",
    "serve": "deno task lume -s"
  },
  "compilerOptions": {
    "jsx": "react-jsx",
    "jsxImportSource": "preact",
    "types": [
      "./types.d.ts"
    ],
    "lib": [
      "dom",
      "dom.iterable",
      "dom.asynciterable",
      "deno.ns",
      "deno.unstable"
    ]
  }
}

---

import_map.json

{
  "imports": {
    "preact/jsx-runtime": "https://esm.sh/preact/jsx-runtime",
    "preact/jsx-dev-runtime": "https://esm.sh/preact/jsx-dev-runtime",
    "lume/": "https://deno.land/x/lume/"
  }
}

[zachauten]

The --lock flag is only available on commands that populate the cache. task isn't one of these. But if you want a task that uses one of the deno commands that does use the --lock flag, you should be able to:

"tasks": {
  "cache-with-lock": "deno cache --lock=lock.json deps.ts"
}

[zachauten]

No, deno eval doesn’t write to the cache either. It sounds like maybe you are just trying to vendor lume? Does installing it work for your use case? Or maybe deno vendor?

[DrSensor]

Installing it works but the update method is based on pinned version in the import_map.json. I think deno vendor works for me since it support vendoring from import-map. Can it vendor the whole path? I mean is it going to traverse all files and dirs in the prefix url? For example,

{
  "imports": {
    "plugins/": "https://esm.sh/lume/plugins/"
  }
}

will that download all https://esm.sh/lume/plugins/*.ts and https://esm.sh/lume/plugins/**/*.ts?

[DrSensor]

I think I will go with 1 file that only consist of this single line

/// lume.js
import "lume/task.ts"

then I can do deno run --lock=lock.json lume.js. Kinda ugly but at least it works on my favor.

[DrSensor]

Does deno cache and --lock-write also detect dynamic import?

[zachauten]

Does deno cache and --lock-write also detect dynamic import?

I'm not sure. Try running deno cache on a file with a dynamic import and check if it writes anything to the lockfile?