fix: resolve relative path extends in parent directory

[nwalters512]

Closes #76.

Using path.resolve to obtain an absolute path ensures that we search all the way up, instead of stopping at directoryPath.

[privatenumber]

Appreciate your contributions as always @nwalters512 !

I invited you to my private development org if you're interested. Would love to collaborate more!

[privatenumber]

🎉 This PR is included in version 4.7.5 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀

[nwalters512]

Thanks @privatenumber! I accepted the invitation.

[mrazauskas]

Seems like this change broke something with resolution of paths.

My project is using get-tsconfig via eslint-import-resolver-typescript. Recent lock file update failed because of resolution errors (the failure is gone, if get-tsconfig is not upgraded): https://github.com/tstyche/tstyche/actions/runs/9055459985/job/24876636622

paths are defined here (seems that the latest version of get-tsconfig fails to resolve this case):

https://github.com/tstyche/tstyche/blob/e3d6dd816849818aeac8ad9a9bbf373c8407932b/source/tsconfig.json#L6-L8

[privatenumber]

Would you mind filing a bug report, or a PR with a fix & test?

[mrazauskas]

Sorry, I can’t find time for that any soon. Just wanted to draw your attention.

[privatenumber]

Thanks, but until the bug is proven to be in get-tsconfig, I'm not able to invest time debugging (often times it turns out it's unrelated and I'm end up just debugging stuff for other people).

I'm going to lock this thread because it's not the appropriate place to discuss this.