Node.js uses an event-driven, non-blocking I/O model that makes it lightweight and efficient, perfect for data-intensive real-time applications that run across distributed devices.
See the version list below for details.
Install-Package Node.js -Version 0.12.0
dotnet add package Node.js --version 0.12.0
<PackageReference Include="Node.js" Version="0.12.0" />
paket add Node.js --version 0.12.0
Following are some highlights of v0.12 release:
* Streams 3
- The Streams implementation now works the way you thought it already should, without introducing any changes to the API. Basically this means no more getting stuck in "old mode", there are only streams that are flowing or not.
- Streams now support the use of cork and uncork mechanisms to prevent flushing writes out to the system if an application is going to be performing many writes in a row. There is an implicit uncork performed when you end a writable stream.
- maxSockets are no longer limited to 5. The default is now set to Infinity with the developer and the operating system given control over how many simultaneous connections an application can keep open to a given host.
- Proper KeepAlive support means that sockets will stay open until they timeout at the configured time, are closed by the remote side, or the process exits. Developer's no longer have to make sure requests have been pipelined to keep the socket open, or use an alternative module to get that support.
- Developers can also now explicitly flushHeaders to ensure time to first byte is low and proxied connections are held open.
- Now has two modes of operation, the new default is a round robin distribution mechanism where the master accepts new connections and distributes them to your workers. If you want you can still opt back into the old method where your workers are responsible for acception connections.
- Added APIs for asynchronous SNI callbacks, OCSP stapling, and storage events.
- We use a more accurate mechanism for allocating memory for buffers now, which means you'll see less overhead and impact from holding onto to small slices of Buffers. This reduces the amount of memory pressure on the system, which means GC runs are quicker, which means Node.js is on CPU less, and thus lower latency for your applications.
- spawnSync/execSync have been added to facilitate synchronous child processes, warning your node process won't make forward progress while waiting for the child to exit, caveat emptor!
- Added APIs for loading custom engines for use with compiled in OpenSSL.
- More APIs support supplying the pass phrases.
- Added APIs for RSA public/private key encryption/decryption.
- The module is now based on the Contextify module, which shares values from the sandbox to avoid missing changes inside the execution from appearing in the parent context.
* Initial support for ECMAScript Internationalization API 1.0 (ECMA-402)
- By default, Node.js v0.12.0 binaries are shipped with ECMA-402 support, but only for the English language. In other words, the ECMA-402 API is working as you would expect, but only data for the English language is included. You can find more info on how to include more languages in the Wiki.
This package has no dependencies.
Showing the top 4 GitHub repositories that depend on Node.js:
Reporting tool for .NET Core/.NET Framework that helps your application generate document-like reports
Microsoft’s Corporate, External, and Legal Affairs (CELA) group, in partnership with the Office extensibility team, developed Matter Center for Office 365 -- a document management and collaboration solution built using the Office app development model, Azure and Sharepoint.