Unable to find module with tsconfig-paths when using esm: tsconfig-paths is incompatible with native ESM

[kikyouink]

Expected Behavior

tsconfig-paths can read my alias in tsconfig.json

Actual Behavior

tsconfig-paths can't read my alias in tsconfig.json

Steps to reproduce the problem

i use nodemon，here is my modemon.json

{
    "watch": ["*"],
    "ext": "ts,js,json",
    "exec": "node --loader ts-node/esm -r tsconfig-paths/register ./src/server/server.ts"
}

Minimal reproduction

just run nodemon

Specifications

• ts-node version: 10.0.0
• node version: 16.0.0
• TypeScript version: 4.3.2
• tsconfig.json, if you're using one:

{
    "ts-node": {
        "transpileOnly": true,
        "files": true,
    },
    "compilerOptions": {
        "target": "ESNext",
        "module": "ESNext",
        "moduleResolution": "node",
        "strict": true,
        "jsx": "preserve",
        "sourceMap": true,
        "resolveJsonModule": true,
        "noImplicitThis": true,
        "noEmit": true,
        "removeComments": true,
        "esModuleInterop": true,
        "lib": ["ESNext", "dom"],
        "baseUrl": ".",
        "paths": {
            "@/*": ["src"],
            "@components/*": ["src/components/*"],
            "@config/*": ["src/config/*"],
            "@hooks/*": ["src/hooks/*"],
            "@views/*": ["src/views/*"],
            "@utils/*": ["src/utils/*"]
        }
    },
    "include": ["/**/*.ts", "/**/*.d.ts", "/**/*.vue"]
}

• Operating system and version: macos big sur 11.4
• If Windows, are you using WSL or WSL2?:

[jeroen-hoekstra]

Experiencing the same issue. It works in version 9.1.1. Stopped working in version 10.0.0

[kikyouink]

Experiencing the same issue. It works in version 9.1.1. Stopped working in version 10.0.0

Unfortunately i tried 9.1.1，doesnt work too

[cspotcode]

tsconfig-paths does not support native ESM. Ts-node 9.1.1 has a limitation where it will allow you to (silently, accidentally) use CommonJS when you think you are using native ESM. Projects that are accidentally taking advantage of this behavior may find that things break on ts-node 10, since ts-node 10 fixes this flaw. When ts-node 9 silently runs your code as CommonJS, and tsconfig-paths is compatible with CommonJS, then things work. Fixes are either: - add native ESM support to tsconfig-paths - use CommonJS

…

On Wed, Jun 23, 2021, 2:59 AM SAI ***@***.***> wrote: Experiencing the same issue. It works in version 9.1.1. Stopped working in version 10.0.0 Unfortunately i tried 9.1.1，doesnt work too — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#1375 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAC35OEVKJAQRGRQYWK3RC3TUGA5VANCNFSM47AALGWQ> .

[kikyouink]

tsconfig-paths does not support native ESM. Ts-node 9.1.1 has a limitation where it will allow you to (silently, accidentally) use CommonJS when you think you are using native ESM. Projects that are accidentally taking advantage of this behavior may find that things break on ts-node 10, since ts-node 10 fixes this flaw. When ts-node 9 silently runs your code as CommonJS, and tsconfig-paths is compatible with CommonJS, then things work. Fixes are either: - add native ESM support to tsconfig-paths - use CommonJS
…
On Wed, Jun 23, 2021, 2:59 AM SAI @.***> wrote: Experiencing the same issue. It works in version 9.1.1. Stopped working in version 10.0.0 Unfortunately i tried 9.1.1，doesnt work too — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#1375 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAC35OEVKJAQRGRQYWK3RC3TUGA5VANCNFSM47AALGWQ .

thanks a lot , i think i'll use commonjs

[FossPrime]

You could also, bend your code to support relative imports... You may have to move it around if you use unpredictable, and that may break tests, linters transpilers ... I've just been living without typescript linting where I can't make it work yet.