Better handling of the module.workspace config

[UtkarshVerma]

The current state of workspaces in Hugo is:

• module.workspace needs an absolute path
• With workspace, Hugo was able to resolve nested modules in a private Hugo theme (added as a module). A good alternative to Module replacements not able to resolve nested modules #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.

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.