Customizable Pipes (especially for JS resources)

[AlanBreck]

Several topics that seem related:

Hugo integration with js.Build (ESBuild) and multiple output files

{{ resources.Get "script.js" | js.Build }} uses the ESBuild api as a single entry point and expects a single output file (to pass through additional pipes). ESBuild, though, sometimes creates multiple output files from a single entry point, e.g. code splitting, external source maps, and “import *.css” statements in javascript files. This leads to my question: how will/should Hugo handle multiple outputs from ESBuild in Hugo Pipes? Currently, Hugo already added external source maps as a develop…

Compile svelte file via js.Build

Currently with the esBuild support in Hugo 0.78.2, I was wondering can we use esBuild plugins system in Hugo which can compile svelte files into normal js files like shown here. Simply I want Hugo to handle svelte files using js.Build.

Is it possible to add plugins to ESBuild for JS in Hugo?

I’m trying to go for an all out Hugo modular theme, without NPM dependencies. Most of the NPM dependencies are done but I’m stuck with dependencies in which index.js imports SCSS styles like cookieconsent/index.js at dev · osano/cookieconsent · GitHub. I want Hugo to tell ESBuild to use the esbuild-plugin-sass plugin for this purpose, but I couldn’t find any mention in the Hugo docs. Would it be possible to do so, or is there some other way I can approach this?