Typst Packages
An experimental package repository for Typst. A searchable list of all packages that were submitted here is available in the official documentation.
Package format
A package is a collection of Typst files and assets that can be imported as a unit. A typst.toml manifest with metadata is required at the root of a package. An example manifest could look like this:
[package]
name = "example"
version = "0.1.0"
entrypoint = "lib.typ"
authors = ["The Typst Project Developers"]
license = "Unlicense"
description = "An example package."
Required by the compiler:
name: The package's identifier in its namespace.version: The package's version as a full major-minor-patch triple. Package versioning should follow SemVer.entrypoint: The path to the main Typst file that is evaluated when the package is imported.
Required for submissions to this repository:
authors: A list of the package's authors.license: The package's license. Must contain a valid SPDX-2 expression describing one or multiple OSI-approved licenses.description: A short description of the package.
Optional:
repository: A link to the repository where this package is developed.
Packages always live in folders named as {name}-{version}. The name and version in the folder name and manifest must match. Paths in a package are local to that package. Absolute paths start in the package root while relative paths are relative to the file they are used in.
Published packages
This repository contains a collection of published packages. Due to its early and experimental nature, all packages in this repository are scoped in a preview namespace. A package that is stored in packages/preview/{name}-{version} in this repository will become availabe in Typst as #import "@preview/{name}:{version}". You must always specify the full package version.
Submission guidelines
To submit a package, simply make a pull request with the package to this repository. There are a few requirements for getting a package published, which are detailed below:
- Naming: Names should not include the word "typst" (as it is redundant). They should also not be merely descriptive to create level grounds for everybody (e.g. not just
slides). - Functionality: Packages should conceivably be useful to other users and should expose their capabilities in a reasonable fashion.
- Documentation: Packages must contain a
README.mdfile documenting (at least briefly) what the package does and all definitions intended for usage by downstream users. - License: Packages must be licensed under the terms of an OSI-approved license. In addition to specifying the license in the TOML manifest, a package must either contain a
LICENSEfile or link to one in itsREADME.md. - Size: Packages should not contain large files or a large number of files. This will be judged on a case-by-case basis, but if it needs more than ten files, it should be well-motivated.
- Security: Packages must not attempt to exploit the compiler or packaging implementation, in particular not to exfiltrate user data.
- Safety: Names and package contents must be safe for work.
This list may be extended over time as improvements/issues to the process are discovered. Given a good reason, we reserve the right to reject any package submission.
Once submitted, a package will not be changed or removed without good reason to prevent breakage for downstream consumers. By submitting a package, you agree that it is here to stay. If you discover a bug or issue, you can of course submit a new version of your package.
Note: Please do not submit templates as packages just yet. We plan to build infrastructure around this so that they can show up in the web app's template gallery and be used to scaffold a project through the CLI. Stay tuned!
Downloads
The Typst compiler downloads packages from the preview namespace on-demand. Once used, they are cached in {cache-dir}/typst/packages/preview where {cache-dir} is
$XDG_CACHE_HOMEor~/.cacheon Linux~/Library/Cacheson macOS%LOCALAPPDATA%on Windows
Importing a cached package does not result in a network access.
Local packages
Want to install a package locally on your system without publishing it or experiment with it before publishing? You can store packages in {data-dir}/typst/packages/{namespace}/{name}-{version} to make them available locally on your system. Here, {data-dir} is
$XDG_DATA_HOMEor~/.local/shareon Linux~/Library/Application Supporton macOS%APPDATA%on Windows
Packages in the data directory have precedence over ones in the cache directory. While you can create arbitrary namespaces with folders, a good namespace for system packages is local:
- Store a package in
~/.local/share/typst/packages/local/mypkg-1.0.0 - Import from it with
#import "@local/mypkg:1.0.0": *
Note that future iterations of Typst's package management may change/break this local setup.
License
The infrastructure around the package repository is licensed under the terms of the Apache-2.0 license. Packages in packages/ are licensed under their respective license.
9 Apr 18, 2023
4 Jun 7, 2023
18 Dec 16, 2023
58 Jan 1, 2024
3 Feb 15, 2024
12 Nov 16, 2022
5 Nov 2, 2021
1 Feb 4, 2022
10 Aug 25, 2022
169 Dec 30, 2022
130 Feb 5, 2023
3 May 9, 2023
18 Aug 7, 2023
3 Sep 9, 2023
8 Oct 27, 2023
6 Oct 28, 2023
294 Dec 23, 2022
91 Jul 4, 2023
414 Apr 17, 2023