expo / vscode-expo

Expo Tools keep you productive with debugging, IntelliSense, and prebuild previews
https://marketplace.visualstudio.com/items?itemName=expo.vscode-expo-tools
MIT License
433 stars 11 forks source link

fix: add workaround for package json fetch from autolinking #118

Closed byCedric closed 2 years ago

byCedric commented 2 years ago

Linked issue

Fixes #115

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.

github-actions[bot] commented 2 years ago

:tada: This PR is included in version 0.8.0 :tada:

The release is available on GitHub release

Your semantic-release bot :package::rocket: