File Structure: Requiring Sub-Modules in Node.js

Question

I have the following Node.js module/npm package:

|- dist/
|- - requirejs/
|- - - [stuff in amd pattern ...]
|- - node/
|- - - index.js
|- - - submodules/
|- - - - submodule1.js
|- - - - [submodule2.js etc.]
|- package.json
|- README.md

I can require dist/node/index.js via the module name (because I set it as the main entry-point file in package.json) like so:

var myModule = require('myModule');

I would like to require the submodule (as in AMD pattern) by doing so:

var mySubmodule = require('myModule/submodules/submodule1');

This throws an error in Node.js. The problem is, that Node.js requires the main file from its dist/node/ subdirectory but still keeps the modules root as the working directory.

Assuming the following structure would be present:

|- dist/
|- - node/
|- - - index.js
|- submodules/
|- - submodule1.js
|- package.json
|- README.md

Now doing require('myModule/submodules/submodule1') would work.

NOW THE QUESTION: Is there any setting/config to set the "module namespace" or working directory to the directory where the main file is in, or do I really need to put the submodules folder into the project root, to make it accessible without doing require('myModule/dist/node/submodules/submodule1')?

Crogo · Accepted Answer · 2015-09-09 13:28:09Z

10

Short answer: you can't.

Long answer: You should either directly use the second directory structure you proposed (/myModule/submodules/) or add some kind of API to your main exports (index.js) to quickly get the desired module.

While you can technically call require('myModule/some/complex/path'), the Node.js / npm packages standard is to rely on the unique interface provided by require('myModule').

// /dist/node/index.js
var path = require('path');
exports.require = function (name) {
  return require(path.join(__dirname, name));
};

Then in your app:

var myModule = require('myModule');
var submodule1 = myModule.require('submodules/submodule1');

answered Sep 9, 2015 at 13:28

Crogo

4934 silver badges8 bronze badges

Sign up to request clarification or add additional context in comments.

2 Comments

2778 Over a year ago

require('myModule') does not return a module object (or maybe at least not anymore)

hippietrail Over a year ago

At least require('fs/promises') has now become a canonical "my/complex/path"

Remirror · Accepted Answer · 2020-09-24 08:05:42Z

0

You now can do something like this using the exports feature of Node.

answered Sep 24, 2020 at 8:05

Remirror

7747 silver badges18 bronze badges

Collectives™ on Stack Overflow

File Structure: Requiring Sub-Modules in Node.js

2 Answers 2

2 Comments

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

2 Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Related