cmd: clean up generate stdout/stderr

[egtann]

cmd: clean up generate stdout/stderr

[a-h]

Good points. I'd be up for a redesign of the templ output.

I like to see the feedback that "stuff is happening", especially in watch mode, but it is a little noisy. It outputs so much that it obscures any application logging output that's happening at the same time.

I'd really like to see something like a bubbletea style interface for interactive sessions (https://github.com/charmbracelet/bubbletea) where you can see a short summary of whether templ is working, and maybe show/hide your own application logging too. In the interactive mode, it would probably show something like the last time it ran (5 seconds ago etc.), how long each run is estimated to take, when the app was last restarted, a progress bar if it's running a generate, a tail of the underlying app logs, and maybe the last few HTTP request/response operations from the proxy.

Along with that (as the default), a --plain flag would be useful (probably more your style?), where there's minimal output with no bubbletea style interface.

So, support two modes, interactive, and a plain version for CI/CD and integration into other workflows.

[a-h]

I've introduced a new structured logger, with a custom colourised handler in #470 while I was rewriting everything.

I thought that a fancy TUI was overkill once the output was tidied up. By default, it logs at Info level, so the default output is much simpler, just providing a summary.

$ templ generate
(✓) Complete [ updates=54 duration=87.295806ms ]

It's now under a verbose flag. You can set -v for debug mode, or set the level to "warn", "error" etc.. with the -log-level flag if you want no output at all unless there's errors.

However, I've kept the logs on stdout, since go's slog handler only has the choice of one and the logs are the program output.

[a-h]

Update on this one. Decided to log to stderr, since it affects Bazel and other users to log to stdout.

#753