LSP on Producthunt daily

zls

Sun, 24 Aug 2025 15:27:47 +0800

zigtools/zls

Need support? Wanna help out? Join our Discord server!

ZLS is a non-official implementation of the Language Server Protocol for Zig in Zig. It provides developers with IDE features in their editor.

Installation

See the Installation Guide for editor and binary installation instructions.

From Source

Building ZLS requires a build of Zig master.

1
2
3

git clone https://github.com/zigtools/zls
cd zls
zig build -Doptimize=ReleaseSafe

Features

ZLS supports most language features, including simple type function support, using namespace, payload capture type resolution, custom packages, cImport and others. Support for comptime and semantic analysis is Work-in-Progress.

The following LSP features are supported:

Completions
Hover
Goto definition/declaration
Document symbols
Find references
Rename symbol
Formatting using zig fmt
Semantic token highlighting
Inlay hints
Code actions
Selection ranges
Folding regions

sublime-zig-language by @prime31
- Supports basic language features
- Uses data provided by src/data to perform builtin autocompletion
zig-lsp by @xackus
- Inspiration for ZLS
known-folders by @ziglibs
- Provides API to access known folders on Linux, Windows and Mac OS
zls by @zigtools
- Used by many ZLS developers to more efficiently work on ZLS

Quick Thanks :)

We’d like to take a second to thank all our awesome contributors and donators/backers/sponsors; if you have time or money to spare, consider partaking in either of these options - they help keep ZLS awesome for everyone!

typescript-go

Wed, 28 May 2025 15:29:20 +0800

microsoft/typescript-go

TypeScript 7

Not sure what this is? Read the announcement post!

Preview

A preview build is available on npm as @typescript/native-preview.

1
2

npm install @typescript/native-preview
npx tsgo # Use this as you would tsc.

A preview VS Code extension is available on the VS Code marketplace.

To use this, set this in your VS Code settings:

1
2
3

{
    "typescript.experimental.useTsgo": true
}

How to Build and Run

This repo uses Go 1.24 or higher, Rust 1.85 or higher, Node.js with npm, and hereby.

For tests and code generation, this repo contains a git submodule to the main TypeScript repo pointing to the commit being ported. When cloning, you’ll want to clone with submodules:

`1`	`git clone --recurse-submodules https://github.com/microsoft/typescript-go.git`

If you have already cloned the repo, you can initialize the submodule with:

`1`	`git submodule update --init --recursive`

With the submodule in place and npm ci, you can run tasks via hereby, similar to the TypeScript repo:

hereby build          # Verify that the project builds
hereby test           # Run all tests
hereby install-tools  # Install additional tools such as linters
hereby lint           # Run all linters
hereby format         # Format all code
hereby generate       # Generate all Go code (e.g. diagnostics, committed to repo)

Additional tasks are a work in progress.

hereby is not required to work on the repo; the regular go tooling (e.g., go build, go test ./...) will work as expected. hereby tasks are provided as a convenience for those familiar with the TypeScript repo.

Running `tsgo`

After running hereby build, you can run built/local/tsgo, which behaves mostly the same as tsc.

Running LSP Prototype

To debug and run the VS Code extension without installing it globally:

Run VS Code in the repo workspace (code .)
Copy .vscode/launch.template.json to .vscode/launch.json
F5 (or Debug: Start Debugging from the command palette)

This will launch a new VS Code instance which uses the Corsa LS as the backend. If correctly set up, you should see “tsgo” in the status bar when a TypeScript or JavaScript file is open:

What Works So Far?

This is still a work in progress and is not yet at full feature parity with TypeScript. Bugs may exist. Please check this list carefully before logging a new issue or assuming an intentional change.

Feature	Status	Notes
Program creation	done	Same files and module resolution as TS5.8. Not all resolution modes supported yet.
Parsing/scanning	done	Exact same syntax errors as TS5.8
Commandline and `tsconfig.json` parsing	mostly done	Entry point slightly different for now
Type resolution	done	Same types as TS5.8
Type checking	done	Same errors, locations, and messages as TS5.8. Types printback in errors may display differently (in progress)
JavaScript-specific inference and JS Doc	not ready	-
JSX	done	-
Declaration emit	not ready	Coming soon
Emit (JS output)	in progress	`target: esnext` well-supported, other targets may have gaps
Watch mode	prototype	Watches files and rebuilds, but no incremental rechecking
Build mode / project references	not ready	-
Incremental build	not ready	-
Language service (LSP)	prototype	Minimal functionality (errors, hover, go to def). More features coming soon
API	not ready	-

