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

Author	SHA1	Message	Date
Trevor Norris	0bba590283	bindings: update api All compile time warnings about using deprecated APIs have been suppressed by updating node's API. Though there are still many function calls that can accept Isolate, and still need to be updated. node_isolate had to be added as an extern variable in node.h and node_object_wrap.h Also a couple small fixes for Error handling. Before v8 3.16.6 the error stack message was lazily written when it was needed, which allowed you to change the message after instantiation. Then the stack would be written with the new message the first time it was accessed. Though that has changed. Now it creates the stack message on instantiation. So setting a different message afterwards won't be displayed. This is not a complete fix for the problem. Getting error without any message isn't very useful.	12 years ago
Ben Noordhuis	51f6e6a9b3	src, test: downgrade to v8 3.14 api	12 years ago
Fedor Indutny	8a96bb42c6	test: make tests work with newer v8	12 years ago
isaacs	564172510d	Revert "test: stack overflow output" This reverts commit `f8519e10b8`. Recent update to V8 fixes the problem where it incorrectly reports the line number as 0 for thrown RangeErrors.	13 years ago
isaacs	f8519e10b8	test: stack overflow output	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
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.	13 years ago
isaacs	8df6f9e544	Close #974 Properly report traceless errors. Also, tests for the same.	14 years ago