typst / typst/packages

Automatically label packages as "working"/"not working" if their template builds using the latest version of Typst

Open
#3,126 4 comments 5 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Rust
Stars
1k
Forks
1.3k
Avg merge
2d 22h
Merged PRs (30d)
189

Description

Description

It's quite incredible how the Typst Universe is expanding on a daily basis.

As of today there are 3000 merged PRs in the typst/packages repo!

Image

A victim to its own success, since there are now so many packages on the Typst Universe. As a user it becomes more difficult to find good (and working) templates.

As one step in improving the situation, it would be useful to automatically label template packages as "working"/"not working", based on if the template compiles using the latest version of Typst.

There are several template packages that don't seem to compile using the latest version of Typst. For instance:

Image Image Image

There are also template packages that don't seem to compile due to missing resource files, e.g.

Image

And as such, when e.g. using the Typst.app webapp and creating a new project based on these templates, the user can be faced with an error which they cannot solve, since they don't have access/possibility to edit the template source code (at least not in an easy way).

So, to add a label where one can filter for packages that are known to compile successfully (with the latest version of the Typst compiler) would be great for Typst Universe users!

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue does not identify repository files, tests, or an existing entry point. Start by locating how packages are built and how package metadata or labels are represented, then trace how the listed template failures could be detected. Done means packages are automatically marked according to whether they compile with the latest Typst version, including missing-resource failures.

Written by the indexing model from the issue text.

Assessment

Domain
build-system, testing
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.