# Development Guide Tinymist provides a single integrated language service for Typst. The tinymist project is arranged as follows: **The Language Server** – The main component, [tinymist](./crates/tinymist/), starts as a thread or process, obeying the [Language Server Protocol](https://microsoft.github.io/language-server-protocol/). **The Analyzers** – The most critical features are lsp functions, built upon the [tinymist-query](../crates/tinymist-query/) crate. **The Editor Frontend** – Leveraging the interface of LSP, tinymist provides frontend to each editor, located in the [editor folder](../editors). **The builtin essential but optional features** – All rest features in tinymist are optional. The significant features are enabled by default, but you can disable them with feature flags. - The syntax highlighting feature powered by [textmate](../syntaxes/textmate/). - The document formatting feature powered by [typstfmt](https://github.com/astrale-sharp/typstfmt) or [typstyle](https://github.com/Enter-tainer/typstyle). - The document previewing feature powered by [`typst-preview`](../crates/typst-preview/). - The handwritten-stroke recognizer powered by [Detypify](https://detypify.quarticcat.com/). To get a full overview of the crates and structure of the project, you could take a look at [Overview of Service](https://myriad-dreamin.github.io/tinymist/overview.html). ## Installing Toolchain To contribute to tinymist, you need to install the following tools: - [Cargo](https://doc.rust-lang.org/cargo/) to develop Rust [crates](../crates/). - [Yarn](https://yarnpkg.com/) to develop [VS Code extension](../editors/vscode/) or [tools](../tools/). ## Configure the Development Environment You don't have to configure anything to start developing tinymist. However, here we provide some tips to make your development experience better. - [@Myriad-Dreamin's VS Code Settings](#appendix-myriad-dreamins-vs-code-settings) ## Building and Running To build tinymist LSP: ```bash git clone https://github.com/Myriad-Dreamin/tinymist.git # Debug cargo build # Release cargo build --release # RelWithDebInfo (GitHub Release) cargo build --profile=gh-release ``` To run VS Code extension locally, open the repository in VS Code and press `F5` to start a debug session to extension. The VS Code extension also shows how we build and run the language server and the editor tools. ## Local Documentation To serve the documentation locally, run: ```bash yarn docs ``` To generate and open crate documentation, run: ```bash yarn docs:rs --open ``` > [!Tip] > Please install [Shiroa](https://myriad-dreamin.github.io/shiroa/guide/installation.html) to build the docs with `yarn`. If you find missing or incomplete documentation, please feel free to open an issue or pull request. There is also a tracking issue to improve the documentation, see [Request for Documentation (RFD)](https://github.com/Myriad-Dreamin/tinymist/issues/931). ## Contribute to tinymist-assets or tools/typst-preview-frontend To build the frontend and copy the output to the `crates/tinymist-assets` folder, run: ```bash yarn build:preview ``` To bundle the locally built assets (instead of that from [crates.io](https://crates.io/crates/tinymist-assets)) into tinymist's CLI binary, make sure you build with the feature `typst-preview` enabled, and have uncommented the line in the root [`Cargo.toml`](../Cargo.toml): ```patch @@ -207,1 +207,1 @@ # This patch is used to bundle a locally built frontend (HTML) of `typst-preview`. -# tinymist-assets = { path = "./crates/tinymist-assets/" } +tinymist-assets = { path = "./crates/tinymist-assets/" } ``` ## Running Analyzer Tests This is required if you have changed any code in `crates/tinymist-query`. To run analyzer tests for tinymist: ```bash cargo insta test -p tinymist-query --accept ``` > [!Tip] > Check [Cargo Insta](https://insta.rs/docs/cli/) to learn and install the `insta` command. To add more tests, please refer to the guide to [test analyzers.](./dev-guide/tinymist-query.md#testing-analyzers) ## Running Syntax Grammar Tests This is required if you are going to change the textmate grammar in `syntaxes/textmate`. ```bash # in root yarn test:grammar # Or in syntaxes/textmate cd syntaxes/textmate && yarn test ``` ## Running E2E Tests This is required if you have changed any code in `crates/tinymist` or `crates/tinymist-query`. To run e2e tests for tinymist on Unix systems: ```bash ./scripts/e2e.sh ``` To run e2e tests for tinymist on Windows: ```bash ./scripts/e2e.ps1 ``` ## Release on GitHub The code owners and maintainers of the release channels can check the [Release Guide](/dev-guide/release-instruction.md) to learn how to check and release the new version of tinymist. ## APPENDIX: @Myriad-Dreamin's VS Code Settings Applies the workspace settings template: ``` cp .vscode/tinymist.code-workspace.tmpl.json .vscode/tinymist.code-workspace.json ``` And then open the workspace in VS Code. Rust Settings explained: This configuration enables clippy on save: ```json { "rust-analyzer.check.command": "clippy", } ``` This configuration wraps comments automatically: ```json { "rust-analyzer.rustfmt.extraArgs": ["--config=wrap_comments=true"], } ``` This configuration excludes the `target` folder from the file watcher: ```json { "files.watcherExclude": { "**/target": true }, } ``` Typst Settings explained: This configuration help use the same fonts as the CI building tinymist docs: ```json { "tinymist.fontPaths": [ "assets/fonts" ], } ``` Formatter Settings explained: This configuration runs formatters on save and using the `prettier` formatter: ```json { "[javascript]":{ "editor.formatOnSave": true, "editor.defaultFormatter": "esbenp.prettier-vscode", }, "[json]": { "editor.formatOnSave": true, "editor.defaultFormatter": "esbenp.prettier-vscode" }, } ```