Why are absolute ids skipped?

[eddiemonge]

On this line https://github.com/aleclarson/vite-tsconfig-paths/blob/master/src/index.ts#L114, it skips it if it is an "absolute path" but why?

I have this in my tsconfig: "paths": { "/*": ["./*"] }," so I can do imports like import CardNavItem from '/UI/CardNavItem';. This fails through the plugin but if I remove the isAbsolute check it works and in my limited testing, doesn't seem to break anything else.

[aleclarson]

It's a perf optimization. PR welcome

[rtmann]

Perf optimization? So is this saying that vite-tsconfig-paths does not support absolute alias's like "@common/models" ????

If so, I've wasted days debugging my build and this was the problem the whole time.

[aleclarson]

@rtmann This issue is about using tsconfig to redirect paths like /x/y/z (note the leading slash)

[pappnase99]

Just ran into this issue. Even though absolute paths are generally disencouraged, there are legitimate use cases. For example, if you want to deploy code into AWS Lambda functions, but you want to keep your deployment size as minimal as possible, you can use dependency layers where you can put common code like service classes etc. These layers are then mounted into the Lambda with a prefix '/opt', creating import paths like '/opt/services/MyService', so you know in the target runtime this absolute path will be available to your code.

So making absolute paths possible via config param/whatever would be a big improvement.

[aleclarson]

@pappnase99 Can't you just use explicit file extensions? I'm confused how tsconfig.json paths are used in this scenario.

[aleclarson]

I've decided to support this use case in v6.

You can give it a try starting with v6.0.0-beta.3:

pnpm add -D vite-tsconfig-paths@next

[pappnase99]

@pappnase99 Can't you just use explicit file extensions? I'm confused how tsconfig.json paths are used in this scenario.

Not sure if I understand your question, but in my use case it's about mapping an absolute file path to something in your workspace, that's why you have 'paths' entries in tsconfig like this: "/opt/services/*": ["./src/services/*"],. As explained, in the target runtime env the stuff will be deployed into the '/opt' path, but it's not there in compilation time.