The PACKAGE Package

A short description about the project and/or client.

Template adaptation checklist

• Fill out README.md
  • Change the PACKAGE package name, including code snippets
  • Check section contents and/or delete sections that don't apply
• Check and/or replace LICENSE by something that suits your needs
• Fill out typst.toml
  • See also the typst/packages README
• Adapt Repository URLs in CHANGELOG.md
  • Consider only committing that file with your first release, or removing the "Initial Release" part in the beginning
• Adapt or deactivate the release workflow in .github/workflows/release.yml

  • to deactivate it, delete that file or remove/comment out lines 2-4 (on: and following)

  • to use the workflow

    • check the values under env:, particularly REGISTRY_FORK
    • if you don't have one, create a fine-grained personal access token with only Contents permission for the REGISTRY_FORK
    • on this repo, create a secret REGISTRY_TOKEN (at https://github.com/[user]/[repo]/settings/secrets/actions) that contains the so created token

    if configured correctly, whenever you create a tag v..., your package will be pushed onto a branch on the REGISTRY_FORK, from which you can then create a pull request against typst/packages

• remove/replace the example test case
• (add your actual code, docs and tests)
• remove this section from the README

Getting Started

To add this package to your project, first download it using typship:

typship download https://codeberg.org/eraa/typst-PACKAGE -n eraa -c v0.1.0

Then you can use this:

#import"@eraa/PACKAGE:0.1.0":*...

Usage

See the manual for details.