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/paths

v0.15.1

Published

First-party ttsc plugin that rewrites emitted module specifiers from tsconfig paths.

Readme

@ttsc/paths

banner of @ttsc/paths

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

@ttsc/paths rewrites module specifiers that match compilerOptions.paths into relative JavaScript and declaration imports.

Setup

Install ttsc and TypeScript-Go, then the paths plugin:

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

Run your normal ttsc command:

npx ttsc

Configuration

@ttsc/paths has no separate plugin options. It reads the same compilerOptions.paths, rootDir, and outDir values that ttsc uses for the project.

Configure those fields under compilerOptions:

{
  "compilerOptions": {
    "paths": {
      "@/*": ["./src/*"],
      "@lib/*": ["./src/modules/*"],
    },
    "rootDir": "src",
    "outDir": "dist",
  },
}

An import such as import { value } from "@lib/value" becomes a relative JavaScript import such as import { value } from "./modules/value.js". Declaration output follows the same source rewrite.

outDir must be set for the rewrite to run. Without it, @ttsc/paths cannot map a source path to its emitted location and makes no changes. rootDir is optional: when omitted it is derived from the common source directory.

Sponsors

Sponsors

Thanks for your support.

Your donation encourages ttsc development.

References

Inspired by typescript-transform-paths.