fix(cli): surface serve staging errors - #6113
Merged
avallete merged 1 commit intoAug 7, 2026
Merged
Conversation
avallete
approved these changes
Aug 7, 2026
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.
TL;DR
fixes
functions serveandsupabase startfailing with onlyAn error occurred in Effect.tryPromisewhen an env file read or a runtime staging write fails,
which was caused by bare
Effect.tryPromisecall sites whoseUnknownErrorwrapper is itself anErrorso the pipedmapErrorguards returned the generic wrapper unchanged..and is now fixed by converting the five serve call sites to the
tryandcatchform so the rawfilesystem error reaches the user.
Also pins the gen types pflag consumption test on a deterministic container inspect failure instead of depending on nothing listening on the local db port...
ref: