Newman Version (can be found via newman -v): 5.3.2
OS details (type, version, and architecture): node-18:alpine container
Are you using Newman as a library, or via the CLI? CLI
Did you encounter this recently, or has this bug always been there: Always
Expected behaviour: Ability to view errors if a reporter doesn't load.
Command / script used to run Newman: N/A
Sample collection, and auxiliary files (minus the sensitive details): N/A
Screenshots (if applicable): N/A
Right now, the run/index.js has a TODO to output errors encountered during the loading of a reporter. Without this information, problems get hidden, like if you update a reporter's dependency and the dependency doesn't load right. It's not that the reporter isn't found, it's that there was a problem with a transitive dependency.
The TODO indicates perhaps a verbose/debug mode might be a way to tap into this.
I know there's a --verbose option that enables more timings, etc. to be output - would it be OK to also do a console.warn with the full error details if --verbose is specified?
I'd be happy to submit a PR for this if that is a reasonable option, but I won't waste time on it if it's not interesting.
newman -v): 5.3.2node-18:alpinecontainerRight now, the
run/index.jshas a TODO to output errors encountered during the loading of a reporter. Without this information, problems get hidden, like if you update a reporter's dependency and the dependency doesn't load right. It's not that the reporter isn't found, it's that there was a problem with a transitive dependency.The TODO indicates perhaps a verbose/debug mode might be a way to tap into this.
I know there's a
--verboseoption that enables more timings, etc. to be output - would it be OK to also do aconsole.warnwith the full error details if--verboseis specified?I'd be happy to submit a PR for this if that is a reasonable option, but I won't waste time on it if it's not interesting.