Use Hugo Modules

Prerequisite  

Initialize a New Module  

Use hugo mod init to initialize a new Hugo Module. If it fails to guess the module path, you must provide it as an argument, e.g.:

hugo mod init github.com/gohugoio/myShortcodes

Also see the CLI Doc .

Use a Module for a Theme  

The easiest way to use a Module for a theme is to import it in the config.

1. Initialize the hugo module system: hugo mod init github.com/<your_user>/<your_project>
2. Import the theme in your config.toml:

[module]
  [[module.imports]]
    path = "github.com/spf13/hyde"

Update Modules  

Modules will be downloaded and added when you add them as imports to your configuration, see Module Imports .

To update or manage versions, you can use hugo mod get.

Some examples:

Update All Modules  

hugo mod get -u

Update All Modules Recursively  

hugo mod get -u ./...

Update One Module  

hugo mod get -u github.com/gohugoio/myShortcodes

Get a Specific Version  

hugo mod get github.com/gohugoio/myShortcodes@v1.0.7

Also see the CLI Doc .

Make and test changes in a module  

One way to do local development of a module imported in a project is to add a replace directive to a local directory with the source in go.mod:

replace github.com/bep/hugotestmods/mypartials => /Users/bep/hugotestmods/mypartials

If you have the hugo server running, the configuration will be reloaded and /Users/bep/hugotestmods/mypartials put on the watch list.

Note that since v.0.77.0 you can use modules config replacements option. New in v0.77.0

Print Dependency Graph  

Use hugo mod graph from the relevant module directory and it will print the dependency graph, including vendoring, module replacement or disabled status.

E.g.:

hugo mod graph

github.com/bep/my-modular-site github.com/bep/hugotestmods/mymounts@v1.2.0
github.com/bep/my-modular-site github.com/bep/hugotestmods/mypartials@v1.0.7
github.com/bep/hugotestmods/mypartials@v1.0.7 github.com/bep/hugotestmods/myassets@v1.0.4
github.com/bep/hugotestmods/mypartials@v1.0.7 github.com/bep/hugotestmods/myv2@v1.0.0
DISABLED github.com/bep/my-modular-site github.com/spf13/hyde@v0.0.0-20190427180251-e36f5799b396
github.com/bep/my-modular-site github.com/bep/hugo-fresh@v1.0.1
github.com/bep/my-modular-site in-themesdir

Also see the CLI Doc .

Vendor Your Modules  

hugo mod vendor will write all the module dependencies to a _vendor folder, which will then be used for all subsequent builds.

Note that:

• You can run hugo mod vendor on any level in the module tree.
• Vendoring will not store modules stored in your themes folder.
• Most commands accept a --ignoreVendorPaths flag, which will then not use the vendored modules in _vendor for the module paths matching the Glob pattern given. Note that before Hugo 0.75 this flag was named --ignoreVendor and was a “all or nothing”. New in v0.75.0

Also see the CLI Doc .

Tidy go.mod, go.sum  

Run hugo mod tidy to remove unused entries in go.mod and go.sum.

Also see the CLI Doc .

Clean Module Cache  

Run hugo mod clean to delete the entire modules cache.

Note that you can also configure the modules cache with a maxAge, see File Caches .

Also see the CLI Doc .