node/test/message/undefined_reference_in_new_...

before

node.js:*
    throw e; // process.nextTick error, or 'error' event on first tick
    ^
ReferenceError: foo is not defined
    at evalmachine.<anonymous>:*
    at *test/message/undefined_reference_in_new_context.js:*
    at Module._compile (node.js:*)
    at Object..js (node.js:*)
    at Module.load (node.js:*)
    at Array.<anonymous> (node.js:*)
    at EventEmitter._tickCallback (node.js:*)
script.runIn*Context not throwing errors properly. 15 years ago			`before`

Fix: uncaughtException was broken for main module See: http://github.com/ry/node/commit/635986e4338cf34cf8e1abc4343ffd69d109bb4e 14 years ago			`node.js:*`
Report "weird" errors a little better. There are a few kinds of errors that are very confusing. 1. Errors raised in nextTick 2. Errors emitted on the "error" event 3. RangeErrors that crash the program (or anything without a stack trace) Long traces will make make these better, of course. In the meantime, this adds a few handy signposts (in the form of better error reporting and comments on the otherwise inscrutable code printed to the terminal) that can help new users find the cause, or at least, ask for help more effectively. 14 years ago			`throw e; // process.nextTick error, or 'error' event on first tick`
Fix: uncaughtException was broken for main module See: http://github.com/ry/node/commit/635986e4338cf34cf8e1abc4343ffd69d109bb4e 14 years ago			`^`
script.runIn*Context not throwing errors properly. 15 years ago			`ReferenceError: foo is not defined`
Fix undefined_reference_in_new_context test 15 years ago			`at evalmachine.<anonymous>:*`
Fix undefined_reference_in_new_context test for own-context module loader. 14 years ago			`at test/message/undefined_reference_in_new_context.js:`
Remove module.js - put code into src/node.js 14 years ago			`at Module._compile (node.js:*)`
Fix test/message/undefined_reference_in_new_context 14 years ago			`at Object..js (node.js:*)`
Remove require.async This patch removes require.async from nodejs. 1. It complicated the code unnecessarily. 2. Everyone uses sync require anyway. 3. It's got a lot of weird edge cases when mixed with sync require. 4. It is many months behind the commonjs spec anyhow. 14 years ago			`at Module.load (node.js:*)`
Fix: uncaughtException was broken for main module See: http://github.com/ry/node/commit/635986e4338cf34cf8e1abc4343ffd69d109bb4e 14 years ago			`at Array.<anonymous> (node.js:*)`
			`at EventEmitter._tickCallback (node.js:*)`