#DX experience

3 messages · Page 1 of 1 (latest)

gray sun
#

This isnt deluxe - just restrictive

molten zealot
tulip drum
#

it would make more sense if deno.json would allow / deny permissions explicitly and then deno run would read that file. thus, it's more customizable than editing a shell script. but hey, there's already support for this:

{
  "tasks": {
    "start": "deno run -A --watch=static/,routes/,data/ dev.ts"
  }
}

here's the manual reference: https://deno.land/[email protected]/getting_started/configuration_file#tasks

so, there's no point imo to have an explicit list of permissions

Deno

Deno supports a configuration file that allows you to customize the built-in
TypeScript compiler, formatter, and linter.