feat: add fallback option to avoid meaningless result.

[emosheeep]

#65

[privatenumber]

Why would we need to accept a fallback if TypeScript doesn't accept a fallback?

[emosheeep]

I was not sure if this is an intending behavior so I made it a feature not a bug fix. we can return an empty array when matched value is null on condition that you're sure the behavior to join baseUrl and a mismatched alias is really meaningless.🤔

[emosheeep]

how do you think about it ？🌚

[privatenumber]

I haven't had time to take a look yet, but very high chance I won't be accepting any options TypeScript doesn't accept.

The point of this project is feature parity so it should do exactly what TypeScript does.

[emosheeep]

emmm does it mean ts will join baseUrl and alias directly even if the path is meaningless ？Sorry I don't aware of this at that moment，if it is， just keep it as it was.

[privatenumber]

Again, I haven't looked into this at all — haven't even understood what problem it's addressing.

But for the tests, it runs TypeScript to get it's correct behavior via getTscResolution. Have you tried comparing results to that?

[emosheeep]

It seems that getTscResolution function calculated these:

It did join them together...what confused me a lot...but as what you said, if this project aims to be a feature, maybe it can extend this behavior and remove the meaningless part.

For a better user experiences, it’ll be convenient if the resolved path is reliable, because it’s easy to judge a null value but hard to a wrong path, which may need to call the filesystem and manually try possible paths, it's not efficient on performance usually.

On the end, it’s your project and depends on you, what I thought about is just a reference, sorry to bother you, I’m not in emergency, you have enough time.

Have a good day~