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

Author	SHA1	Message	Date
Ben Noordhuis	2c6f79c08c	src: don't error at startup when cwd doesn't exist The current working directory may not exist when iojs starts up. Don't treat that as an error because it's still possible to do many useful things, like evaluating a command line script or starting a REPL. This commit also fixes an age-old Windows bug where process.argv[0] was not properly expanded, that's why the parallel/test-process-argv-0 test gets an update as well. Fixes: https://github.com/iojs/io.js/issues/1184 PR-URL: https://github.com/iojs/io.js/pull/1194 Reviewed-By: Johan Bergström <bugs@bergstroem.nu> Reviewed-By: Rod Vagg <rod@vagg.org>	10 years ago
isaacs	3e1b1dd4a9	Remove excessive copyright/license boilerplate The copyright and license notice is already in the LICENSE file. There is no justifiable reason to also require that it be included in every file, since the individual files are not individually distributed except as part of the entire package.	10 years ago
Ben Noordhuis	f17f473af5	build: rename binary from node to iojs * rename the build targets * update the test runner to use `out/{Debug,Release}/iojs` * update the installer to install the iojs binary * update one test that explicitly checks for the binary name PR-URL: https://github.com/iojs/io.js/pull/262 Reviewed-By: Bert Belder <bertbelder@gmail.com>	10 years ago
Fedor Indutny	0e19476595	test: split test in parallel/sequential Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl> PR-URL: https://github.com/iojs/io.js/pull/172 Fix: iojs/io.js#139	10 years ago
Igor Zinkovsky	9ea5a4c468	fix simple/test-process-argv-0 on windows	13 years ago
isaacs	29463cb60c	Update argv0 test to verify correct behavior	13 years ago
Maciej Małecki	b73ec84ce1	test: test for `process.argv[0]` correctness joyent/node@b0c15412270f32e00c268c578f07a1ed032323f5 introduced a regression causing `process.argv[0]` to be invalid in node processes spawned from `PATH` (without explicit path to executable file - for example when using global node installation). Instead of finding a correct path to the executable, `process.cwd()` would be prepended to `process.argv[0]`.	13 years ago
Ryan Dahl	850609ea2d	Remove separation of libuv tests	13 years ago
Ryan Dahl	4e1d6fca8e	Mark tests which are broken in libuv	14 years ago
koichik	d6ec8f668e	Fix -e/--eval can't load module from node_modules With -e or --eval, require() can load module using relative path. node -e 'require("./foo")' But it can't load module from node_modules directory. node -e 'require("foo")' Fixes #1196.	14 years ago
Ryan Dahl	55048cdf79	Update copyright headers	14 years ago
Oleg Efimov	0665f0271e	GJSLint all simple tests exclude http-*, url, path	14 years ago
Ryan Dahl	a0159b4b29	Fix global leaks	14 years ago
Oleg Efimov	c0d69a4883	GJSLint part of tests	14 years ago
Ryan Dahl	9fd5e3c89c	Update tests to work with module contexts	15 years ago
isaacs	5861db8a69	Remove process.mixin dependency from all tests.	15 years ago
Felix Geisendörfer	44dde5f24c	Remove fs/path globals from test suite It is way too easy to not notice bugs due to those modules being exported as globals while running the test suite. See: http://github.com/ry/node/issues#issue/75	15 years ago
arlolra	04fac19822	Split tests.	15 years ago