Menu
Fix TypeScript ES module import errors by adding .js extensions to relative imports.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Find the commit that introduced a regression automatically with git bisect run.
Configure Jest for a TypeScript project — ts-jest, module mapping, and coverage thresholds.
Diagnose a slow Postgres query and add the right index using EXPLAIN ANALYZE.
Test React components with Testing Library — render, query by role, and assert on user-visible behavior.
Migrate a Jest test suite to Vitest — config, globals, and mock API differences.
Comprehensive guide for creating high-quality skills for Claude. Use when building a new skill, writing a SKILL.md, designing skill frontmatter, planning skill structure, debugging trigger issues, or reviewing an existing skill for improvements. Covers standalone skills, MCP-enhanced skills, and skill-tree programmatic skills.
| name | typescript-esm-import-fix |
| description | Fix TypeScript ES module import errors by adding .js extensions to relative imports. |
| version | 1.0.0 |
| tags | ["typescript","esm","imports"] |
| status | active |
TypeScript with ES modules requires explicit .js extensions in relative imports —
even though the source files are .ts.
.js extension to every relative import (./foo → ./foo.js)..js even when the file on disk is foo.ts.tsc --noEmit and confirm there are no module-resolution errors.If you can't touch every import, set "moduleResolution": "bundler" in tsconfig.json.