When did hugo watcher become so verbose?

support
1

I am upgrading a project from version 0.123.0. I noticed the watcher has become so verbose. When did this happen and what was the reason behind it? I quite like the compact nature of the former.

$ hugo server
Watching for changes in /home/johndoe/hugo/quickstart/{archetypes,assets,content,data,i18n,layouts,static,themes}
Watching for config changes in /home/johndoe/hugo/quickstart/hugo.toml, /home/johndoe/hugo/quickstart/themes/t/hugo.toml
Start building sites … 
hugo v0.123.0-3c8a4713908e48e6523f058ca126710397aa4ed5+extended linux/amd64 BuildDate=2024-02-19T16:32:38Z VendorInfo=gohugoio

                   | EN  
-------------------+-----
  Pages            | 18  
  Paginator pages  |  0  
  Non-page files   |  1  
  Static files     |  1  
  Processed images |  0  
  Aliases          |  0  
  Cleaned          |  0  

Built in 30 ms
Environment: "development"
Serving pages from disk
Running in Fast Render Mode. For full rebuilds on change: hugo server --disableFastRender

$ hugo server
Watching for changes in /home/johndoe/hugo/quickstart/archetypes, /home/johndoe/hugo/quickstart/assets/{css,js}, /home/johndoe/hugo/quickstart/content/posts, /home/johndoe/hugo/quickstart/data, /home/johndoe/hugo/quickstart/i18n, /home/johndoe/hugo/quickstart/layouts/_partials, /home/johndoe/hugo/quickstart/static
Watching for config changes in /home/johndoe/hugo/quickstart/hugo.toml
Start building sites … 
hugo v0.163.0-4a9485336a3ff2cea07ab88e2a17ec34d5baaa6e linux/amd64 BuildDate=2026-06-08T14:13:03Z VendorInfo=gohugoio


                  │ EN 
──────────────────┼────
 Pages            │ 18 
 Paginator pages  │  0 
 Non-page files   │  1 
 Static files     │  1 
 Processed images │  0 
 Aliases          │  0 
 Cleaned          │  0 

Built in 48 ms
Environment: "development"
Serving pages from disk
Running in Fast Render Mode. For full rebuilds on change: hugo server --disableFastRender
Web Server is available at http://localhost:1313/ (bind address 127.0.0.1) 
Press Ctrl+C to stop

My ideal suggestion

Watching for changes in /home/johndoe/hugo/quickstart/{archetypes,assets{css,js},content,data,i18n,layouts,static,themes}
Watching for config changes in /home/johndoe/hugo/quickstart{hugo.toml, /themes/t/hugo.toml}
Start building sites …
2

So, I liked the old output better, too; the reasoning can be read in Fix slow server startup of very big content trees · gohugoio/hugo@7a43b92 · GitHub

So, there’s surely must be a way to get the old output without serving the performance penalty, but the fix above was what I had time for. Spending minutes extra to to start the server to get pretty output was obviously not worth it.