Is there a way to manage package dependencies in a single place? Let’s say multiple Typst files in my project use Glossarium and import it with:
#import "@preview/glossarium:0.5.8"
How to I avoid repeating the version number 0.5.8 every time?
From what I found so far, it seems Typst does not provide any dedicated dependency management file or similar.
The approach I am currently using is having a separate package-imports.typ file which only defines the package imports, and then importing all packages from that file instead:
#import "/package-imports.typ": glossarium.gls
If that is currently the approach suggested by the community, are there any conventions for how to name this file? I noticed the typst-community/setup-typst action uses requirements.typ, but I am not sure if that is only intended to be used by the GitHub action or also by the project itself, and I don’t know either how widespread that file name convention is.
Or which approaches do you use to manage package dependencies in a single place?