search

davestewart / alias-hq

The end-to-end solution for configuring, refactoring, maintaining and using path aliases
https://davestewart.co.uk/projects/open-source/alias-hq/
MIT License
333 stars 12 forks source link

Tsconfig parser does not support Node.js-style resolution of the `extends` field #72

Closed bjoluc closed 1 year ago

bjoluc commented 1 year ago

65 removed support for Node.js-style resolution of the tsconfig extends field – something that TypeScript can do. Implementing this from-scratch is not entirely trivial, but get-tsconfig has it all. @davestewart Since you decided against get-tsconfig, I'm not sure if there's a reason not to use it in this project? If not, I'm happy to submit a PR (I'm desperately depending on module resolution in extends :smiling_face_with_tear:). Just drop me a thumbs-up reaction here if get-tsconfig would also work.

davestewart commented 1 year ago

Ah! Wasn't aware there was a difference. That was removed for other reasons. If this other package does it right then it's a candidate.

Let me take a look later today (actually have some free time as I'm on holiday) and report back 👍

bjoluc commented 1 year ago

Thanks for the super-fast reply! For the reference and maybe to save you some time, here's how TS resolves extends paths and here's how get-tsconfig does it.

EDIT: TS 5 allows extends to be an array, so now is the time to rely on other projects to add support for this :smile:

davestewart commented 1 year ago

The README for the project looks just the ticket.