You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Node. is executable has a different name on this system: "nodejs" instead of "node". And it uses version 4 by default.
It causes some uninformative internal eclipse exceptions (null pointer) and omnisharp don't start.
Creating symlink doesn't help: instead of null pointer we got IOException "stream is closed". Omnisharp starts, but finds nothing (even for System package).
I can still write code and run the project, but it is just the same experience as using nano.
May be solved just by warning for Ubuntu users and specifying node. js version requirements?
The text was updated successfully, but these errors were encountered:
IIRC, there is a requirement on node being 7.x. Can you try with a more recent version?
Checking node version in the code and showing a warning is a good idea.
We're waiting for OmniSharp to deliver the support for the language server protocol in the roslyn server directly ( see OmniSharp/omnisharp-roslyn#968 and related PR OmniSharp/omnisharp-roslyn#969 ). While we would welcome patches to improve the handling of node for the current language server, I'd like to make it clear that neither @LucasBullen nor I will actively try to fix the node related issue as the future is in the roslyn server.
Node. is executable has a different name on this system: "nodejs" instead of "node". And it uses version 4 by default.
It causes some uninformative internal eclipse exceptions (null pointer) and omnisharp don't start.
Creating symlink doesn't help: instead of null pointer we got IOException "stream is closed". Omnisharp starts, but finds nothing (even for System package).
I can still write code and run the project, but it is just the same experience as using nano.
May be solved just by warning for Ubuntu users and specifying node. js version requirements?
The text was updated successfully, but these errors were encountered: