resolveFully don't use --out-file-extension value

[savi2w]

Describe the bug

If you use resolveFully: true with e.g. --out-file-extension mjs CLI option, the compiled code will try to import relative files using a fixed *.js extension causing a ERR_MODULE_NOT_FOUND error

Input code

No response

Config

{
  "$schema": "https://swc.rs/schema.json",
  "jsc": {
    "baseUrl": ".",
    "parser": {
      "dynamicImport": true,
      "syntax": "typescript"
    },
    "target": "es2022"
  },
  "module": {
    "noInterop": true,
    "resolveFully": true,
    "strictMode": true,
    "type": "es6"
  },
  "sourceMaps": true
}

Playground link (or link to the minimal reproduction)

https://github.com/savi2w/swc-repro-1

SWC Info output

No response

Expected behavior

I think the compiled code should use the provided value of --out-file-extension CLI option to import relative files

Actual behavior

No response

Version

^0.4.0

Additional context

No response

[savi2w]

I want to make a PR fixing this, but I don't know if my solution is right within the swc context. It is okay if the compiled code use the extension provided by --out-file-extension flag for imports?

[kdy1]

Yeah I think so but currently the value of --out-file-extension is not passed to @swc/core

[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.