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

Commit Graph

Author	SHA1	Message	Date
Sam Roberts	abe02553f2	doc: clarify Windows signal sending emulation	11 years ago
Sam Roberts	198ed0bd0d	doc: describe child_process.fork() silent option	11 years ago
Sam Roberts	549be1caa8	doc: child_process.execFile arguments are optional	11 years ago
isaacs	e7f7e2aeca	blog: TJ is the new node core project lead	11 years ago
Sam Roberts	7bd6e33318	doc: streams must be open to be passed to child spawn stdio options can be a 'stream', but the following code fails with "Incorrect value for stdio stream: [object Object]", despite being a stream. The problem is the test isn't really for a stream, its for an object with a numeric `.fd` property, and streams do not have an fd until their async 'open' event has occurred. This is reasonable, but was not documented. child_process.spawn('date', [], {stdio: [ 'ignore', fs.createWriteStream('out.txt',{flags:'a'}), 'ignore']})	11 years ago
gluxon	56913d2cde	doc: Fix argument typo in SimpleProtocol example	11 years ago
Lorenz Leutgeb	fc7e217a30	doc: fix typo in cluster page	11 years ago
Timothy J Fontaine	aa56d9d354	blog: Post for v0.11.10	11 years ago
Maciej Małecki	5a8de857f0	doc: document that `process.send` is synchronous Ref #2598	11 years ago
Timothy J Fontaine	ffb718b5a3	doc: clarify process on exit safe usage	11 years ago
Ron Korving	3917232030	docs: process.on('exit') receives exit code The fact that the "exit" event passes the exit code as an argument as omitted from the documentation. This adds the explanation and augments the example code to show that.	11 years ago
Dav Glass	34b9280da4	doc: Fix missing backtick in debugger doc	12 years ago
Timothy J Fontaine	f84c7a2776	blog: Post for v0.10.24	11 years ago
Timothy J Fontaine	7dca8d714f	blog: Post for v0.10.23	11 years ago
Nicolas Kaiser	4bc2ec90d7	doc: fix typos in node.1	11 years ago
Mathias Bynens	f89a7185b7	doc: mention `binary` as deafult for Hash strings	11 years ago
Gabriel Farrell	04d52270b6	doc: "finish" event is on the writable stream	11 years ago
Yazhong Liu	5cfee927cd	doc: mention execArgv in setupMaster	11 years ago
Fedor Indutny	796834bf18	doc: document 'error' event for stream.Writable fix #5255	11 years ago
isaacs	b371d4ae8f	blog: bnoordhuis departure	11 years ago
Yazhong Liu	bd7fa92de4	doc: list execArgv option for child_process.fork()	11 years ago
Gabriel Falkenberg	94c4ba9dd3	doc: change constant to consistent	11 years ago
Sam Roberts	8aac118b69	process: document kill(0), disallow kill(O_RDWR) The null signal test existed, but only tested the case where the target process existed, not when it did not exist. Also clarified that SIGUSR1 is reserved by Node.js only for receiveing, its not at all reserved when sending a signal with kill(). kill(pid, 'O_RDWR'), or any other node constant, "worked". I fixed this by also checking for 'SIG'. The same as done in the isSignal() function. Now the signal names supported by process.kill() are the same as those supported by process.on().	11 years ago
Yazhong Liu	fcfaa392ae	doc: net: fix typo in example code	11 years ago
Michael Ridgway	a32b8787a4	doc: http: document ServerResponse 'finish' event	11 years ago
Nikolai Vavilov	207a3e10f8	doc: http: properly document callback argument	11 years ago
isaacs	90655a998e	blog: npm outage postmortem	11 years ago
Linus Unnebäck	953d7184ec	doc: clarify child_process error behaviour Clarify that an 'error' event may or may not be followed by an 'exit' event and that it's not safe to make assumptions either way.	11 years ago
Timothy J Fontaine	a34bbaf31b	blog: Post for v0.11.9	11 years ago
Fedor Indutny	88dc1fcb62	crypto: `randomBytes` is non-blocking Add NOTE section in documentation, mentioning that `randomBytes` won't block when entropy sources are drained. fix #6372	11 years ago
Fedor Indutny	5885f464f0	net: fix `new net.Socket` documentation `Socket` no longer accepts `type` option, and also accepts `readable`, `writable` options. fix #6541	11 years ago
Ben Noordhuis	1394d5856b	doc: add nodejs.vn to community page Node.js. It's not just for SF hipsters anymore.	11 years ago
Ben Noordhuis	a763db8fc0	doc: sort community page links alphabetically This commit introduces some long lines but it's HTML so it's okay.	11 years ago
Timothy J Fontaine	ac9cf00252	blog: Post for v0.10.22	11 years ago
Fedor Indutny	0be5a94c56	doc: encoding is ignored if input is a Buffer NOTE: it wasn't in 0.8 fixes #6386	11 years ago
isaacs	849c92fec7	doc: Correct and add several items Several names/urls were out of date, and some really awesome stuff was missing.	11 years ago
Sam Roberts	155df9ca76	doc: document node signal handling Partly lifted from uv.h, partly from observation of node.cc.	11 years ago
Timothy J Fontaine	9f7f9d1240	blog: Post for v0.11.8	11 years ago
Ben Noordhuis	0c5981b226	doc: dgram: reword dgram.Socket#send() docs Make it clear that the address argument is not really optional and fix some Engrish and long lines while we're here. Fixes #6433.	11 years ago
Phillip Alexander	977c54adb5	doc: fs: clarify fs.symlink Windows specific args	11 years ago
Ryan Graham	5ac6f4de13	doc: improve module documentation Expands on when to use module.exports vs. exports. This is a recurring question on mailing list and continues to confuse new devs.	11 years ago
Sam Roberts	a60f67192f	doc: fix missing backtick in `2e16037`	11 years ago
Brian White	21265e20d3	doc: streams: document default objectMode setting	11 years ago
Zarko Stankovic	eb291de00e	doc: add nodejs.rs to the community page	11 years ago
isaacs	97813ae58d	blog: HTTP server DoS vulnerability details CVE-2013-4450	11 years ago
Timothy J Fontaine	028e524bce	blog: Post for v0.10.21	11 years ago
Timothy J Fontaine	2649ae8395	blog: Post for v0.8.26	11 years ago
Sam Roberts	2e16037201	doc: cluster documentation cleanup and corrections - fixed some incomprehensible wording ("event assigned to..."?) - removed undocumented and unnecessary process properties from example - corrected the docs on the default for the exec setting - described when workers are removed from cluster.workers - described addressType, which was documented as existing, but not what values it might have - spell out more clearly the limitations of setupMaster - describe disconnect in sufficient detail that why a child does or does not exit can be understood - clarify which cluster functions and events are available on process or just on the worker, as well as which are not available in children, - don't describe events as the same, when they have receive different arguments - fix misleading disconnect example: since disconnect already calls close on all servers, doing it again in the example is a no-op, not the "force close" it was claimed to be - document the error event, not catching it will kill your node - describe suicide better, it is important, and a bit unintuitive (process.exit() is not suicide?) - use worker consistently throughout, instead of child.	12 years ago
Sam Roberts	ed186c971c	doc: child_process corrections and cleanups - Make explicit that .disconnected is set before the disconnect event, and it is not allowed to send messages after calling .disconnect(), even while waiting for a delayed disconect event. - Remove obsolete claim that explicit exit is required - Describe silent: in the options for fork() - Describe .connected as the property it is, not just as an aside in the disconnect() method	12 years ago
Ben Noordhuis	5bc5210b92	doc: http: reword IncomingMessage 'close' event The bit that says "before response.end() was called or able to flush" doesn't apply to incoming streams. Fixes #6359.	11 years ago

1 2 3 4 5 ...

1620 Commits (61c0d571bf6317807fd0d569099397e5b26b09b9)