Add Javascript Support

Instead of JSON and YAML, I’d prefer to use a JavaScript module. For example, instead of this JSON:

{
  "scripts": {
    "start": "deno run --allow-net server.ts",
    "test": "deno test --allow-net server_test.ts"
  }
}

or this YAML:

# scripts.yaml
scripts:
  start: deno run --allow-net server.ts
  test: deno test --allow-net server_test.ts

I prefer this:

let options = {};
options.scripts = {};
options.scripts.start = "deno run --allow-net server.ts";
options.scripts.test = "deno test --allow-net server_test.ts";
export options;

Granted, my preference is more verbose. However, nothing is more flexible. You could do anything you wanted (programmatically) within this file and Velociraptor should only care about the object that gets exported at the end.

[umbopepato]

This will allow me to accomplish the configuration in a .js file correct?

@Lonniebiz no, we’re supporting only .ts for the reasons discussed above but you can still write JS in TS files since they’re sub/supersets of one another. Also, when this is implemented you will get code assistante for the configuration object without needing to manually add types.

[littledivy]

these config files are effectively Deno scripts and therefore could need some permissions that vr may not have. This essentially would require all permissions to be granted to vr at install time. Probably not a big deal (also the install command would be much shorter), but I was trying to avoid it if possible…

That is true and inevitable. To avoid perm errors the install command must give all perms (which seems fair).

.js configuration files are commonly used, but since Deno’s main language is TS wouldn’t it be more appropriate to use .ts files? (or at most both of them?)

Yup. I’ve just added that to the PR.

Every time .ts config files are compiled you would get a bunch of Deno logs which interfere with the output of launched scripts (don’t know if it’s possible to add the -q flag to an installed script though).

Maybe it is better to let the user know that the config scripts are compiled at runtime so they should expect compile logs from Deno. Though it won’t actually interrupt other logs as it is the compiled before any of the configs is processed.

Overall, I think this would be a good feature to introduce as it provides a more dynamic way to make config files.