Anoduck, The Anonymous Duck

@chl33 Your comment lends credit to the hypothesis of the culprit causing the error is not Hugo itself, but rather the node.js package `hugo-bin`.

> > [@chl33](https://github.com/chl33) Your comment lends credit to the hypothesis of the culprit causing the error is not Hugo itself, but rather the node.js package `hugo-bin`. > > Hey [@anoduck](https://github.com/anoduck),...

Your site will build without `hugo-bin`, because `hugo-bin` is just a wrapper around the hugo binary, but npm specific commands that execute `hugo` will cease to work.

> What if I'm on Hugo version 147? Will this be fixed soon without downgrading hugo-bin? No. Take into consideration #1430. Downgrading your environment to a stable configuration is rather...

@eclecticpassions Since Hugo is distributed as a single file binary, you could always just download release 145 and rename it `hugo145` or `old-hugo` or `supercalifragilisticexpialidocious-hugo`. Then move it to where...

@theyamo I wouldn't hold your breath, as it appears he only patrons GitHub sparsely, like every 6 months or so. https://github.com/ruediger/weather-metno-el/issues/15

After upgrading from 10.4 to 11.0, and gutting the now defunct lsp-zero package, I have found myself receiving the same godforsaken error. I have attempted to rename the configuration file,...

I have never had to set up a CI before, so I am not sure how to go about doing that.

Building curl-impersonate generates error: ```bash checking for ZSTD_decompress in -lzstd... no configure: error: failed to find zstd ``` Although, zstd is installed, and the configuration script is set to the...

Just to reiterate everything already stated for sheer redundancy. Most modern distros have dropped support for OCAML4 by now, and now only provide OCAML5, which will fail to compile MLDonkey....