We shouldn't rely on the existence of "module.paths" (Meteor)

[apendua]

According to CommonJS specs, the paths property is optional. Depending on its existence, e.g.

https://github.com/mochajs/mocha/blob/master/lib/mocha.js#L28

may cause unnecessary runtime errors, for example:

benjamn/install#9

We should probably test against the property existence before modifying module.paths.

[boneskull]

In this case, I think we can try / catch some require() statements when loading local UIs and reporters.

[ematipico]

Hi, is there any movement around this?
At the moment this is causing an issue. I am running mocha in a bundled file (I packed mocha using rollup) to be executed in a serverless environment.

I get an error in the following snippet:

if (!process.browser) {
  var cwd = process.cwd();
  module.paths.push(cwd, path$2.join(cwd, 'node_modules')); // <= here
}

module.paths doesn't exists.

[boneskull]

Does the serverless environment not support module.paths?

As this is marked help wanted, if a contributor can find an alternative, we’d accept a PR to address.

[ematipico]

I take a guess: could it be empty because there's no node_modules folder? As I bundled everything, I don't use the folder.

Would bypassing that lines of code break the framework? I could help if pointed to the right direction