Spread the word!
Thanks a lot bep!
I’ve noticed some minor display bug though.
Running Hugo 0.50 in Windows 10 shell it prints a control character sequence before and after the usual “Building sites” message.
Remnant from non windows builds maybe…
e[K25lBuilding sites … e[?25h
- traditional release - updated
- extended release - updated
Docker/CI Image - a Hugo Docker image for Continuous Integration - updated
Debian (sid) - not yet updated (Track link)
Ubuntu (cosmic) - not yet updated (Track link)
Fedora Copr - Hugo RPM packages for Fedora and CentOS - updated
Chocolatey traditional release - a Windows package manager - not yet updated
Chocolatey extended release - a Windows package manager - updated
Scoop - another Windows package manager - updated
Docker image updated.
Nah… I redid the logic with these Ansi escape codes and use a library to get some proper truth about you running in a proper terminal or not. But that is possibly not enough for the Windows case … Can you create a GitHub issue to remind me to fix it?
Yes, of course!
I didn’t have time to try it in dev but wow, this is great! Love the colors in the terminal and the super easy-to-read browser errors. Fantastic @bep, thanks!
Tnx for another great release of Hugo. Love the error messages in the browser, just testing the rest with an example project. Very fast, very reliable - just Hugo!
Just had a play and really love the new error reporting.
Nice work Bep and everyone else that contributed - thanks so much for everything you do!
Hugo is reaching a point where I’m not even sure what to wish for anymore
Brew me a nice brazilian coffee in the morning perhaps
You’re right. I started when Hugo was someting around v0.21 or so and the evolvement since then is outstanding.
Some say (seriously) that Hugo 0.18 still is the best.
I believe that’s called maturity (or product market fit for startups). Perhaps this means we’re not far off from v1.0 anymore.
This definitely is a great release. Very little in this release was needed, I feel like it was polish. That’s what’s crazy because typically polish doesn’t improve performance. I’m very excited for Hugo.
Chocolatey package is automatically updated at https://chocolatey.org/packages/hugo-extended (I maintain this package).
There is the standard Hugo package (https://chocolatey.org/packages/hugo) which is always behind releases (I don’t maintain this but have offered to help keep it up to date without success unfortunately). I just tend to install the extended package - it’s larger but still has the same functionality.
My suggestion would be to track the hugo-extended package - as it’s is automatically updated whenever a new release is made it will be available, at most, within 12 hours of the Github release (and generally a lot sooner!).
I’ve finally updated the copr repo. Sorry for the delay