clo/sitegen

long running dev server that can report the status of errors and builds #81

New issue

Open

opened 2026-02-04 04:19:43 -08:00 by clo · 0 comments

clo commented

2026-02-04 04:19:43 -08:00

Owner

low key should design this in a way it can fit into @clo/lib but not a requirement or it could be its own publication if wanted

i realize the problem with doing integrated tests and lints and so on is youll get alot of errors and they'll point at source code and you'll want to be able to show all of them and navigate it easily. im skeptical the TUI will be a great experience.

have sitegen run a server that runs on :3000 that proxies the real site, but adds a banner to show active errors, use a websocket to listen for new watches, and then send a clover progress stream with a full screen overlay when stuff is rebuilding. then if it fails you show all errors on screen. if lint errors you can like half dismiss it.

low key should design this in a way it can fit into @clo/lib but not a requirement or it could be its own publication if wanted i realize the problem with doing integrated tests and lints and so on is youll get alot of errors and they'll point at source code and you'll want to be able to show all of them and navigate it easily. im skeptical the TUI will be a great experience. have sitegen run a server that runs on :3000 that proxies the real site, but adds a banner to show active errors, use a websocket to listen for new watches, and then send a clover progress stream with a full screen overlay when stuff is rebuilding. then if it fails you show all errors on screen. if lint errors you can like half dismiss it.