Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Auto-discover for elm-format fails when using nvm on linux

See original GitHub issue

When using nvm on Linux to manage node.js versions, the auto-discovery process will fail when checking the versions for elm-format and elm-test:

Screenshot 2019-09-30 at 08 22 27

The plugin seems to be assuming that the node executable is under /usr/bin/env; perhaps it would have more luck if it used the path in the node.js settings of the IDE?

Screenshot 2019-09-30 at 08 24 32

(Possibly related to #252 ?)

Issue Analytics

State:
Created 4 years ago
Comments:5 (3 by maintainers)

Top GitHub Comments

1reaction

yonigibbscommented, Jan 3, 2020

@r-k-b : some NVM-related docs have now been added here. If this issue is still affecting you, maybe this might help you resolve the problem.

1reaction

klazukacommented, Oct 2, 2019

This plugin does not make any assumptions that node lives at /usr/bin/env/node. It’s the npm-installed wrapper scripts for elm-format and elm-test that start with #!/usr/bin/env node. Which in turn relies on your PATH env var to locate node.

Setting PATH for GUI apps is platform-dependent, and not obvious at all. So maybe I need to provide a separate text box for the path to node and then internally when I run elm-format or elm-test, I can augment the PATH to include whatever value you provide. As an optimization, I can try to pre-populate based on .nvmrc, if available.

Top Results From Across the Web

Package Reporting and Search

Amazon Linux 2 Latest ... files: * Pretty-printing data bases * Syntactic checks with error recovery * Semantic checks * Sorting ... hs-elm-format,...