Jonas Kello

@GeoffreyBooth Thanks for the reply! :-). Yes you are correct that is what I'm looking for. I currently can see two main ways it could be implemented. Either as options...

Yes this is exactly what I meant. Having a fine grained API with functions that does a little part each so you can compose your own loader from that and...

I noticed [PR 44501](https://github.com/microsoft/TypeScript/pull/44501) in the typescript repo where @weswigham is working on node12 and nodenext module resolution for the typescript compiler. I have not looked deep into that code...

Regarding which functions I would need in the API. My goal is to be able to resolve typescript files, not just in simple cases for absolute/relative files, but in more...

Yes, I also think subpath imports could replace `tsconfig.paths`. I'm kind of hoping the typescript team makes `tsconfig.paths` incompatible with the node12 modules setting so we don't have to support...

Yes, `packageJson.workspaces` and `tsconfig.references` work in tandem. Using workspaces you get symlinks for your packages in `node_modules`. Using `tsconfig.references` each package can have it's own `tsconfig.json` for separate root/outDir and...

@giltayar Yes that works for simple cases. For example [esbuild-node-loader](https://github.com/antfu/esbuild-node-loader/blob/main/loader.mjs) also takes a simple approach. I don't think there is something bad about this if that is all you need....

The format is specified in the first column so I think it the resolve part should just be removed? Acceptable types For source returned by ~resolve or~ load

I tried for the longest time to make `OTEL_LOG_LEVEL` work and finally found this issue. Added the code below and now it works: ```ts api.diag.setLogger(new DiagConsoleLogger(), getEnv().OTEL_LOG_LEVEL); ```

I have the same issue with Docker Desktop 4.11.1 on Windows: ``` ❯ docker compose up -d Invalid template: "{\"dev\": \"^(all|jonas)$\"}" ``` My `.env` file has this line, if I...