npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@ttsc/vscode

v0.15.1

Published

Show ttsc plugin diagnostics in VS Code, with @ttsc/lint errors, fix-all actions, and formatter support.

Readme

ttsc for VS Code

banner of @ttsc/vscode

GitHub license NPM Version NPM Downloads Build Status Guide Documents Discord Badge

Bring ttsc plugin diagnostics into VS Code.

When @ttsc/lint or another LSP-capable ttsc plugin like typia reports a compile-time diagnostic, this extension shows it in the editor next to normal TypeScript errors.

Use it when the project already runs ttsc. Add @ttsc/lint when you also want lint diagnostics, fix-all actions, and formatting in the editor.

VS Code showing ttsc lint diagnostics

Requirements

  • VS Code 1.94 or later.
  • Node.js 18 or later.
  • A workspace with tsconfig.json or jsconfig.json.
  • Project-installed ttsc, @typescript/native-preview, and the ttsc plugins you want editor diagnostics from.

Install the common project dependencies:

npm install -D ttsc @typescript/native-preview @ttsc/lint

@ttsc/lint is optional for TypeScript-Go language features, but required for the lint and format commands shown below.

Install

Install from the VS Code Marketplace by searching ttsc and choosing the extension by samchon.

From a shell, the short installer is:

npx @ttsc/vscode

The direct VS Code CLI form is:

code --install-extension samchon.ttsc

To uninstall the npm-installed copy:

npx @ttsc/vscode uninstall

Both shell commands use the code CLI. If it isn't on your PATH, run Shell Command: Install 'code' command in PATH from VS Code's command palette.

Configuration

lint.config.ts

At the project root, this drives both the lint rules and the formatter. Without it the extension still type-checks, but @ttsc/lint diagnostics and formatting do nothing:

// lint.config.ts
import type { ITtscLintConfig } from "@ttsc/lint";

export default {
  rules: {
    "no-var": "error",
    "prefer-const": "error",
    "typescript/no-explicit-any": "warning",
    "typescript/no-floating-promises": "error",
  },
  format: {
    printWidth: 100,
    singleQuote: true,
    trailingComma: "all",
  },
} satisfies ITtscLintConfig;

.vscode/settings.json

Set samchon.ttsc as the default formatter and turn on editor.formatOnSave:

{
  "[typescript][typescriptreact]": {
    "editor.defaultFormatter": "samchon.ttsc",
    "editor.formatOnSave": true
  }
}

Lint fixes stay off-save by default because they can change code meaning. Run ttsc: Fix all lint issues from the command palette, or opt in on manual saves:

{
  "editor.codeActionsOnSave": {
    "source.fixAll.ttsc": "explicit"
  }
}

What it adds

  • TypeScript-Go diagnostics, hover, navigation, and completions.
  • @ttsc/lint diagnostics and code actions, including source.fixAll.ttsc.
  • Diagnostics reported by other LSP-capable ttsc plugins.
  • ttsc: Fix all lint issues, ttsc: Format document, and ttsc: Restart language server in the command palette.
  • Format on save with the format block from lint.config.*.
  • Multi-root workspace support. Each package can use its own ttsc, @typescript/native-preview, tsconfig.json, and lint.config.*.

Save the file before relying on lint diagnostics or running the command-palette lint and format commands. Format-on-save works on the live editor buffer.

Troubleshooting

No diagnostics? Work through these in order:

  1. Confirm the workspace has a tsconfig.json or jsconfig.json.
  2. Confirm ttsc resolves in the project: npx ttsc --version.
  3. Confirm the project itself checks: npx ttsc --noEmit.
  4. Open View → Output → ttsc and read the server log.
  5. For full LSP tracing, set ttsc.trace.server to "verbose" and reload the window.

Sponsors

Sponsors

Thanks for your support.

Your donation encourages ttsc development.