如何配置RequireJS使其默认检索node_modules中的模块？

Got it, let's tackle this RequireJS + node_modules issue you're hitting. The problem is that RequireJS doesn't automatically look in node_modules by default—it only searches the baseUrl and paths you explicitly configure. Here's how to fix it step by step:

1. Basic Path Mapping (Individual Modules) #

The simplest approach is to define explicit paths for each module you need from node_modules. This works great if you're only using a handful of modules.

First, make sure your RequireJS configuration sets a clear baseUrl (usually your web root or a dedicated js folder). Then map each module to its location in node_modules:

requirejs.config({
  baseUrl: '/', // Web root directory (adjust if your JS lives in a subfolder like /js)
  paths: {
    // Map module names to their actual files in node_modules
    'lodash': 'node_modules/lodash/lodash',
    'axios': 'node_modules/axios/dist/axios',
    // Add your own UMD module here too, if it's in node_modules
    'my-umd-module': 'node_modules/my-umd-module/dist/my-umd-module'
  }
});

// Now you can require these modules normally
require(['lodash', 'my-umd-module'], function(_, myModule) {
  // Use your modules here
});

2. Generic Mapping (All Unconfigured Modules) #

If you're using lots of modules from node_modules and don't want to map each one individually, use a wildcard path to tell RequireJS to fall back to node_modules for any unrecognized module ID:

requirejs.config({
  baseUrl: '/',
  paths: {
    // For any module not explicitly mapped, check node_modules first
    '*': 'node_modules/*'
  }
});

// Now you can require modules directly without pre-mapping
require(['moment'], function(moment) {
  console.log(moment().format());
});

⚠️ Note: This works best for modules where the main entry file matches the module name (or is index.js in the module root). For modules with non-standard entry points (like those that store their build in a dist folder), you'll still need an explicit path mapping.

3. Handle Modules with Non-Standard Entry Points #

Some modules don't expose their main file at the root of their node_modules folder (e.g., they use a dist or lib directory). For these, use the packages configuration to specify the module's location and main entry file:

requirejs.config({
  baseUrl: '/',
  packages: [
    {
      name: 'some-module', // The name you'll use to require it
      location: 'node_modules/some-module', // The folder in node_modules
      main: 'dist/some-module.min' // Path to the main entry file relative to location
    }
  ]
});

Critical Server Configuration Check #

Even with the right RequireJS setup, you'll get 404s if your web server isn't serving files from the node_modules directory. Make sure:

• The node_modules folder is inside your web server's document root (or you've configured the server to serve it as static content).
• For example, if you're using Express.js, add this line to expose node_modules:

  app.use(express.static('node_modules'));
  

Bonus: Optimize for Production #

While this setup works for development, in production you'll want to bundle your modules (using tools like RequireJS Optimizer, Webpack, or Rollup) to reduce HTTP requests. But for development, the above configurations will get you up and running.

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