fix: handle relative tsconfig.json paths

[stefanprobst]

this fixes a regression introduced in 4.7.3:

previously, the implicit base url used an absolute path (see here), which was changed to just using path.dirname() (see here)

this resulted in different paths being resolved for the base url here - in the example from #79 this would be:

// v4.7.5
const resolvedBaseUrl = path.resolve(
  path.dirname("e2e/tsconfig.json"),
  "e2e",
);
// '/home/stefan/e2e/e2e'

// v4.7.3
const resolvedBaseUrl = path.resolve(
  path.dirname("e2e/tsconfig.json"),
  "/home/stefan/e2e",
);
// '/home/stefan/e2e'

closes #79

[stefanprobst]

@privatenumber could you take a look at this please? thanks!

[privatenumber]

Actually took a look at the time and I was going to add a test but I went down a rabbit hole. Basically this needs a test to land. I don't mind doing it but might take some time.

[stefanprobst]

tried adding a test - let me know what you think (it does fail on master but passes on this branch).

[privatenumber]

🎉 This issue has been resolved in version 4.7.6 🎉

The release is available on:

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

Your semantic-release bot 📦🚀

[privatenumber]

Appreciate the PR @stefanprobst Thanks for working on this 🙏