fix: suppress stdout log spam when daemon is already running#219
Merged
fix: suppress stdout log spam when daemon is already running#219
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
alreadyRunningflag toDaemonStartResult— set whenstartDaemon()detects the daemon is already runningindex.ts) now suppresses all output whenalreadyRunningis true, exiting silently with code 0KeepAlivere-invocationsTest plan
npx tsc --noEmit)node dist/index.js startwhen already running produces no output, exits 0node dist/index.js reloadstill works normallynpm run build)Closes #217