Unify TypeScript path aliases at compile time
The Problem
TypeScript compiler (tsc) does not rewrite path aliases to relative paths during compilation, forcing developers to use runtime loaders like tsconfig-paths (307M downloads/month) or post-build replacers like tsc-alias. This affects all TypeScript projects using aliases in tsconfig.json, particularly monorepos, Module Federation setups, and teams with dozens of projects requiring consistent builds. Developers currently spend time configuring 2-3 tools (tsc + tsc-alias + watcher) per project, with no seamless compile-time solution available.
Real Demand Evidence
Found on GitHub Wontfix — TypeScript issue #15479 ↗·Yesterday
TypeScript is a type checker and emitter, not a module bundler. Rewriting module specifiers would break an insanely large number of tools. — @DanielRosenwasser (closed Out of Scope, 307 reactions)
Core Insight
Unifies and rewrites TypeScript path aliases directly at compile time within tsc, eliminating runtime overhead, post-build steps, and tool chaining—plug-and-play tsconfig integration without bundlers or watchers, fixing gaps in direct competitors like tsconfig-paths and tsc-alias.
- Target Customer
- Indie hackers and solo founders building TypeScript/Node.js apps or monorepos (millions of npm TypeScript users), plus small dev teams in enterprises using Module Federation; TypeScript has 25M+ weekly npm downloads, with alias tools showing extreme usage.
- Revenue Model
- Freemium: Free core for solo devs, $10-25/month per seat for teams (Pro: monorepo support, CI integration, priority support); benchmarks free OSS volume against paid devtools like Vercel ($20+/mo) or Build tools with enterprise tiers.
Competitive Landscape
Free (open-source)
Operates as a runtime loader that registers path mappings dynamically, adding overhead and potential performance issues in production. Does not resolve aliases at compile time, requiring additional tooling chains.
Free (open-source)
Post-compilation script that replaces aliases with relative paths after tsc run, necessitating extra build steps and watch mode configuration. Lacks native compile-time integration, leading to fragile multi-tool workflows.
Free (open-source)
Bundler focused on esbuild-powered TypeScript builds that respects tsconfig paths during bundling, but not designed for standard tsc compilation or non-bundled outputs. Requires migrating away from plain tsc, unsuitable for many existing projects.
Free (open-source)
Handles module sharing across apps but lacks built-in TypeScript alias support in DtsPlugin, forcing workarounds like tsc-alias in MF projects. Adds complexity for non-federated setups.
Willingness to Pay
- 307M downloads/month (indicative of massive demand for alias solutions)
tsconfig-paths gets 307M downloads/month as a runtime workaround
User query signal provided
- Multi-tool chains per project (high friction driving paid alternative demand)
Teams chain 3 fragile tools across every project.
User query signal provided
Get the best signals delivered to your inbox weekly
Every Monday we pick the top scored opportunities from 9 sources and send them straight to you. Free forever.
No spam. No credit card. Unsubscribe anytime.