tsconfig paths not resolving in imported package about tsx HOT 8 CLOSED

This is expected behavior.

A TypeScript compilation—which is happening at runtime in this case—, cannot load more than one tsconfig.json at once. I imagine esr is looking up a tsconfig.json for each file, but that's expensive and also not correct behavior.

I verified that tsx's behavior is consistent with ts-node.

from tsx.

@privatenumber But this is not consistent with esbuild itself! In the reproduction repo:

❯ p esbuild test.ts --bundle > test.js

❯ cat test.js
"use strict";
(() => {
  // ../b/lib.ts
  console.log("imported lib");
})();

❯ node test.js
imported lib

So it's possible to build a production build with these aliases but not run it in dev mode with tsx? Please reconsider your decision.

from tsx.

@privatenumber thoughts?

from tsx.

Curious how esbuild works if setting a different tsconfig path?

https://esbuild.github.io/api/#tsconfig

from tsx.

@privatenumber esbuild supports multiple tsconfig.json from referenced folders - same as I would expect from tsx.

This is explicitly stated by Evan, e.g.:

• evanw/esbuild#277 (comment): "different directories can take their settings from different tsconfig.json files with esbuild"
• https://pullanswer.com/questions/esbuild-resolves-modules-by-using-the-typescript-modulesuffixes-per-package-instead-of-per-bundle#711300: "This is why esbuild supports multiple tsconfig.json files: because each folder with a tsconfig.json file in it is conceptually a thing that you would traditionally run tsc in for each one before bundling."

from tsx.

How does it handle custom tsconfig.json paths via the tsconfig CLI flag for multiple projects?

e.g. If project A uses tsconfig.a.json and its dependency project B uses tsconfig.b.json, how is it configured?

from tsx.

I'm not following how is that related to the case. From what I've quickly gathered, there's no esbuild API option to provide different custom named tsconfig's for different projects. Why would that matter?

from tsx.

In case the uncompiled dependency project has a custom tsconfig (eg. with paths configured).

I'm going to lock this thread in favor of #96 since this one is already closed.

from tsx.