arethetypeswrong/arethetypeswrong.github.io

Health v2 · maintenance only

Adoption not part of the score

1609 stars · 65 forks observed · 2026-10-07

What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-30, confidence not recorded

A tool that analyzes npm package contents for issues with their TypeScript types, particularly ESM-related module resolution problems across node10, node16, and bundler resolution modes. It is available both as a website for exploring packages and as a CLI (@arethetypeswrong/cli) for checking packages on disk.

Use cases

• check if my npm package's TypeScript types resolve correctly
• detect ESM/CJS module resolution issues before publishing
• verify package exports work in node16 and bundler module resolution
• find out why consumers get 'no types' errors for my package
• lint TypeScript type resolution in CI for a published library
• analyze npm pack output for type problems

When to choose

• you publish npm packages with TypeScript types and want to catch resolution issues before release
• you maintain a dual ESM/CJS library and need to verify exports in multiple module resolution modes
• you want to add type-resolution checks to a CI pipeline via the CLI

When to avoid

• you need general TypeScript type checking or linting of source code rather than package type resolution
• you need runtime testing of package behavior rather than static type analysis

Facets

cli-tool · maturity active

developer-tools testing parser developer-tools web-development frontend backend cli typescript npm-packages module-resolution esm cjs package-publishing type-checking nodejs web-server

Member repositories

For agents

markdown · JSON · MCP: product_card(name="arethetypeswrong/arethetypeswrong.github.io")