typescript-modules-packaging

What problem does it solve? TypeScript packages often fail for consumers because the runtime loader, the compiler's resolver, and the package's public exports are configured as three mismatched contracts. This Skill diagnoses and aligns those contracts so published artifacts actually resolve for every supported consumer. ## Core Features & Use Cases - Resolution Matching: Pairs module and moduleResolution settings (NodeNext, bundler, CommonJS) with the actual deployment target instead of mixing incompatible emit and resolver strategies. - Explicit Export Surface: Defines exports targets with ./ paths, orders types before runtime conditions, and keeps forbidden deep imports unavailable. - Artifact Verification: Packs the real archive, installs it into isolated consumer fixtures, and compiles and executes public imports across every supported resolver and runtime. - Use Case: You are publishing a dual-audience npm library and consumers report broken subpath imports. Use this Skill to fix the exports map, emit a complete declaration graph, and verify the packed tarball in external ESM and CommonJS fixtures. ## Quick Start Review my package.json and tsconfig setup and make the published package resolve correctly for both ESM and CommonJS consumers.