Supporting a deps.json wouldn’t be that hard.
Most people (?) are using a single deps/0 function now that just returns a list of tuples.
It’d be easy enough to parse a JSON file and return a list of ‘deps’ tuples. Your tool’s README could just document how users would modify their deps/0 function to included the parsed JSON output, e.g. something like:
defp deps do
[
# Fixed/static/hard-coded deps (if any) ...
]
++ function_or_something_with_parsed_deps_json_data()
end
Personally, I don’t like npm-style ‘add deps’ CLI commands – I much prefer maintaining deps ‘manually’ as-is the current convention.


















