Example using SWC with path aliases?

[jasonkuhrt]

I haven't been able to get ts-node + SWC + TS path aliases to work. My simple PR/attempt is here jasonkuhrt/template-typescript-lib#55. Anyone can point out the issue or a different working example?

Thanks!

[cspotcode]

For starters, how do you use path aliases without swc? We can build off of that.

[jasonkuhrt]

@cspotcode I'm not sure I follow. I already have it working without SWC. I assumed the issue would be on the SWC level.

[cspotcode]

I assume typescript-transform-paths works by hooking into the typescript compiler, but if you replace that compiler with swc, then it can't do that transformation. The links I shared relate to solutions for path mapping that do not require hooking into the TS compiler, so they're compatible with swc.

[jasonkuhrt]

@cspotcode Yeah I understood that the previous solution was using TSC which SWC does not. However based on the links in my PR I expected SWC to support path aliasing out of the box. For example: swc-project/swc#1935 and https://swc.rs/docs/configuration/compilation#jscpaths.

But now I see your point about your own links that those can be used in a way that is not reliant on TSC. I'll give that a shot!

That said, I feel like this should be possible with vanilla SWC... 🤔

[jasonkuhrt]

Thanks @cspotcode https://typestrong.org/ts-node/docs/paths/ worked for me for now 👏

[cspotcode]

Yeah, the problem with handling mappings in the TS->JS transformation layer, is that we've got a bunch of QOL resolver behaviors planned: #1514 I don't think it'd be feasible to implement all of them in a way that meets the requirements:

a) done within the transformer
b) compatible with all transformers: typescript, swc, other future third-party transformers
c) compatible with pre-compiled code (if a project has a mix of compiled ts and non-compiled js, we probably want these resolver behaviors to apply to both)

Instead we opt to implement resolutions within the node engine's own resolver.