It depends on your testing framework and build system. In most cases, enabling verbose logging (--verbose or -v flags) and configuring your CI/CD pipeline to capture build output can help. Are you using Jest, Mocha, or another testing framework
go build -v gives no output go test shows compile errors, but it doesn’t stop there, it executes all test which needlessly take time and results in potentially hunderds of lines about failed tests (which happens in the middle of development) which I don’t want to see. go test -v is even worse because it also shows information about passed tests.
I use go.testing from stdlib 1.24.1 for tests and stretchr/testify for assertions.
For now I’m concerned about local development, I shouldn’t commit a code which doesn’t even compile, right?