Skip to content

Feature Request - Improved logging of lifecycle scripts #882

Open
@rr-justin-hanselman

Description

@rr-justin-hanselman

Hey all!

First off, I really love standard-version. It makes versioning pretty and the lifecycle scripts is a great draw for my personal projects.

With that out of the way, I ran into a rather frustrating debugging issue with lifecycle scripts.

It seems that the runExec function that runs all scripts will not actually run any lifecycle scripts is dryRun is included in the args. My main need to run a dry-run is when I'm trying to test out a lifecycle script and verify that it worked. I actually spent half-an-hour trying to debug why the script itself might not be running.

So my request, or question is two-fold:

  1. Can we have either make dry-run not include lifecycle scripts or can we add a flag like --dry-run-with-lifecycle? Let me know if that goes against the spirit of the tool.

  2. It would be great to have stdout piped out from the runExec process for scripting. Especially if a complex script is doing several things that wouldn't be obvious to a new developer on the project. Is there a reason for only stdErr going out? Could we have a log-level flag that would trigger this?

Thanks for any insights!

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions