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.

Sign up for GitHub

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

Jump to bottom

Improve error message when npm isn't in PATH #2113

Open
sodic opened this issue Jun 22, 2024 · 0 comments
Open

Improve error message when npm isn't in PATH #2113

sodic opened this issue Jun 22, 2024 · 0 comments
Labels
dx shouldfix We should do/fix this at some point

Comments

@sodic
Copy link
Contributor

sodic commented Jun 22, 2024 •
edited
Loading

If a user starts a wasp command and npm isn't in PATH, this is the error they get:

[  Wasp  ] Starting npm installwasp-bin: npm: streamingProcess: exec: invalid argument (Bad file descriptor)

We should check if npm is in PATH and give our users a meaningful message if we don't find it (like we do when we don't find node).

Thanks @Rotemoyal for letting us know: #1980 (comment)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
dx shouldfix We should do/fix this at some point
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@sodic