lukechilds/node - node - Gitea: Git with a cup of tea

Commit Graph

Author	SHA1	Message	Date
isaacs	875e4a0c59	core: Remove the nextTick for running the main file Not necessary, since we can handle the error properly on the first tick now, even if there are event listeners, etc. Additionally, this removes the unnecessary "_needTickCallback" from startup, since Module.loadMain() will kick off a nextTick callback right after it runs the main module. Fix #4856	12 years ago
Trevor Norris	86c0745a5e	process: streamlining tick callback logic * Callbacks from spinner now calls its own function, separate from the tickCallback logic * MakeCallback will call a domain specific function if a domain is detected * _tickCallback assumes no domains, until nextTick receives a callback with a domain. After that _tickCallback is overridden with the domain specific implementation. * _needTickCallback runs in startup() instead of nextTick (isaacs) * Fix bug in _fatalException where exit would be called twice (isaacs) * Process.domain has a default value of null * Manually track nextTickQueue.length (will be useful later) * Update tests to reflect internal api changes	12 years ago
isaacs	dd85a8c183	Update message test for new v8 behavior	13 years ago
Bert Belder	0dba4ad0f9	tests: make all message tests pass on Windows	13 years ago
isaacs	e0f5d8e86d	test: v8 stack trace messages changed slightly	13 years ago
Felix Geisendörfer	bf9d8e9214	Fix exception output for module load exceptions So instead of: node.js:201 throw e; // process.nextTick error, or 'error' event on first tick ^ You will now see: path/to/foo.js:1 throw new Error('bar'); ^ This is a sub-set of isaacs patch here: https://github.com/joyent/node/issues/3235 The difference is that this patch purely adresses the exception output, but does not try to make any behavior changes / improvements.	13 years ago
Felix Geisendörfer	814033365b	Fix process.nextTick throw call sites This patch now reports the proper throw call site for exceptions triggered within process.nextTick. So instead of this: node.js:201 throw e; // process.nextTick error, or 'error' event on first tick ^ You will now see: mydir/myscript.js:15 throw new Error('My Error'); ^ From my testing this patch causes no performance regressions, but does greatly simplify processing the nextTickQueue.	13 years ago
isaacs	079b81358b	test: Minor change to message/undefined_reference_in_new_context	13 years ago
koichik	f5a01d1764	test: fix test/message/undefined_reference_in_new_context.js after `4d4900f`, stack trace was changed.	13 years ago
koichik	4662ace916	Fix message tests V8 3.4.12.1 changed exception log format. 3.14.10: node.js:189 throw e; // process.nextTick error, or 'error' event on first tick ^ 3.4.12.1: node.js:189 throw e; // process.nextTick error, or 'error' event on first tick ^ The caret was moved.	14 years ago
Ryan Dahl	72dd8778b9	Fix undefined_reference_in_new_context	14 years ago
Daniel Ennis	52f93185c7	Adding support for require-like initialization of node, so `node foo` will load one of: ./foo.js ./foo.node ./foo/index.js ./foo/index.node Test cases added. Ensured no conflict with native names.	14 years ago
Felix Geisendörfer	91cc2d8c4b	Restructure src/node.js startup code This patch introduces a logical structure and sequence for the bootstrap code found src/node.js.	14 years ago
Ryan Dahl	555184663a	windows compat: undefined_reference_in_new_context test	14 years ago
Felix Geisendörfer	5a49f96505	Move commonjs module system into lib/module.js This de-couples NativeModule from the module system and completes the main objective of this refactoring.	14 years ago
Ryan Dahl	d3532a4bf2	Fix indention in 'make test-message'	14 years ago
Ryan Dahl	c7b24efd21	Move ev_loop out of javascript	14 years ago
Jorge Chamorro Bieling	99e19aa398	Remove unneeded function wrappers	14 years ago
isaacs	e9b6b0b327	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
Ryan Dahl	1b1bee8099	Fix test/message/undefined_reference_in_new_context	14 years ago
isaacs	bb08f0c219	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
Felix Geisendörfer	ef54777fa5	Fix: uncaughtException was broken for main module See: `635986e433`	15 years ago
Herbert Vojčík	28b21d15c3	Fix undefined_reference_in_new_context test for own-context module loader.	15 years ago
Ryan Dahl	d408de87fc	Remove module.js - put code into src/node.js	15 years ago
Ryan Dahl	9fd5e3c89c	Update tests to work with module contexts	15 years ago
Ryan Dahl	82ce3481fe	Fix undefined_reference_in_new_context test	15 years ago
Ryan Dahl	ba792ea202	:%s/sys.puts/console.log/g and there was much rejoicing	15 years ago
Ryan Dahl	b93faf9afa	Comment out lines with full paths in message test. Note that * in the .out files is a special wildcard.	15 years ago
Ryan Dahl	f1a4f17897	script.runIn*Context not throwing errors properly.	15 years ago

30 Commits (0604d9ab93311212b3f8bc3526c3c711ee7dc165)