Andrew Bradley

Sharing in case it's helpful: tsconfig-paths hooks into node's resolver here: https://github.com/dividab/tsconfig-paths/blob/master/src/register.ts#L73-L96 And it checks for package.json "main" field here: https://github.com/dividab/tsconfig-paths/blob/master/src/match-path-sync.ts#L85-L106 ...but doesn't check for the new `"exports"` nor `"module"`...

ts-node added experimental support for node's (also experimental) native ESM support. It's already been published, and feedback is being tracked here. https://github.com/TypeStrong/ts-node/issues/1007 However, ts-node doesn't need to hook into node's...

I'm referring specifically to node's new native ESM mode, where you have to use a special CLI flag to use a custom loader hook which intercepts ESM imports / exports....

Perhaps, I'm not sure. I don't think that's a use-case we need to prioritize. In other words, if you're writing code that works with `tsc` and with the language service,...

@jonaskello I'm reviewing #135 and looking at the behavior of the code immediately prior to when #27 was merged. It looks like when you require a directory containing a `package.json`,...

@jonaskello > If tsconfig-paths has found the exact file we want to resolve to, why should it then return less information to node, like removing the extension, or the returning...

Agreed about common goals. My goal is to make it work seamlessly with ts-node, perhaps even add a ts-node flag to register it automatically. But I also understand the need...

@miZyind Looks like a problem with nest. It's not clear how tsconfig-paths can possibly be causing this bug, since it's only responsible for resolving paths, not for stripping type-only imports...

I'm happy to switch to tfenv if you feel that is a better way to handle this situation. I hadn't seen it before. Now that I look at the readme,...

I tested `tfenv` and it is working well, so I've switched my project to `tfenv` and removed the vendored binaries. Thank you for the recommendation. I feel comfortable closing this...