node --eval "require('./')"

[Mithgol]

Test the node --eval "require('./')" problem for #39.

[Mithgol]

Node.js v0.10.26 on Windows 7 Professional Service Pack 1:

It seems that a failure in require(…) (when the given module does not exist) is caught successfully.

A couple of other tests are necessary for the node --eval "require('./')" solution:

• an existing (but erroneous) module — REPL is probably not suitable for testing if REPL is too greedy in trying to catch syntax errors
• what happens on non-Windows systems (especially on Travis)

[Mithgol]

First test passed. REPL does not seem to interfere.

[springmeyer]

maybe using vm to try to require directly would be more consistent/robust than the repl?

[Mithgol]

If REPL were to interfere (for example, if REPL were catching errors to display them as ... in its console instead of letting them to be passed to my callback), then yes.

However, REPL does not seem to interfere. The error happens and is passed to my callback.

And I do not intend to use REPL in the node-pre-gyp module. I only needed REPL to run some code to test the require's behaviour in a child process.