You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using releasePublish programmatically via import { releasePublish } from 'nx/release;, successful invocations will result in the method calling process.exit(0), while errors call process.exit(1). This makes this unsuitable for programmatic consumption, as it is not possible to try/catch errors, or perform additional tasks after successfully running.
E.g., the following code does not work (does not print the logged line):
To support programmatic consumption, the method releasePublish should throw errors or return results. A CLI wrapper could easily convert these into process.exit commands but allow programmatic consumers to perform their own error handling and clean up tasks.
Current Behavior
When using
releasePublish
programmatically viaimport { releasePublish } from 'nx/release;
, successful invocations will result in the method callingprocess.exit(0)
, while errors callprocess.exit(1)
. This makes this unsuitable for programmatic consumption, as it is not possible totry/catch
errors, or perform additional tasks after successfully running.E.g., the following code does not work (does not print the logged line):
Expected Behavior
To support programmatic consumption, the method
releasePublish
should throw errors or return results. A CLI wrapper could easily convert these intoprocess.exit
commands but allow programmatic consumers to perform their own error handling and clean up tasks.GitHub Repo
No response
Steps to Reproduce
Nx Report
Failure Logs
No response
Package Manager Version
No response
Operating System
Additional Information
No response
The text was updated successfully, but these errors were encountered: