-
Notifications
You must be signed in to change notification settings - Fork 3
FAQ
http://logs.nodejs.org/node.js/
- When referring to the software or the project in general, it's Node.js or simply Node. It is a proper noun, so capitalize it. The
.js
appears with the first use, to disambiguate from other things called "Node", andNode
(without the .js) afterwards. One way to think of this is thatNode.js
is the full name, andNode
is the more familiar first name. - When referring specifically to the binary executable, it's always
node
, capitalized like a normal noun. - When referring to the libs that are included with the binary, as opposed to the libs published by Node users in The npm Registry, it's
node-core
. (See node core vs userland.) - "npm" is always lowercase, even when it appears at the start of a sentence, unless used in a context where all-caps are used (such as the title of a man page.)
- "Node.js" is pronounced either "node dot jay ess", or "node jay ess", or "node point javascript".
- "npm" is pronounced "en pee em", spelled out.
Odd versions are unstable, even versions are stable. v0.2 and v0.4 are even/stable. v0.3 and v0.5 are odd/unstable. The current stable series is v0.10.x. The next stable series will be v0.12.x. The stable branch takes bug fixes only - it does not change the JavaScript API, addon API, nor ABI (you don't have to rebuild modules after upgrading node with-in a stable branch).
Currently, by default v8 has a memory limit of 512mb on 32-bit systems, and 1gb on 64-bit systems. The limit can be raised by setting --max-old-space-size to a maximum of ~1gb (32-bit) and ~1.7gb (64-bit), but it is recommended that you split your single process into several workers if you are hitting memory limits.
Known issue: https://github.com/joyent/node/issues/4412
![Graph of size in MB vs node release, by dtrejo.com](http://c0848462.cdn.cloudfiles.rackspacecloud.com/c97716dd8e4f943501bfcaadcecfdd75d06407afde.jpg "Graph of size in MB vs node release, by dtrejo.com")