Definitions:

done aka “believed done”: We’re not currently aware of any deficits or major left work to do. OK to log bugs
in progress: currently being worked on; some features may work and some might not. OK to log panics, but nothing else please
prototype: proof-of-concept only; do not log bugs
not ready: either haven’t even started yet, or far enough from ready that you shouldn’t bother messing with it yet

Other Notes

Long-term, we expect that this repo and its contents will be merged into microsoft/TypeScript. As a result, the repo and issue tracker for typescript-go will eventually be closed, so treat discussions/issues accordingly.

For a list of intentional changes with respect to TypeScript 5.7, see CHANGES.md.

Contributing

This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit Contributor License Agreements.

When you submit a pull request, a CLA bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., status check, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA.

This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact opencode@microsoft.com with any additional questions or comments.

Trademarks

This project may contain trademarks or logos for projects, products, or services. Authorized use of Microsoft trademarks or logos is subject to and must follow Microsoft’s Trademark & Brand Guidelines. Use of Microsoft trademarks or logos in modified versions of this project must not cause confusion or imply Microsoft sponsorship. Any use of third-party trademarks or logos are subject to those third-party’s policies.

mason.nvim

Sat, 10 May 2025 15:26:31 +0800

mason-org/mason.nvim

Portable package manager for Neovim that runs everywhere Neovim runs.
Easily install and manage LSP servers, DAP servers, linters, and formatters.

:help mason.nvim

^{Latest version: v2.0.0}

Introduction

:h mason-introduction

mason.nvim is a Neovim plugin that allows you to easily manage external editor tooling such as LSP servers, DAP servers, linters, and formatters through a single interface. It runs everywhere Neovim runs (across Linux, macOS, Windows, etc.), with only a small set of external requirements needed.

Packages are installed in Neovim’s data directory (:h standard-path) by default. Executables are linked to a single bin/ directory, which mason.nvim will add to Neovim’s PATH during setup, allowing seamless access from Neovim builtins (shell, terminal, etc.) as well as other 3rd party plugins.

For a list of all available packages, see https://mason-registry.dev/registry/list.

Screenshots

Requirements

:h mason-requirements

mason.nvim relaxes the minimum requirements by attempting multiple different utilities (for example, wget, curl, and Invoke-WebRequest are all perfect substitutes). The minimum recommended requirements are:

neovim >= 0.10.0
For Unix systems:
- git(1)
- curl(1) or GNU wget(1)
- unzip(1)
- GNU tar (tar(1) or gtar(1) depending on platform)
- gzip(1)
For Windows systems:
- pwsh or powershell
- git
- GNU tar
- One of the following:
  - 7zip
  - peazip
  - archiver
  - winzip
  - WinRAR

Note that mason.nvim will regularly shell out to external package managers, such as cargo and npm. Depending on your personal usage, some of these will also need to be installed. Refer to :checkhealth mason for a full list.

Installation

Packer

1
2
3

use {
    "mason-org/mason.nvim"
}

lazy.nvim

1
2
3

{
    "mason-org/mason.nvim"
}

vim-plug

`1`	`Plug 'mason-org/mason.nvim'`

Setup

:h mason-quickstart

`1`	`require("mason").setup()`

mason.nvim is optimized to load as little as possible during setup. Lazy-loading the plugin, or somehow deferring the setup, is not recommended.

Refer to the Configuration section for information about which settings are available.

Extensions

Refer to the Wiki for a list of 3rd party extensions.

mason-lspconfig.nvim - recommended for usage with lspconfig

Commands

:h mason-commands

:Mason - opens a graphical status window
:MasonUpdate - updates all managed registries
:MasonInstall <package> ... - installs/re-installs the provided packages
:MasonUninstall <package> ... - uninstalls the provided packages
:MasonUninstallAll - uninstalls all packages
:MasonLog - opens the mason.nvim log file in a new tab window

Registries

Mason’s core package registry is located at mason-org/mason-registry. Before any packages can be used, the registry needs to be downloaded. This is done automatically for you when using the different Mason commands (e.g. :MasonInstall), but can also be done manually by using the :MasonUpdate command.

