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

Author	SHA1	Message	Date
Rich Trott	a030c5cf49	test: remove unused assert module imports Many test modules load assert but do not use it. This change removes those instances. It also removes a handful of other unused variables when they were nearby. PR-URL: https://github.com/nodejs/node/pull/4438 Reviewed-By: Michaël Zasso <mic.besace@gmail.com> Reviewed-By: Brian White <mscdex@mscdex.net> Reviewed-By: Colin Ihrig <cjihrig@gmail.com>	9 years ago
Michaël Zasso	2235fad11b	test: remove unreachable code There is no way a line can be called after throwing an exception. PR-URL: https://github.com/nodejs/node/pull/2289 Reviewed-By: Sakthipriyan Vairamani <thechargingvolcano@gmail.com> Reviewed-By: Roman Reiss <me@silverwind.io> Reviewed-By: Brendan Ashworth <brendan.ashworth@me.com>	10 years ago
Roman Reiss	f29762f4dd	test: enable linting for tests Enable linting for the test directory. A number of changes was made so all tests conform the current rules used by lib and src directories. The only exception for tests is that unreachable (dead) code is allowed. test-fs-non-number-arguments-throw had to be excluded from the changes because of a weird issue on Windows CI. PR-URL: https://github.com/nodejs/io.js/pull/1721 Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl>	10 years ago
Ben Noordhuis	635337f953	test: fix message tests regression Commit `3e1b1dd` ("Remove excessive copyright/license boilerplate") broke some of the message tests because without the license boilerplate at the top, the line numbers no longer match up. PR-URL: https://github.com/iojs/io.js/pull/316 Reviewed-By: Bert Belder <bertbelder@gmail.com>	10 years ago
Fedor Indutny	f1de13b8ab	node: do not print SyntaxError hints to stderr Try embedding the ` ... ^` lines inside the `SyntaxError` (or any other native error) object before giving up and printing them to the stderr. fix #6920 fix #1310	11 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.	14 years ago
isaacs	8df6f9e544	Close #974 Properly report traceless errors. Also, tests for the same.	14 years ago