Permissions

Deno has a permission system that allows configuring the access to different APIs like environment variables, filesystem reads or writes, net access, etc. See the Deno's permissions manual for more info.

Lume is executed by default with the -A flag (or --allow-all), allowing all permissions. The Lume task generated in the deno.json file uses the following script to run Lume:

{
  "importMap": "import_map.json",
  "tasks": {
    "lume": "echo \"import 'lume/cli.ts'\" | deno run --unstable -A -",
    "build": "deno task lume",
    "serve": "deno task lume -s"
  }
}

This scripts echoes the import 'lume/cli.ts' code and then executes it. This allows resolving the lume/cli.ts module with the import map, so it's possible to update Lume just by editing the import_map.json file.

If you are concerned about the permissions granted to Lume and want to customize them, it's possible by replacing -A flag with your desired permission flags in the lume task. For example:

This is an example of a Lume task with some permissions configured:

{
  "importMap": "import_map.json",
  "tasks": {
    "lume": "echo \"import 'lume/cli.ts'\" | deno run --unstable --allow-net --allow-read=./ --allow-write=./_site -",
    "build": "deno task lume",
    "serve": "deno task lume -s"
  }
}

It seems this method has some issues with NPM modules, so for now, it only works in Lume v1.11.x