Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix Yarn diagnose report support by not assuming node_modules exists #1038

Open
unflxw opened this issue Apr 19, 2024 · 0 comments
Open

Fix Yarn diagnose report support by not assuming node_modules exists #1038

unflxw opened this issue Apr 19, 2024 · 0 comments
Labels

Comments

@unflxw
Copy link
Contributor

unflxw commented Apr 19, 2024

The diagnose report, when executed via npx @appsignal/cli@latest diagnose (which is the currently recommended way to execute it) checks for the presence of a node_modules in the current folder, or any folders above it, and looks for @appsignal/nodejs within it, in order to require the actual implementation of the diagnose report from it.

This is incompatible with package managers such as Yarn, which do not store dependencies in a node_modules folder at the root of the project.

@unflxw unflxw added the bug label Apr 19, 2024
@unflxw unflxw self-assigned this Apr 19, 2024
@unflxw unflxw changed the title Fix Yarn diagnose report support by not assuming node_modules Fix Yarn diagnose report support by not assuming node_modules exists Apr 19, 2024
@unflxw unflxw removed their assignment Apr 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant