Currently I am writing a GitHub action, that resolves the current packages tree that results from the meteor list --tree command and checks for outdated package versions.
However, this involves manually parsing the |-- symbols from the output to re-create the structure as a data model.
It would be much easier (and less error-prone) for this (and potential other actions / ci) to generate the packages tree directly as json file.
From what I perceive,there would be the following changes
Currently I am writing a GitHub action, that resolves the current packages tree that results from the
meteor list --tree
command and checks for outdated package versions. However, this involves manually parsing the|--
symbols from the output to re-create the structure as a data model.It would be much easier (and less error-prone) for this (and potential other actions / ci) to generate the packages tree directly as json file. From what I perceive,there would be the following changes
json
flag to the options--json
flag is active.--json
is omitted, keep the actual output symbols for--tree
--tree
is not active,--json
is irgnoredI would myself start a PR,if this would get a green light