-
Notifications
You must be signed in to change notification settings - Fork 6
Give better error message than "failed to run undefined undefined" if node unavailable #30
Comments
Hey thanks for the info. This is a good call. There are probably better search strategies for finding a valid node binary as well, before we fall back to raising an error message. I'll look into this when I can, otherwise PRs are accepted :) |
I am having the same issue. Workaround:
|
I just set Path to the node interpreter to use. Defaults to Atom's to If I get some time I might look into this, but if anyone else wants to pick this up and resolve. I wonder if there is a way of actually detecting which node binary Atom is using rather than just defaulting to the one that is expected to exist as |
Just to say - I've just spent twenty minutes with this same issue (also installed on Arch Linux). For some reason this issue doesn't come up when searching (via Duck Duck Go). I wonder if it might be worth including |
Updated. Sorry guys, I've actually switched back to vim since writing this plugin, but if someone had a PR, I'm happy to release it! |
Creating symlink back to the system node binary worked for me. On Arch:
|
When node is unavailable, the error that is presented is really unclear:
It isn't even obvious that the error is caused by the
linter-write-good
plugin - I only knew because I had just installed it when getting this message. Can you implement this failure in a more graceful way with a useful error message suggesting that the user alters their configuration?For reference, node is not available at
/usr/lib/node_modules/atom-package-manager/bin/node
when atom is installed using the atom package for Arch Linux.The text was updated successfully, but these errors were encountered: