bcomnes / sublime-standard-format

:sparkles: Runs standard --fix against the javascript in your ST3 window on save or manually.
https://packagecontrol.io/packages/StandardFormat
MIT License
60 stars 21 forks source link

b'env: node: No such file or directory\n' on "standard --fix" #68

Closed feljx closed 4 years ago

feljx commented 7 years ago

Hi,

every time I try to use standard-format, nothing happens and I get this error in my console.

b'env: node: No such file or directory\n'

I use the fish shell and nvm, but I also have my nvm config set up for Bash. Both .bashrc and .bash_profile have the proper node directory in their $PATHs.

Another guy had the same issue here, but nothing in that thread seems to work for me.

I also tried

"get_path_command": ["/usr/bin/env", "fish", "-l", "-i", "-c", "echo $PATH"].

Would love if you could help me! :)

bcomnes commented 7 years ago

I think some of the recent changes busted nvm for some people's environments. I unfortunately don't have time to look into this right away, so PRs are welcome if you are feeling adventurous. The plugin needs a bit of a rewrite however since its gone through some major revisions without a holistic approach to how environment is generated. Unfortunately Sublime leaves real user environment resolution all of this up to plugins to handle.

feljx commented 7 years ago

I have no clue why, but copy-pasting "standard-format.py" from this repo into a Sublime Text 3/Packages/StandardFormat folder fixes it.

I'm guessing that overrides the packed .py script... but since both are version 6.1.3 I don't know what that changes. Have you got any idea?

Also is it ok/better to just add the path manually instead? "PATH": ["my_nvm_node_bin_path"]

bcomnes commented 7 years ago

That will work too, but the idea was that you didn't have to do that.

feljx commented 7 years ago

I'd rather not overwrite plugin files on my first day of using Sublime. Especially since I don't know why that even works when I didn't change a single line of code.

bcomnes commented 4 years ago

Closing due to lack of movement. If there is something actionable on this, reopen or start a new issue.