Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Lazy Extra Typst uses outdated Typst Version

Open
#176 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
55/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Tech stack
lua, neovim
Domain
tooling

Research direction

Locate the Lazy Extra LSP configuration for tinymist and inspect how its version is selected. Compare that source with the 0.13.1 version reported in the issue, then verify the configuration uses the current supported version and that tinymist still attaches and formats Typst files.

Written by the indexing model from the issue text.

Description

With the used lsp configuration, an older typst/tinymist version 0.13.1 is used. The current one is 0.14.2

I changed the lsp config in this way so that it is forced to use my tinymist version.

{
"neovim/nvim-lspconfig",
opts = {
    servers = {
      tinymist = {
        cmd = { vim.fn.exepath("tinymist") }, -- or full path to the tinymist server executable
        keys = {
          {
            "<leader>cP",
            function()
              local buf_name = vim.api.nvim_buf_get_name(0)
              local file_name = vim.fn.fnamemodify(buf_name, ":t")
              LazyVim.lsp.execute({
                title = "Pin Main",
                filter = "tinymist",
                command = "tinymist.pinMain",
                arguments = { buf_name },
              })
              LazyVim.info("Tinymist: Pinned " .. file_name)
            end,
            desc = "Pin main file",
          },
        },
        single_file_support = true, -- Fixes LSP attachment in non-Git directories
        settings = {
          formatterMode = "typstyle",
          typst = { path = vim.fn.exepath("typst") }, -- if server accepts this
        },
      },
    },
  },
Dominant language
Lua
Stars
99
Forks
136
PR merge metrics
No merged PRs in 30d

Getting set up

We have not checked this project's setup files yet. Start from its README, and see our first-contribution guide for the general steps.

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.

More from LazyVim/lazyvim.github.io

All issues in LazyVim/lazyvim.github.io

Similar issues

More Lua issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.