This is a sub-optimal workaround, but it does work. Instead of resolving the package.json by process.cwd(), we resolve it by the paths the methods are searching in. Once fetched, the path is cached for fast reuse.
Additional context
We probably need to switch to something like an LSP to remotely, and full Node, to resolve this type of data. Where we can fully embrace the usage of Node with our other tooling.
Linked issue
Fixes #115
This is a sub-optimal workaround, but it does work. Instead of resolving the
package.json
byprocess.cwd()
, we resolve it by the paths the methods are searching in. Once fetched, the path is cached for fast reuse.Additional context
We probably need to switch to something like an LSP to remotely, and full Node, to resolve this type of data. Where we can fully embrace the usage of Node with our other tooling.