Wrong root(cwd) determination for esm modules

[ThePlenkov]

Hi! During debug I have noticed something interesting. To use top-level await I've changed package to module and activated esm for ts-node. However right after this import for json files stopped working.
Here is what I have in IDE

And here is the base path ts-node is trying to resolve workspace.json against to.

I think you should take root path from tsconfig to resolve imports, same as typescript does. Otherwise is different logic

For now I'd prefer not to use ts-node with esm: true.

Thanks!

[ThePlenkov]

it's important - I run the command from the root npx my-command where my-command is a link to a workspace ts file with ts-node shebang

[ThePlenkov]

So current workaround instead of import to use dynamic import:

// import { projects } from 'workspace.json' assert { type: 'json' };

const projects = (await import(path.resolve(cwd(), 'workspace.json'), {
  assert: { type: 'json' },
})) as { default: { projects: Record<string, string> } };