opened 01:02PM - 19 Dec 22 UTC
NeedsTriage
Proposal
The current state of workspaces in Hugo is:
- `module.workspace` needs an absol…ute path
- With workspace, Hugo was able to resolve nested modules in a private Hugo theme (added as a module). A good alternative to https://github.com/gohugoio/hugo/issues/9494
- Hugo perfectly builds the site in workspaces, however, it doesn't watch the directories from `use` directive in `go.work` for changes. For example, my use case was to debug a theme I'm working on. Hugo would not detect and rebuild the site if I made changes to the theme.
My `go.work`:
```
go 1.19
use ../../themes/hugo-yami
```
It would be really great if Hugo looks for the `go.work` file relative to the project. Additionally, having Hugo parse the `go.work` file to look out for `use` directives would be awesome. It would allow site rebuilds if any of the modules in the workspace got updated.