Build failure during asset minification in Hugo Pipes

Answer the question first

Hugo does not provide a built‑in mechanism to skip minification for a single file when the minifier reports a syntax error. The minify function is a hard stop: if the underlying minifier (Terser for JS, cssnano for CSS, etc.) returns an error, Hugo logs it as a fatal error and aborts the entire build. Likewise, there is no configuration flag that turns these fatal errors into warnings.

Why the failure is fatal

• Pipeline design – The asset pipeline is executed during the "transform" phase, before any output is written. A broken resource would corrupt the expected output set.
• External minifiers – For JavaScript, Hugo calls the external terser binary. If terser fails, Hugo cannot recover because it has no fallback.
• Error propagation – The minify function returns a Go error; Hugo treats any non‑nil error as a build‑fatal condition.

Steps to diagnose and resolve the issue

1. Run with verbose logging

   hugo --verbose
   

   The error output will include the file path and the exact message from the minifier, e.g. terser: Unexpected token or cssnano: Invalid CSS.

2. Check Hugo and Go versions

   hugo version
   

   Ensure you are on Hugo ≥ 0.55 (the version that introduced the minify pipeline). Older releases silently ignore minify or fail unpredictably.

3. Verify external dependencies for JS

   node -v
   npm -v
   npm list terser || npm install terser
   

   Hugo looks for terser in the local node_modules/.bin directory. If it is missing, the build fails with “terser not found”.

4. Validate CSS syntax

   npx postcss --config
   

   Run your PostCSS configuration separately to confirm there are no syntax errors that would be caught by cssnano.

5. Temporarily disable minify for the problematic file

   Remove the | minify call from the template or wrap the resource in a conditional that excludes that file:

   {{ $src := resources.Get "js/bad.js" }}
   {{ if eq $src.Path "js/bad.js" }}
     {{ $src | safeJS }}
   {{ else }}
     {{ $src | minify | safeJS }}
   {{ end }}
   

   While this is a manual workaround, it allows the rest of the site to build.

6. Global disable (if you prefer to avoid the issue altogether)

   Add to config.toml:

   [minify]
     disable = true
   

   Note that this turns off minification for all assets.

What you should provide for further help

• The exact error message printed by Hugo when the build fails.
• The snippet of template code where | minify is applied.
• Hugo version (output of hugo version).

With that information, the next step would be to pinpoint whether the syntax error is in the asset itself or in a PostCSS/SCSS configuration that corrupts the output.

Bottom line

Hugo does not support graceful skipping of a single minification error or logging it as a warning. The recommended approach is to either fix the offending asset, exclude it from minification, or disable minify globally until the issue is resolved.