sublimelsp / LSP-eslint

ESLint support for Sublime LSP plugin
MIT License
34 stars 5 forks source link

Why is the minimum requirement of node version so high? (>14) #53

Closed shrikrishnaholla closed 1 year ago

shrikrishnaholla commented 2 years ago

Troubleshooting: LSP-eslint

Version

 - selector

source.js | source.ts | source.jsx | source.tsx | source.js.jsx | source.js.react | source.ts.react | text.html.vue | text.html.basic

 - priority_selector

source.js | source.ts | source.jsx | source.tsx | source.js.jsx | source.js.react | source.ts.react | text.html.vue | text.html.basic

 - init_options
```json
{}

Active view

Project / Workspace

LSP configuration

## System PATH - /home//.nvm/versions/node/v12.20.1/bin - /usr/local/sbin - /usr/local/bin - /usr/bin - /bin - /usr/sbin - /sbin - /home//.local/bin --- I cannot upgrade to v14 yet, because of dependencies in some of my projects. Hence am not able to use this LSP server, although I'd like to. Is there any particular reason that the minimum required version is so high?
rwols commented 2 years ago

Is there any particular reason that the minimum required version is so high?

Yes. VSCode ships with v14.

rwols commented 2 years ago

If the user doesn't have node in his/her $PATH, then this package offers to download a modern node that is local to ST.

I don't know if there's a way to install a local node runtime, and then use that local node, while also having a system node in the $PATH. @rchl probably knows more about that.

rchl commented 2 years ago

Yes, open Preferences: LSP Utils Settings from Command Palette and set local runtime per instructions there.

The reason that 14 is required is because the underlaying eslint server requires Node 14+.