swcpack: Fully-Specified ESM Import Specifier Fails

[karlhorky]

Describe the bug

Similar to this webpack bug, swcpack aka spack doesn't match the behavior and semantics of TypeScript when importing using a fully-specified path with a .js extension.

Eg. the following fails:

// index.ts
import { two } from './two.js';

// two.ts
export function two() {}

But does not fail when building with TSC.

Full repo with failing build script: https://github.com/karlhorky/swcpack-esm-fully-specified-demo

Input code

No response

Config

No response

Playground link

No response

Expected behavior

swcpack should match the semantics of TSC and TypeScript, and allow for fully-specified import paths with .js extensions for ESM.

See @RyanCavanaugh's comment here: microsoft/TypeScript#41887 (comment)

TypeScript doesn't modify JavaScript code you write, the import path you write should be the one you want to appear in the output .js file

Version

@swc/cli@0.1.55, @swc/core@1.2.120

Additional context

No response

[karlhorky]

Wow, that was a super fast fix, thanks @magic-akari and @kdy1 !! 🙌 🚀

[swc-bot]

This closed issue has been automatically locked because it had no new activity for a month. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.