Skip to main content
Back to Extensions Directory
coc.nvim fallback icon

coc-pretty-ts-errors

hexh

coc-pretty-ts-errors

Installation CommandVim prompt
:CocInstall coc-pretty-ts-errors
GitHub owner
hexh
Version
v0.0.30
Requirements
coc ^0.0.82
License
Anti-996
Repository
GitHub
npm latest published 2024-12-05Registry checked 2026-08-23Registry summary

Published Package Summary

coc-pretty-ts-errors

Inspired by https://github.com/yoavbls/pretty-ts-errors. This CoC extension is a port of the original extension to work with CoC.

Based on https://github.com/hexh250786313/pretty-ts-errors-markdown.

https://github.com/hexh250786313/coc-pretty-ts-errors/assets/26080416/8fdbf55f-0b4e-4421-b8bf-44d144230355

Features

  • Show TypeScript error messages in a more readable format.

  • You can choose to use doHover or diagnostic floating window to display error message by option pretty-ts-errors.mode.

  • There are two ways to highlight code blocks, one is to use the highlight group PrettyTsErrorType to highlight a single color, and the other is to use ts syntax highlight.

    pretty-ts-errors.codeBlockHighlightTypescreenshotdescription
    "prettytserr"prettierUse highlight group PrettyTsErrorType to highlight a single color.
    "typescript"tsUse ts syntax highlight. And for correct syntax highlight it will extra add a "type Type = " before type definition in code blocks.

    ※ Personally, I prefer to use prettytserr to highlight a single color, because it is more readable and does not affect the original code.

Usage

Make sure you have coc.nvim and coc-tsserver installed.

And make sure your coc.nvim includes the pr https://github.com/neoclide/coc.nvim/commit/9c079ad79d66d4ede7886cc4094a822352559502 which gives diagnostic floating window highlight.

Then run the following command:

:CocInstall coc-pretty-ts-errors

Highlight Group

  • CocMarkdownCode is for inline code.
  • CocMarkdownLink is for file link.
  • PrettyTsErrorType is for the code block if you choose prettytserr in pretty-ts-errors.codeBlockHighlightType. PrettyTsErrorType defaults link to CocMarkdownCode.
2024-07-09_10-48 Click to see the different ways of highlighting demo1 demo2 demo3

Q & A

  • Q: When to use serverName

  • A: Examples:

    • When using coc-tsserver , serverName is "tsserver"

    • When using a customized typescript "languageserver", you need to modify serverName to the corresponding values, such as typescript-language-server

      // coc-settings.json
      "pretty-ts-errors.serverName": "my-tsserver",
                                     ~~~~~~~~~~~~~          Your customized typescript language server name.
      "languageserver": {
          "my-tsserver": {
          ~~~~~~~~~~~~~          `serverName` is from here.
              "enable": true,
              "command": "typescript-language-server",
              "args": ["--stdio"],
      
              ...
              ...other options
      
          }
      }
      
    • Some common typescript language server names:

Read the complete README
  • coc-pretty-ts-errors
Activation Events
  • onLanguage:javascript
  • onLanguage:javascriptreact
  • onLanguage:javascript.jsx
  • onLanguage:typescript
  • onLanguage:typescript.tsx
  • onLanguage:typescript.jsx
  • onLanguage:typescriptreact
  • onLanguage:jsx-tags
  • onLanguage:jsonc
  • onLanguage:vue
Developer Resources

Want to build, test, or contribute to coc.nvim extensions? Explore our official SDK and testing toolkits.

Open Developer Guide

Version History

This published npm package does not include a history.md or changelog.md file. Browse its npm versions or repository releases for available release information.