Skip to content

env: node: No such file or directory on MacOS #897

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
zulus opened this issue May 22, 2024 · 3 comments
Open

env: node: No such file or directory on MacOS #897

zulus opened this issue May 22, 2024 · 3 comments

Comments

@zulus
Copy link

zulus commented May 22, 2024

In logs in osx, I see for example:

[21:46:53.665] Updating types-registry npm package...
[21:46:53.665] Exec: "/Applications/EclipseJava.app/Contents/Eclipse/.node/node-v18.18.2-darwin-arm64/lib/node_modules/npm/bin/npm-cli.js" install --ignore-scripts types-registry@latest
[21:46:53.676]     Failed. stdout:
    stderr:
    env: node: No such file or directory

npm-cli.js just have #!/usr/bin/env node so I afraid PATH env is not forwarded to subprocess

@predragnikolic
Copy link
Contributor

The error you posted is not related to this repository.
Please provide more details and context.

@zulus
Copy link
Author

zulus commented May 22, 2024

Eclipse WildWebDeveloper use types-script-language server to provider intellisense for TS/JS files. While analyzing another issue, I saw this error on MacOS. Off course if I use {disableAutomaticTypingAcquisition:true} error gone but I would like to have automaticTypingAcquisition enabled

@stark-jarvis
Copy link

I also encountered the same problem。

The same configuration works fine when running Neovim in iTerm2, but errors occur in the Neovide GUI.

View lsplog as follows:

[START][2024-07-23 17:30:58] LSP logging initiated

[ERROR][2024-07-23 17:30:58] .../ vim/lsp/rpc.lua:770 "rpc" "~/.local/share/nvim/mason/bin/typescript-language-server" "stderr" "env: node: No such file or directory\n"

I use Lazy.nvim and mason.nvim 、mason-lspconfig.nvim、nvim-lspconfig

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants