{"version":"2.1.275","anchor":"module-resolution-now-also-tries-mtscts-for-mjscjs","canonical_anchor":"module-resolution-now-also-tries-mtscts-for-mjscjs","heading":"Module resolution now also tries .mts\/.cts for .mjs\/.cjs","tier":"notice","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.275\/e\/module-resolution-now-also-tries-mtscts-for-mjscjs","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.275","markdown":"### Module resolution now also tries .mts\/.cts for .mjs\/.cjs\n\nImport resolution now also tries .mts and .cts file extensions for .mjs and .cjs imports\n\n**What**\n\nWhen resolving an import path, Claude Code's module resolver now also tries a `.mts` file if the import ends in `.mjs`, and a `.cts` file if it ends in `.cjs`. This joins the existing mapping that tries `.tsx` for a `.jsx` import.\n\n**Why**\n\nThis lets imports resolve correctly to TypeScript source files (`.mts`, `.cts`) even when the import specifier uses the compiled JavaScript extension (`.mjs`, `.cjs`).\n\n- Area: Elsewhere\n- Names: `.mts`, `.cts`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}