You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
You can import packages in typst using the import syntax:
#import"@preview/cetz:0.3.1"#cetz.canvas({
import cetz.draw: *// Your drawing code goes here
})
The goal is to enable developers to do so without spamming the Typst server on app releases.
The Problem
At the moment, doing so will trigger a warning/error from Velyst as we actively block downloading packages from the server in favor of local packages. This is done to prevent Typst's server spam if the game happens to get a ton of downloads.
However, this is limiting because dependency tracking is needed for packages that depends on other packages...
Proposed Solution
We request downloads from Typst only during development phase. This means that whatever package imports we have, must be pre-downloaded during development phase and embedded into the project folder.
Nice to have
A simple tutorial on explaining the workflow as well as how packaging works when it comes to release phase.
The text was updated successfully, but these errors were encountered:
Goal
You can import packages in typst using the
import
syntax:The goal is to enable developers to do so without spamming the Typst server on app releases.
The Problem
At the moment, doing so will trigger a warning/error from Velyst as we actively block downloading packages from the server in favor of local packages. This is done to prevent Typst's server spam if the game happens to get a ton of downloads.
However, this is limiting because dependency tracking is needed for packages that depends on other packages...
Proposed Solution
We request downloads from Typst only during development phase. This means that whatever package imports we have, must be pre-downloaded during development phase and embedded into the project folder.
Nice to have
A simple tutorial on explaining the workflow as well as how packaging works when it comes to release phase.
The text was updated successfully, but these errors were encountered: