#Workflow

4 messages · Page 1 of 1 (latest)

turbid halo
#

Hi all.

I try to maintain my template project when I find the time but I feel like I have not gotten a good grasp on a sustainable workflow. My template is built using the typst-package-template and I have mostly nailed down the PRs towards typst-packages. What I struggle with is when developing locally (using VS Code and Typst Tinymist), and having to switch package imports between the @local/package-name:X.X.X and @preview/package-name:X.X.X.

In both of these cases, the lib.typst code I am imported is not actually changed, just the contents of the files. The @preview obviously imports from the remote repo so no changes will be applied, but using @local is very confusing and results in me having to edit files elsewhere on my filesystem. I feel like I have this whole thing backwards.

Please help me understand how you are supposed to use these tools and templates

lilac vapor
#

You can use the just install-preview script to install into the preview namespace

#

If you haven't seen it already this will probably be useful: https://jamesrswift.github.io/blog/2024/07/09/packages.html (credit to @frank kraken)

turbid halo
#

Thank you for your help