Auto-discover for elm-format fails when using nvm on linux
See original GitHub issueWhen 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:
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?
(Possibly related to #252 ?)
Issue Analytics
- State:
- Created 4 years ago
- Comments:5 (3 by maintainers)
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,...
Read more >vmtouch - OSCHINA - 中文开源技术交流社区
快速定位性能瓶颈,检查出所有资源(CPU、内存、磁盘IO等)的利用率(utilization)、饱和度(saturation)和错误(error)度量,即USE方法.
Read more >FreeBSD Ports Collection Index - UCU Open Source Mirror
44bsd-more-20000521_1 -- The pager installed with FreeBSD before less(1) was ... HeroesOfMightAndMagic-3_1 -- BSD Installation of the Linux game "Heroes of ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@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.
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 yourPATH
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 tonode
and then internally when I runelm-format
orelm-test
, I can augment thePATH
to include whatever value you provide. As an optimization, I can try to pre-populate based on.nvmrc
, if available.