The CLI allows users to reference ALCE-formatted files: essentially a more flexible form of JSON that allows comments. There are a few downsides to using this format: 1. it is not a widely-known or -used format 2. as such the alce library hasn't been touched in 5 years (e.g. to run tests on newer versions of node) and 3. it requires some pretty heavy dependencies such as esprima.
I see three paths forward:
Move to the json5 format which is actively supported and has the same purpose as ALCE.
Only support JSON files.
Instead require() the config file to support JSON or a module export. In this case we could support export of a confidence store in addition to a plain object.
My recommendation would be the last option, since it's both flexible and simple. It would also be compatible with the boilerplate's server/manifest.js export, which is a confidence store. To my knowledge the confidence CLI isn't currently used especially often, so I think going with something simple might be a good choice!
The CLI allows users to reference ALCE-formatted files: essentially a more flexible form of JSON that allows comments. There are a few downsides to using this format: 1. it is not a widely-known or -used format 2. as such the
alcelibrary hasn't been touched in 5 years (e.g. to run tests on newer versions of node) and 3. it requires some pretty heavy dependencies such as esprima.I see three paths forward:
require()the config file to support JSON or a module export. In this case we could support export of a confidence store in addition to a plain object.My recommendation would be the last option, since it's both flexible and simple. It would also be compatible with the boilerplate's
server/manifest.jsexport, which is a confidence store. To my knowledge the confidence CLI isn't currently used especially often, so I think going with something simple might be a good choice!