What user cases are there for `noMounts` in module config?

I was reading through the docs and stumbled upon the noMounts option for the Hugo Modules configuration… I can’t think of any use for that option. What can a Hugo Module provide without mounting any folders?

1 Like

Rummaging around in my weird brain for reasons to not mount anything, one reason for this could be some form of “configuration in a module” system. Because the config directory would not be something that has to be mounted. So I could put often used configuration (like for instance markup setup) into a module.

Any other usable case?

:thinking: :mag:

Configure Modules | Hugo > Release v0.84.2 · gohugoio/hugo · GitHub > Add module.import.noMounts config · Issue #8708 · gohugoio/hugo · GitHub

My use case for this is rather special case, but it may possibly be useful to others.

Hey @bep, what’s your rather special case? :slight_smile:

1 Like

I try to remember, but it does not click … I will think about, I know it was some … thing.

3 Likes

Just in case… there is a requirement for you to remember :wink: We need to know. I think the config module idea I had is quite good. But anything else will help.