If you’re utilizing Mason’s Lua APIs to access packages, it’s recommended to use the :h mason-registry.refresh() and/or :h mason-registry.update() functions to ensure you have the latest package information before retrieving packages.

Configuration

:h mason-settings

You may optionally configure certain behavior of mason.nvim when calling the .setup() function. Refer to the default configuration for a list of all available settings.

Example:

require("mason").setup({
    ui = {
        icons = {
            package_installed = "✓",
            package_pending = "➜",
            package_uninstalled = "✗"
        }
    }
})

Default configuration

---@class MasonSettings
local DEFAULT_SETTINGS = {
    ---@since 1.0.0
    -- The directory in which to install packages.
    install_root_dir = path.concat { vim.fn.stdpath "data", "mason" },

    ---@since 1.0.0
    -- Where Mason should put its bin location in your PATH. Can be one of:
    -- - "prepend" (default, Mason's bin location is put first in PATH)
    -- - "append" (Mason's bin location is put at the end of PATH)
    -- - "skip" (doesn't modify PATH)
    ---@type '"prepend"' | '"append"' | '"skip"'
    PATH = "prepend",

    ---@since 1.0.0
    -- Controls to which degree logs are written to the log file. It's useful to set this to vim.log.levels.DEBUG when
    -- debugging issues with package installations.
    log_level = vim.log.levels.INFO,

    ---@since 1.0.0
    -- Limit for the maximum amount of packages to be installed at the same time. Once this limit is reached, any further
    -- packages that are requested to be installed will be put in a queue.
    max_concurrent_installers = 4,

    ---@since 1.0.0
    -- [Advanced setting]
    -- The registries to source packages from. Accepts multiple entries. Should a package with the same name exist in
    -- multiple registries, the registry listed first will be used.
    registries = {
        "github:mason-org/mason-registry",
    },

    ---@since 1.0.0
    -- The provider implementations to use for resolving supplementary package metadata (e.g., all available versions).
    -- Accepts multiple entries, where later entries will be used as fallback should prior providers fail.
    -- Builtin providers are:
    --   - mason.providers.registry-api  - uses the https://api.mason-registry.dev API
    --   - mason.providers.client        - uses only client-side tooling to resolve metadata
    providers = {
        "mason.providers.registry-api",
        "mason.providers.client",
    },

    github = {
        ---@since 1.0.0
        -- The template URL to use when downloading assets from GitHub.
        -- The placeholders are the following (in order):
        -- 1. The repository (e.g. "rust-lang/rust-analyzer")
        -- 2. The release version (e.g. "v0.3.0")
        -- 3. The asset name (e.g. "rust-analyzer-v0.3.0-x86_64-unknown-linux-gnu.tar.gz")
        download_url_template = "https://github.com/%s/releases/download/%s/%s",
    },

    pip = {
        ---@since 1.0.0
        -- Whether to upgrade pip to the latest version in the virtual environment before installing packages.
        upgrade_pip = false,

        ---@since 1.0.0
        -- These args will be added to `pip install` calls. Note that setting extra args might impact intended behavior
        -- and is not recommended.
        --
        -- Example: { "--proxy", "https://proxyserver" }
        install_args = {},
    },

    ui = {
        ---@since 1.0.0
        -- Whether to automatically check for new versions when opening the :Mason window.
        check_outdated_packages_on_open = true,

        ---@since 1.0.0
        -- The border to use for the UI window. Accepts same border values as |nvim_open_win()|.
        -- Defaults to `:h 'winborder'` if nil.
        border = nil,

        ---@since 1.11.0
        -- The backdrop opacity. 0 is fully opaque, 100 is fully transparent.
        backdrop = 60,

        ---@since 1.0.0
        -- Width of the window. Accepts:
        -- - Integer greater than 1 for fixed width.
        -- - Float in the range of 0-1 for a percentage of screen width.
        width = 0.8,

        ---@since 1.0.0
        -- Height of the window. Accepts:
        -- - Integer greater than 1 for fixed height.
        -- - Float in the range of 0-1 for a percentage of screen height.
        height = 0.9,

        icons = {
            ---@since 1.0.0
            -- The list icon to use for installed packages.
            package_installed = "◍",
            ---@since 1.0.0
            -- The list icon to use for packages that are installing, or queued for installation.
            package_pending = "◍",
            ---@since 1.0.0
            -- The list icon to use for packages that are not installed.
            package_uninstalled = "◍",
        },

        keymaps = {
            ---@since 1.0.0
            -- Keymap to expand a package
            toggle_package_expand = "<CR>",
            ---@since 1.0.0
            -- Keymap to install the package under the current cursor position
            install_package = "i",
            ---@since 1.0.0
            -- Keymap to reinstall/update the package under the current cursor position
            update_package = "u",
            ---@since 1.0.0
            -- Keymap to check for new version for the package under the current cursor position
            check_package_version = "c",
            ---@since 1.0.0
            -- Keymap to update all installed packages
            update_all_packages = "U",
            ---@since 1.0.0
            -- Keymap to check which installed packages are outdated
            check_outdated_packages = "C",
            ---@since 1.0.0
            -- Keymap to uninstall a package
            uninstall_package = "X",
            ---@since 1.0.0
            -- Keymap to cancel a package installation
            cancel_installation = "<C-c>",
            ---@since 1.0.0
            -- Keymap to apply language filter
            apply_language_filter = "<C-f>",
            ---@since 1.1.0
            -- Keymap to toggle viewing package installation log
            toggle_package_install_log = "<CR>",
            ---@since 1.8.0
            -- Keymap to toggle the help view
            toggle_help = "g?",
        },
    },
}

^{👋 didn't find what you were looking for? Try looking in the help docs :help mason.nvim!}

nvim-lspconfig

Thu, 17 Apr 2025 15:30:46 +0800

neovim/nvim-lspconfig

nvim-lspconfig

nvim-lspconfig is a “data only” repo, providing basic, default Nvim LSP client configurations for various LSP servers.

View all configs or :help lspconfig-all from Nvim.

Important ⚠️

These configs are best-effort and supported by the community (you). See contributions.
If you found a bug in Nvim LSP (:help lsp), report it to Neovim core.
- Do not report it here. Only configuration data lives here.
This repo only provides configurations. Its programmatic API is deprecated and must not be used externally.
- The “framework” parts (not the configs) of nvim-lspconfig will be upstreamed to Nvim core.

Install

Requires Nvim 0.10 above. Update Nvim and nvim-lspconfig before reporting an issue.

Install nvim-lspconfig using Vim’s “packages” feature:

`1`	`git clone https://github.com/neovim/nvim-lspconfig ~/.config/nvim/pack/nvim/start/nvim-lspconfig`

Or use a 3rd-party plugin manager (consult the documentation for your plugin manager).

Quickstart

Install a language server, e.g. pyright
1

npm i -g pyright
Add the language server setup to your init.lua.
- Nvim 0.11+ (see vim.lsp.config)
  1
  
  vim.lsp.enable('pyright')
- Nvim 0.10 (legacy, not supported)
  1
  
  require'lspconfig'.pyright.setup{}
Ensure your project/workspace contains a root marker as specified in :help lspconfig-all.
Open a code file in Nvim. LSP will attach and provide diagnostics.
1

nvim main.py
Run :checkhealth lsp to see the status or to troubleshoot.

Read :help lspconfig for details. Read :help lspconfig-all for the full list of server-specific details. For servers not on your $PATH (e.g., jdtls, elixirls), you must manually set the cmd parameter, see vim.lsp.config.

Configuration

Nvim sets some default options and mappings when a buffer attaches to LSP (see :help lsp-config). In particular:

'tagfunc'
- Enables “go to definition” capabilities using <C-]> and other tag commands.
'omnifunc'
- Enables (manual) omni mode completion with <C-X><C-O> in Insert mode. For autocompletion, an autocompletion plugin is required.
'formatexpr'
- Enables LSP formatting with gq.
K maps to vim.lsp.buf.hover() in Normal mode.
[d and ]d map to vim.diagnostic.goto_prev() and vim.diagnostic.goto_next(), respectively.
<C-W>d maps to vim.diagnostic.open_float().

Further customization can be achieved using the LspAttach autocommand event. The LspDetach autocommand event can be used to “cleanup” mappings if a buffer becomes detached from an LSP server. See :h LspAttach and :h LspDetach for details and examples. See :h lsp-buf for details on other LSP functions.

Extra settings can be specified for each LSP server:

Nvim 0.11+ (see vim.lsp.config)

vim.lsp.config('rust_analyzer', {
  -- Server-specific settings. See `:help lsp-quickstart`
  settings = {
    ['rust-analyzer'] = {},
  },
})

Nvim 0.10 (legacy, not supported)

local lspconfig = require('lspconfig')
lspconfig.rust_analyzer.setup {
  -- Server-specific settings. See `:help lspconfig-setup`
  settings = {
    ['rust-analyzer'] = {},
  },
}

vim.lsp.config

nvim-lspconfig includes configurations compatible with vim.lsp under lsp/, so servers can be enabled (auto-activated when a filetype is opened) with:

`1`	`vim.lsp.enable('pyright')`

and configured with:

1
2
3

vim.lsp.config('pyright', {
  cmd = { … },
})

which extends the configuration under lsp/. For further information see :help lsp-config.

[!WARNING]
Some servers are currently missing.

Troubleshooting

The most common reasons a language server does not start or attach are:

Language server is not installed. nvim-lspconfig does not install language servers for you. You should be able to run the cmd defined in each server’s Lua module from the command line and see that the language server starts. If the cmd is an executable name instead of an absolute path to the executable, ensure it is on your path.
Missing filetype plugins. Certain languages are not detecting by Vim/Nvim because they have not yet been added to the filetype detection system. Ensure :set ft? shows the filetype and not an empty value.
Not triggering root detection. Some language servers will only start if it is opened in a directory, or child directory, containing a file which signals the root of the project. Most of the time, this is a .git folder, but each server defines the root config in the lua file. See doc/configs.md or the source for the list of root directories.
You must pass capabilities for each setup {} if you want these to take effect.
Do not call setup {} twice for the same server. The second call to setup {} will overwrite the first.

Bug reports

If you found a bug with LSP functionality, report it to Neovim core.

Before reporting a bug, check your logs and the output of :LspInfo. Add the following to your init.vim to enable logging:

`1`	`vim.lsp.set_log_level("debug")`

Attempt to run the language server, and open the log with:

:LspLog

Most of the time, the reason for failure is present in the logs.

Commands

:LspInfo (alias to :checkhealth vim.lsp) shows the status of active and configured language servers.
:LspStart <config_name> Start the requested server name. Will only successfully start if the command detects a root directory matching the current config. Pass autostart = false to your .setup{} call for a language server if you would like to launch clients solely with this command. Defaults to all servers matching current buffer filetype.
:LspStop [<client_id_or_name> ...] Stops the given server(s). Defaults to stopping all servers active on the current buffer. To force stop add ++force
:LspRestart [<client_id_or_name> ...] Restarts the given client(s), and attempts to reattach to all previously attached buffers.

Contributions

If a language server is missing from configs.md, contributing a new configuration for it helps others, especially if the server requires special setup. Follow these steps:

Read CONTRIBUTING.md.
Create a new file at lsp/SERVER_NAME.lua.
- Copy an existing config to get started. Most configs are simple. For an extensive example see texlab.lua.
Ask questions on GitHub Discussions or in the Neovim Matrix room.

Release process

To publish a release:

Create and push a new tag.
After pushing the tag, a GitHub action will automatically package the plugin and publish the release to LuaRocks.

License

nvim-lspconfig is licensed under the terms of the Apache 2.0 license.

See LICENSE.md

LSP on Producthunt daily

zls

zigtools/zls

Installation

See the Installation Guide for editor and binary installation instructions.

From Source

Features

Related Projects

Quick Thanks :)

typescript-go

microsoft/typescript-go

TypeScript 7

Preview

How to Build and Run

Running tsgo

Running LSP Prototype

What Works So Far?

Other Notes

Contributing

Trademarks

mason.nvim

mason-org/mason.nvim

Table of Contents

Introduction

Screenshots

Requirements

Installation

Packer

lazy.nvim

vim-plug

Setup

Extensions

Commands

Registries

Configuration

Default configuration

nvim-lspconfig

neovim/nvim-lspconfig

nvim-lspconfig

Important ⚠️

Install

Quickstart

Configuration

vim.lsp.config

Troubleshooting

Bug reports

Commands

Contributions

Release process

License

Running `tsgo`