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
We support "build on run" for commands implemented as Go source directories, but we get the output of the build compiler when its run. The build compiler should probably only output when there is a problem and leave the progress output behind a verbose flag. This would make "build on run" a more seamless experience.
The text was updated successfully, but these errors were encountered:
As of 214113a this is "technically" complete, though only because all build output gets ignored in proc.go. AFAICT this is blocked by #64 since we don't have a good way of using stdio from within the kernel. In the meantime we could workaround this by piping build's stdout/err to the browser console.
We support "build on run" for commands implemented as Go source directories, but we get the output of the
build
compiler when its run. Thebuild
compiler should probably only output when there is a problem and leave the progress output behind a verbose flag. This would make "build on run" a more seamless experience.The text was updated successfully, but these errors were encountered: