Jonas Kello

You might want to try this package: https://github.com/dividab/graphql-simple-fetch

I think we want to keep tsconfig-paths logic as close as possible to how `tsc` resolves modules. Some thoughts on this: 1. The `exports` field of package.json is not supported...

I'm not really sure of the use case for the repro. Seems to do some bundling, but why use tsconfig-paths with it? Removing the `baseUrl` from tsconfig.json and the use...

Regarding resolving cjs/mjs there is an interesting comment from the typescript team [here](https://github.com/microsoft/TypeScript/pull/35148#issuecomment-606224545). Seems like there is going to be multiple resolution modes in the future. Not sure how this...

@katywings > All of those options have one question in common: why does it only fail with the baseUrl "./node_modules" but works without issues with baseUrl: "."? Yes that is...

> All of those options have one question in common: why does it only fail with the baseUrl "./node_modules" but works without issues with baseUrl: "."? I thought about it...

@katywings If the problem has nothing to do with the bundling perhaps it is possible to create a simpler repro that does not involve a bundler? For example does it...

I did an experiment/repro [here](https://github.com/jonaskello/tsconfig-paths-main-cjs) that does not involve `ts-node` or any bundling. It just uses `tsc` and `node`. It works without `tsconfig-paths` loaded but not with it. Looking into...

@cspotcode Yes, I know all of that, no explanation necessary :-). My point was that if ts-node compile and runs stuff by looking at the `exports` or `type` field in...

@cspotcode Yes, an example would be good, I'll try to put one together.