tsx does not respect tsconfig path aliases? about tsx HOT 6 CLOSED

Because tsx is using esbuild transform mode as an esm loader/require.extensions to extend node.js, some features in build mode cannot be simply supported.

from tsx.

I think standard Node.js resolution mechanisms should work just fine here. I'd look at:

https://nodejs.org/api/packages.html#subpath-imports
https://nodejs.org/api/packages.html#subpath-exports

And try to leverage those. So your exports in package.json could look like this maybe?

"exports": {
  ".": "./app"
}

I use those successfully for all my monorepo packages that have the source code within ./src/* directory. tsx works well with those.

from tsx.

Because tsx is using esbuild transform mode as an esm loader/require.extensions to extend node.js, some features in build mode cannot be simply supported.

Got it, and no worries. It might be nice to add a note of this in the README to save future readers some time.

from tsx.

We're not constrained to rely solely on esbuild so its definitely possible to implement.

To your original post: are you referring to Node.js import maps, or TypeScript path aliasing?

Seems your title and example are talking about different things.

If it's Node.js import maps, it should already work. Please provide a minimal repro if its not working.

from tsx.

We're not constrained to rely solely on esbuild so its definitely possible to implement.

To your original post: are you referring to Node.js import maps, or TypeScript path aliasing?

Seems your title and example are talking about different things.

If it's Node.js import maps, it should already work. Please provide a minimal repro if its not working.

Sorry for the ambiguity, I'm referring to Typescript import aliases.

from tsx.

Closing as duplicate of #3

from tsx.