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

Author	SHA1	Message	Date
isaacs	47f3fc9a26	test: add module-loading test with empty string	12 years ago
Felix Böhm	7465cf911a	module: assert that require() is called with a string as requested in #4577	12 years ago
Bert Belder	b27a4cbe2a	test-module-loading: convert backslashes to forward slashes This makes the test pass on Windows.	13 years ago
isaacs	a10cfba766	module: remove 'exited', replace 'children' array	13 years ago
Igor Zinkovsky	7335a4234a	fix test-module-loading on windows	13 years ago
Ryan Dahl	850609ea2d	Remove separation of libuv tests	13 years ago
Ben Noordhuis	018e110cd1	test: replace .addListener() calls with .on()	13 years ago
Colton Baker	87286cc737	Fixed a lot of jslint errors. Fixes #1831	13 years ago
Ryan Dahl	4e1d6fca8e	Mark tests which are broken in libuv	13 years ago
Ben Noordhuis	ac722bbed6	module: strip byte order marker when loading .js and .json files BOMs make V8 raise a 'SyntaxError: Unexpected token ILLEGAL' exception. Fixes #1440.	13 years ago
isaacs	703a1ffe52	Revert "AMD compatibility for node" This reverts commit `9967c369c9`. Conflicts: test/simple/test-module-loading.js	13 years ago
isaacs	588d885e81	Close #1357 Load json files with require() Signed off by everybody.	13 years ago
isaacs	7f0047c2d5	Close #1348 Remove require.paths Module.globalPaths is still set to a read-only copy of the global include paths pulled off of the NODE_PATH environment variable. It's important to be able to inspect this, but modifying it no longer has any effect.	13 years ago
isaacs	9b5098f509	Close #1281 Make require a public member of module Reviewed by @felixge	13 years ago
isaacs	9967c369c9	AMD compatibility for node, with docs and tests Closes #1173 Closes #1170	14 years ago
Ryan Dahl	55048cdf79	Update copyright headers	14 years ago
isaacs	f8defa3e09	package.json main as indexed subdir Closes GH-686.	14 years ago
isaacs	46513483cd	node_modules module lookup, +docs and test.	14 years ago
isaacs	da2f4b2dc4	support for package.json This adds basic support for situations where there is a package.json with a "main" field. That "main" module is used as the code that is loaded when the package folder is required.	14 years ago
isaacs	f86ec1366f	Closes GH-619 Make require.main be the main module	14 years ago
Ryan Dahl	fbb74784b5	Remove more process.assert	14 years ago
isaacs	6cdeb3b3fd	A module ID with a trailing slash must be a dir. require('./foo/') should not try to load './foo.js'. It should only look for ./foo/index.js Closes GH-588	14 years ago
Oleg Efimov	0ce9cbab29	GJSLint continue	14 years ago
Ryan Dahl	a0159b4b29	Fix global leaks	14 years ago
Anders Conbere	c4f8f871c9	adding module tests for .js and bare files Currently the module tests don't cover the cases for when a user requires a file with a request that includes the extension, and for a request to a file with no extensions. ex. require("./a.js") // not tested require("./foo") // (not tested with trying to load a file named ./foo)	14 years ago
isaacs	dff1b5ad10	Don't try to run extension loaders unless they're actually functions	14 years ago
Tim-Smart	0f16af7ee4	Remove registerExtension, add .extensions. Tests. Updated extensions tests	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
Herbert Vojčík	9253333850	Fix registerExtension for NODE_MODULE_CONTEXTS Fix of registerExtension-produced non-string module loading with own context. Plus finishing touches to the test.	14 years ago
Herbert Vojčík	cf2b206a8e	More changes to tests so they really work under context module loader. Plus, getting rid of test/common.js defining things in global.	14 years ago
Ryan Dahl	03123435e0	Remove platform specific asserts	14 years ago
Nick Stenning	0a3eff8021	Standardise module load order for native and registered file extensions. This patch standardises the load order for modules. Highest priority is trying to load exactly the file the user specified, followed by native extensions, followed by registered extra extensions, etc. In full, if we require('foo') having registered '.coffee' as an alternative extension, we try and load the following files in order: foo foo.js foo.node foo.coffee foo/index.js foo/index.node foo/index.coffee	14 years ago
Nick Stenning	78520ba482	Don't attempt to load a directory. This patch replaces the path.exists check for module loading with a call to fs.statSync (or fs.stat for require.async) which ensures that it's not trying to load a directory.	14 years ago
isaacs	d75b63bc3c	Support including modules that don't have an extension. This way, require("/foo") will work if there is a "foo.js", or a file named simply "foo" with no extension.	14 years ago
isaacs	49e0f14a2f	Cache modules based on filename rather than ID This is ever so slightly less efficient than caching based on ID, since the filename has to be looked up before we can check the cache. However, it's the most minimal approach possible to get this change in place. Since require() is a blocking startup-time operation anyway, a bit of slowness is not a huge problem. A test involving require.paths modification and absolute loading. Here's the gist of it. Files: /p1/foo.js /p2/foo.js 1. Add "/p1" to require.paths. 2. foo1 = require("foo") 3. assert foo1 === require("/p1/foo") (fail) 4. Remove /p1 from require.paths. 5. Add /p2 to require.paths. 6. foo2 = require("foo") 7. assert foo1 !== foo2 (fail) 8. assert foo2 === require("/p2/foo") (fail) It's an edge case, but it affects how dependencies are mapped by npm. If your module requires foo-1.2.3, and my module requires foo-2.3.4, then you should expect to have require("foo") give you foo-1.2.3, and I should expect require("foo") to give me foo-2.3.4. However, with module ID based caching, if your code loads first, then your "foo" is THE "foo", so I'll get your version instead of mine. It hasn't yet been a problem, but only because there are so few modules, and everyone pretty much uses the latest version all the time. But as things start to get to the 1.x and 2.x versions, it'll be an issue, I'm sure. Dependency hell isn't fun, so this is a way to avoid it before it strikes.	15 years ago
Ryan Dahl	9fd5e3c89c	Update tests to work with module contexts	15 years ago
David Siegel	2085909aeb	fix corner-case bug in Module and added a test to expose it	15 years ago
Ryan Dahl	ba792ea202	:%s/sys.puts/console.log/g and there was much rejoicing	15 years ago
Herbert Vojcik	c16508c87a	Better require.async throw test	15 years ago
Herbert Vojcik	d36bb6536e	Better require.async tests	15 years ago
Tim-Smart	0c17067d87	Add require.registerExtension	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
Ryan Dahl	ef55324f1a	Do not use Promise in 'fs' module	15 years ago
Felix Geisendörfer	211e82e8d9	Simple test case for require.async() This is to make sure this doesn't break after implementing the new truly sync require() function.	15 years ago
Felix Geisendörfer	b02b54e003	Fix: Module cache did not propagate This patch makes sure nested modules are available in their parents cache. The module simplification broke this behavior. See: http://groups.google.com/group/nodejs/browse_thread/thread/e875132469547d2 `b73f61a137`	15 years ago
Felix Geisendörfer	b73f61a137	Simplified module system createModule got removed as it was unnecessary and caused issues by doing its own cache checks independent of loadModule. Internal modules are now the only globally cached modules, all other modules are only cached by inheriting their parent modules cache. Credits: Module specific cache and a few other diffs by Blaine Cook `431662d25c` http://romeda.org/blog/2010/01/hot-code-loading-in-nodejs.html http://thread.gmane.org/gmane.comp.lang.javascript.nodejs/1994	15 years ago
Felix Geisendörfer	a76c7a89ce	Implemented __dirname It seems that the current __filename module global is mainly used to determine the directory the current module is in. To make that easier, this patch adds support for a __dirname module global directly.	15 years ago
isaacs	4dcdfaf929	Fix require("../blah") issues Added some more tests, and refactored the uri and path modules to use the same normalization logic, so that nothing is relying on flaky regexps. http://groups.google.com/group/nodejs/browse_thread/thread/34779f8c10098c5e http://groups.google.com/group/nodejs/browse_thread/thread/1aa0146b92582679#msg_9822c03998cb4064	15 years ago