安装Hyperledger Fabric SDK REST服务器时遇npm link执行错误

Hey there, let’s break down why you’re hitting issues with npm link in the loopback-connector-fabric directory. I’ve run into similar snags with Hyperledger Fabric tooling before, so here are the most likely culprits and fixes:

• Permission Conflicts (Even with sudo)
  Ubuntu 16.04’s default npm setup stores global packages in system-owned directories like /usr/local/lib/node_modules. Using sudo npm link can mess up file ownership—creating a cycle where non-sudo commands fail later, and sudo commands don’t play nice with user-owned files.
  Fix: Switch to a user-level npm prefix to avoid permission fights entirely:

  mkdir -p ~/.npm-global
  npm config set prefix '~/.npm-global'
  echo 'export PATH=~/.npm-global/bin:$PATH' >> ~/.profile
  source ~/.profile
  

  Now run npm link again without sudo—all npm files will live in your user directory, no more permission errors.

• Corrupted or Incomplete Dependencies
  Even if you installed prerequisites, nested dependencies in loopback-connector-fabric might have failed to install properly, breaking the link process.
  Fix:

  1. Navigate to the packages/loopback-connector-fabric directory.
  2. Wipe existing dependencies and lock files:

     rm -rf node_modules package-lock.json
     

  3. Reinstall cleanly:

     npm install
     

  4. Try npm link again once the install finishes.

• Node.js Version Mismatch
  Ubuntu 16.04 ships with an outdated Node.js version (usually v4 or v6), but Hyperledger Fabric SDKs typically require v10 or v12 (check your specific SDK version’s docs for exact requirements). A version mismatch can cause obscure link errors.
  Fix: Use nvm (Node Version Manager) to install a compatible version:

  curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.39.7/install.sh | bash
  source ~/.bashrc
  nvm install 12  # Replace with the version your SDK requires
  nvm use 12
  

  Verify with node -v and npm -v, then retry npm link.

• Uninitialized Git Submodules
  The fabric-sdk-rest repo might include submodules that weren’t cloned with your initial git clone. Missing submodules can break the connector’s dependency chain.
  Fix:

  1. Go back to the root of your fabric-sdk-rest repo.
  2. Initialize and update all submodules recursively:

     git submodule init
     git submodule update --recursive
     

  3. Return to the loopback-connector-fabric directory and try npm link again.

• Missing Loopback CLI
  npm link for Loopback connectors often requires the Loopback CLI tool to be installed globally. If it’s missing, the link command can fail without clear feedback.
  Fix: Install the CLI globally (using your user-level prefix from the first fix):

  npm install -g loopback-cli
  

  Then retry npm link.

内容的提问来源于stack exchange，提问作者Anton K