npm是使用nvm安装的,但IntelliJ不知道它

Question

我按照以下页面使用NVM安装了NPM:npm抛出错误,没有sudo.在Ubuntu终端,一切都很完美.但是,在IntelliJ终端内部,它表示我没有安装NPM.我试图在语言和框架>节点和NPM中设置我的节点解释器,~/.nvm/versions/node/v6.8.0/bin/node 我启用了Node.js核心库,从那里我可以看到包含npm包.但终端仍然说我没有安装npm.为什么？

这是我的.bashrc

   
# ~/.bashrc: executed by bash(1) for non-login shells.
# see /usr/share/doc/bash/examples/startup-files (in the package bash-doc)
# for examples

# If not running interactively, don't do anything
case $- in
    *i*) ;;
      *) return;;
esac

# don't put duplicate lines or lines starting with space in the history.
# See bash(1) for more options
HISTCONTROL=ignoreboth

# append to the history file, don't overwrite it
shopt -s histappend

# for setting history length see HISTSIZE and HISTFILESIZE in bash(1)
HISTSIZE=1000
HISTFILESIZE=2000

# check the window size after each command and, if necessary,
# update the values of LINES and COLUMNS.
shopt -s checkwinsize

# If set, the pattern "**" used in a pathname expansion context will
# match all files and zero or more directories and subdirectories.
#shopt -s globstar

# make less more friendly for non-text input files, see lesspipe(1)
[ -x /usr/bin/lesspipe ] && eval "$(SHELL=/bin/sh lesspipe)"

# set variable identifying the chroot you work in (used in the prompt below)
if [ -z "${debian_chroot:-}" ] && [ -r /etc/debian_chroot ]; then
    debian_chroot=$(cat /etc/debian_chroot)
fi

# set a fancy prompt (non-color, unless we know we "want" color)
case "$TERM" in
    xterm-color|*-256color) color_prompt=yes;;
esac

# uncomment for a colored prompt, if the terminal has the capability; turned
# off by default to not distract the user: the focus in a terminal window
# should be on the output of commands, not on the prompt
force_color_prompt=yes

if [ -n "$force_color_prompt" ]; then
    if [ -x /usr/bin/tput ] && tput setaf 1 >&/dev/null; then
	# We have color support; assume it's compliant with Ecma-48
	# (ISO/IEC-6429). (Lack of such support is extremely rare, and such
	# a case would tend to support setf rather than setaf.)
	color_prompt=yes
    else
	color_prompt=
    fi
fi

if [ "$color_prompt" = yes ]; then
    PS1='${debian_chroot:+($debian_chroot)}\[\033[01;32m\]\u@\h\[\033[00m\]:\[\033[01;34m\]\w\[\033[00m\]\$ '
else
    PS1='${debian_chroot:+($debian_chroot)}\u@\h:\w\$ '
fi
unset color_prompt force_color_prompt

# If this is an xterm set the title to user@host:dir
case "$TERM" in
xterm*|rxvt*)
    PS1="\[\e]0;${debian_chroot:+($debian_chroot)}\u@\h: \w\a\]$PS1"
    ;;
*)
    ;;
esac

# enable color support of ls and also add handy aliases
if [ -x /usr/bin/dircolors ]; then
    test -r ~/.dircolors && eval "$(dircolors -b ~/.dircolors)" || eval "$(dircolors -b)"
    alias ls='ls --color=auto'
    #alias dir='dir --color=auto'
    #alias vdir='vdir --color=auto'

    alias grep='grep --color=auto'
    alias fgrep='fgrep --color=auto'
    alias egrep='egrep --color=auto'
fi

# colored GCC warnings and errors
#export GCC_COLORS='error=01;31:warning=01;35:note=01;36:caret=01;32:locus=01:quote=01'

# some more ls aliases
alias ll='ls -alF'
alias la='ls -A'
alias l='ls -CF'

# Add an "alert" alias for long running commands.  Use like so:
#   sleep 10; alert
alias alert='notify-send --urgency=low -i "$([ $? = 0 ] && echo terminal || echo error)" "$(history|tail -n1|sed -e '\''s/^\s*[0-9]\+\s*//;s/[;&|]\s*alert$//'\'')"'

# Alias definitions.
# You may want to put all your additions into a separate file like
# ~/.bash_aliases, instead of adding them here directly.
# See /usr/share/doc/bash-doc/examples in the bash-doc package.

if [ -f ~/.bash_aliases ]; then
    . ~/.bash_aliases
fi
# enable programmable completion features (you don't need to enable
# this, if it's already enabled in /etc/bash.bashrc and /etc/profile
# sources /etc/bash.bashrc).
if ! shopt -oq posix; then
  if [ -f /usr/share/bash-completion/bash_completion ]; then
    . /usr/share/bash-completion/bash_completion
  elif [ -f /etc/bash_completion ]; then
    . /etc/bash_completion
  fi
fi

export NVM_DIR="$HOME/.nvm"
[ -s "$NVM_DIR/nvm.sh" ] && . "$NVM_DIR/nvm.sh"

# Node Environment Setup

Answer 1

ln -s "$(which node)" /usr/local/bin/node

该命令将从您安装的当前节点版本创建符号链接。如果已存在 /usr/local/bin/node 文件，请将其删除，因为它可能是损坏的链接。

还可以将“编辑配置”从您必须的任何项目版本更改为“节点”（这将是使用上述命令创建的链接）

Answer 2

添加 nvm 节点解释器对我有用：

设置 -> 语言和框架 -> Node.js 和 NPM -> 节点解释器

选择了~/.nvm/current/bin/node。如果它没有显示在解释器选择中，请单击...并将其添加为新路径。

Answer 3

这为我修好了:

https://intellij-support.jetbrains.com/hc/en-us/community/posts/205964744/comments/205060164

只需编辑您的Intellij启动器/启动脚本并将其更改为 /bin/bash -i -c <path to ide.sh>

Answer 4

对我来说，解决方案是将以下行从~/.bashrc移至~/.profile并重新启动/重新登录。

export NVM_DIR="$HOME/.nvm"
[ -s "$NVM_DIR/nvm.sh" ] && \. "$NVM_DIR/nvm.sh" # This loads nvm

Answer 5

Idea终端默认情况下会启动登录Shell，因此不会读取我的.bashrc文件。

我可以通过转到“设置”解决问题。然后，在左侧面板中展开“工具”，然后单击“终端”。将-i添加到您的Shell路径。（例如/ bin / bash -i）

Answer 6

我在 Ubuntu 上运行并且遇到了同样的问题，无法从 IntelliJ Idea 终端运行 node 或无法运行启动 nvm 相关进程的 gradle 任务。

在 Idea 中使用终端时，一些现有的答案为我修复了它，但运行 gradle 任务仍然不起作用。用 bash -l -c... 启动它，如在其他地方发现的那样也不起作用。

最初通过创建一个与 nvm 所做的相同的启动脚本来解决它，然后 bash -l -c...更简单......所以我的 .desktop exec 输入行现在是：

Exec=/bin/bash -i -c /opt/intellij/idea-IU/bin/idea.sh "%f"

只是在此处提及它，因为已接受的解决方案不适用于从 Idea 中启动与 nvm 相关的 gradle 任务。