That sounds like a job for cjs-module-lexer, which is vendored in node already, maybe we could consider making it publicly available?

I don't think cjs-module-lexer would help my use case as it appears to merely parse source code to find out what's attached to module.exports. I need my "super module" to be able to export the actual values, which requires evaluation of the source code.

Here's a simple example of more or less what I'm currently having to do:

'use strict';

const Module = require('module');

function load(filename, content) {
  const mod = new Module(filename, module);

  // This is my "problem". I'd much rather have `mod.compile(content, filename);`
  mod._compile(content, filename);

  return mod.exports;
}

module.exports = {
  foo: load('foo.js', '/* foo.js raw contents here */'),
  bar: load('bar.js', '/* bar.js raw contents here */'),
  // ...
};

If we want to expose this publicly, maybe we should design a slightly better API?

Personally I'm perfectly fine with the API as-is, it's flexible enough and isn't complicated.

There has been no activity on this feature request for 5 months and it is unlikely to be implemented. It will be closed 6 months after the last non-automated comment.

For more information on how the project manages feature requests, please consult the feature request management document.

Would anyone be opposed to me just renaming ._compile to .compile and making ._compile an alias?

I would be opposed. I'd much prefer a single new function exported from 'module'.

@targos Suggestions then?

To be improved:

const { createCommonJSModule } = require('module');

const myModule = createCommonJSModule({
  filename: 'myModule.js',
  parent: module,
  code: `
    exports.value = 42;
  `
});

console.log(myModule.exports.value) // 42

There has been no activity on this feature request for 5 months and it is unlikely to be implemented. It will be closed 6 months after the last non-automated comment.

For more information on how the project manages feature requests, please consult the feature request management document.

unstale por favor

There has been no activity on this feature request for 5 months and it is unlikely to be implemented. It will be closed 6 months after the last non-automated comment.

For more information on how the project manages feature requests, please consult the feature request management document.

unstale por favor