Skip to main content
coc.nvim logococ.nvim
Extension Registry

Extensions Directory

A database-backed coc.nvim extension index refreshed from published packages.

Discovered from the official Wiki list and npm coc.nvim keyword search. Registry entries require a published npm latest version and engines.coc. Extensions are marked Deprecated when npm latest is deprecated or their GitHub repository is archived. GitHub checks use the repository URL from the published package.json when available. Published versions and manifests are synchronized daily.

Developer Guide

Choose by responsibility

Start with one language service for each language. It supplies completion, navigation and type diagnostics. Add a formatter when you need a particular code style, a linter for project rules, and snippets for reusable text. Installing more providers for the same job can produce duplicate diagnostics or competing formatting edits.

  • TypeScript / JavaScript: coc-tsserver provides the language service and includes TypeScript. First complete the setup walkthrough. Add ESLint only when the project uses ESLint rules; type checking and linting answer different questions.
  • Python: coc-pyright provides Python language analysis. Follow the Python environment example before investigating unresolved imports. Optional lint and format tools have their own installation and configuration requirements.
  • Java: coc-java starts Eclipse JDT Language Server. Check the tooling JDK, import the small Maven example, then verify a type diagnostic and definition jump before troubleshooting a larger project.
  • Before adding a second formatter, decide which tool owns formatting for that filetype and check format-on-save settings. Before adding another language extension, check whether an existing extension or manual languageserver entry already starts that server.

For other tasks, try a focused first workflow: Git hunk staging, patch diagnostics, SQL formatting, Dockerfile analysis or OpenAPI preview.

These are starting points, not a compatibility certification of every combination. Package versions, README text and configuration metadata below are synchronized from upstream; a recent release or passing upstream CI does not establish compatibility with your editor and project.

After each addition, reopen a project file and check completion, diagnostics and your intended formatting action. If a feature stops working, disable the last overlapping provider and follow the diagnostic guide.

Languages:
Building a custom coc.nvim extension?Dev Guide

Check out our official developer tools, templates, coc-test test runner, coc-repl, and coc-skills playbooks.

Open Developer Hub

Available extensions

102 of 102