@swc-node/register@1.8.0 /esm-register does not recognise tsconfig.json paths

[mylesj]

I was playing with the latest and greatest and notice that when running via:

node --import @swc-node/register/esm-register src/index.ts

… tsconfig.json path aliases are not recognised, e.g.

{
  "compilerOptions": {
    "paths": {
      "@/*": ["./src/*"]
    }
  },
}

minimal reproducible example

Stack trace

node:internal/process/esm_loader:34
      internalBinding('errors').triggerUncaughtException(
                                ^
Error [ERR_MODULE_NOT_FOUND]: Cannot find module '/src/common' imported from /Users/myles/dev/issue-swc-node-1/src/index.ts
    at finalizeResolution (node:internal/modules/esm/resolve:264:11)
    at moduleResolve (node:internal/modules/esm/resolve:917:10)
    at defaultResolve (node:internal/modules/esm/resolve:1130:11)
    at nextResolve (node:internal/modules/esm/hooks:865:28)
    at resolve (file:///Users/myles/dev/issue-swc-node-1/node_modules/.pnpm/@swc-node+register@1.8.0_@swc+core@1.3.107_@swc+types@0.1.5_typescript@5.3.3/node_modules/@swc-node/register/esm/esm.mjs:44:12)
    at nextResolve (node:internal/modules/esm/hooks:865:28)
    at Hooks.resolve (node:internal/modules/esm/hooks:303:30)
    at MessagePort.handleMessage (node:internal/modules/esm/worker:196:24)
    at [nodejs.internal.kHybridDispatch] (node:internal/event_target:826:20)
    at exports.emitMessage (node:internal/per_context/messageport:23:28) {
  code: 'ERR_MODULE_NOT_FOUND',
  url: 'file:///src/common'
}

Also of note: I am aware that native ESM would typically expect file-extensions to be specified in the import, but including them doesn't help in this case - though I think the expectation of swc would be not to care either way?

[yeliex]

it is a bug caused by #722

@Brooooooklyn maybe we should consider revert it temporarily, it is a major breaking change and should add more test cases. it caused many unexpected results about resolve and compile. relate: #752 #734 #727.

i tried to fix these issues (#754) but cause more complication issues with @swc/core

@cm-ayf #727 (comment)

[galaxy-s10]

same problem

[c3cris]

It might be the same as #758

[alfaproject]

I've just stumbled upon this )':

[cghiurea]

I've just stumbled upon this )':

@alfaproject, you could use this node --watch --no-warnings=ExperimentalWarning --loader ts-node/esm src/server.ts as it will work depending on your project.

[alfaproject]

Well, TS paths resolution doesn't work and that's why I was trying swc-node to begin with:

❯ node --no-warnings=ExperimentalWarning --loader ts-node/esm ./apps/lambda-api/src/extract-schema.ts

node:internal/process/esm_loader:34
      internalBinding('errors').triggerUncaughtException(
                                ^
Error: Cannot find module '/Users/joaodias/the-mill/lambda-gaming.nosync/apps/lambda-api/src/schemas/schema' imported from /Users/joaodias/the-mill/lambda-gaming.nosync/apps/lambda-api/src/extract-schema.ts

[yeliex]

#754 should fix this, i would test later. feedback please.