v 1.0.0 fails with missing dependencies, see example with graceful-fs

[robrich]

https://github.com/robrich/sandboxed-module-graceful-fs is a project showing how v. 1.0.0 fails with ENOENT, no such file or directory 'path/to/this/project/constants' on [line 262 of sandboxed_module.js] when dependencies don't exist. v. 0.3.0 didn't have this concern.

[domenic]

Hmm interesting. There were a lot of changes. Hope it's an easy fix. Pull request would be much appreciated...

It might be just that we're missing constants from the list of built-in modules. If you're up for testing that fix it might be an easy PR.

[robrich]

Similar issue posted to graceful-fs: isaacs/node-graceful-fs#29

[robrich]

I haven't found any documentation on a native constants module, though because normal resolve doesn't die, I'm quite curious.

[robrich]

Wow, that's a bunny trail.

• http://nodejs.org/api/modules.html#modules_core_modules just says "described elsewhere in this documentation" and "in the lib/ folder" -- how vague.
• https://github.com/joyent/node/blob/master/lib/repl.js#L72-L76 lists modules added automatically to the REPL. This list looks very similar to https://github.com/felixge/node-sandboxed-module/blob/master/lib/sandboxed_module.js#L11-L14. Sadly, this is not an exhaustive list of native modules.
• https://github.com/joyent/node/blob/master/src/node.js#L762 seems to be a descent built-in list of native modules

Based on that, check out #34 which asks Node for the list of native modules, and tests that we can SandboxedModule.require() a file that contains each one.