-
-
Notifications
You must be signed in to change notification settings - Fork 7.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add hugo.Deps #8949
Comments
Do we need a lookup method? Can't |
Closed
Merged
bep
added a commit
to bep/hugo
that referenced
this issue
Jan 11, 2022
bep
added a commit
to bep/hugo
that referenced
this issue
Jan 11, 2022
bep
added a commit
to bep/hugo
that referenced
this issue
Jan 11, 2022
bep
added a commit
that referenced
this issue
Jan 11, 2022
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. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
There are situations where it would be useful to have the Hugo Module dependency information available in the templates (mostly, for JS libraries built from /assets, to know: What version of this library is currently running?).
So I propose we add
hugo.Deps
that lists the dependencies with some basic info:github.com/bep/mylib
)v1.0.0
)And then a lookup method so you can do$mylib := hugo.Deps.ByPath "foo"
The text was updated successfully, but these errors were encountered: