Browserify模块查找路径异常，浏览器端Imgur模块构建问题求助

Looks like you're hitting a path resolution bug caused by a mix of global and local dependencies, or an outdated version of the http-signature package that's incorrectly concatenating absolute paths as relative ones. Here are actionable fixes to resolve this:

1. Clean and Reinstall Local Dependencies #

First, eliminate any corrupted or cross-path dependency references:

• Delete your project's node_modules folder, plus package-lock.json (if using npm) or yarn.lock (if using Yarn).
• Run npm install or yarn install to pull fresh, local copies of all dependencies. This ensures your project isn't trying to reference global packages from a different drive letter, which is likely the root cause of the wonky ./C:/... path.

2. Update or Pin the http-signature Package #

The error originates in http-signature, so targeting this dependency directly can help:

• Try upgrading to the latest version with:

  npm update http-signature
  # Or for Yarn:
  yarn upgrade http-signature
  

• If upgrading doesn't work, force a correct version of is-buffer (the missing module) using resolutions in your package.json (works with Yarn and npm >=8.3):

  "resolutions": {
    "http-signature/is-buffer": "^2.0.5"
  }
  

  Run your install command again after adding this to apply the fix.

3. Avoid Global Dependencies in Local Projects #

Make sure you're not relying on globally installed packages for your local project:

• If you installed imgur globally before, uninstall it with npm uninstall -g imgur or yarn global remove imgur, then install it locally with npm install imgur or yarn add imgur. Global packages on a different drive will almost always cause path resolution issues like this.

4. Adjust Bundler Configuration (Browser-Side Specific) #

Since you're building for the browser, double-check your bundler (Webpack, Vite, etc.) settings to prioritize local module resolution:

• For Webpack, add or tweak the resolve section in your webpack.config.js:

  module.exports = {
    resolve: {
      modules: ['node_modules'],
      preferRelative: true // Ensures relative paths resolve correctly against local node_modules
    }
  };
  

  This forces your bundler to look for modules in your project's local node_modules first, preventing incorrect cross-drive path references.

After trying these steps, verify the fix by checking the http-signature/lib files in your local node_modules—the require statement for is-buffer should be a simple require('is-buffer'), not a mangled absolute path.

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