fix: use path.join and __dirname for require package.json

[ddelgrosso1]

Thank you for opening a Pull Request! Before submitting your PR, there are a few things you can do to make sure it goes smoothly:

• Make sure to open an issue as a bug/issue before writing your code! That way we can discuss the change, evaluate designs, and agree on the general idea
• Ensure the tests and linter pass
• Code coverage does not decrease (if any source code was changed)
• Appropriate docs were updated (if necessary)

Fixes #1934 🦕

[timdp]

@ddelgrosso1 @shaffeeullah This is unnecessary. require() is always relative to the file itself.

Additionally, I don't think it has anything to do with #1934, which it's supposed to close. The issue there is that the import is conditional (through a try).

[faradaytrs]

@timdp You are right because it didn't fix the problem, now it immediately fails in runtime.

[timdp]

It would do, yes. In the case of esbuild, I imagine it leaves the require() untouched and then tries to find package.json relative to the working directory of the bundle rather than the source file. Both are invalid.

Like I said on the original report, I would attempt to avoid the fallthrough altogether by making sure the source file is always at the same depth, whether or not it's gone through a build step.