Node v8.0.0 (Current) | Node.js
The next major release of Node.js brings a range of significant changes and additions, far too many for us to cover adequately in a blog post such as this. This article contains a summary of the most significant changes and features. Say hello to npm version 5.0.0 npm, Inc. recently announced the release of version 5.0.0 of the npm client and we are happy to include this significant new version wi
Node.js — Node v7.0.0 (Current)
Node.js v7 has arrived! This new major version of Node.js includes: V8 5.4 which brings along with 98% coverage of ES6 language features, improved reliability and performance, and a new experimental URL parser based on the WHATWG URL standard. As an odd numbered release, in accordance with our Long Term Support plan, Node.js v7 will be supported only until about June, 2017, with Node.js v8 current
Node.js — Node v6.3.0 (Current)
Notable changes buffer: Added buffer.swap64() to complement swap16() & swap32(). (Zach Bjornson) #7157 build: New configure options have been added for building Node.js as a shared library. (Stefan Budeanu) #6994 The options are: --shared, --without-v8-platform & --without-bundled-v8. crypto: Root certificates have been updated. (Ben Noordhuis) #7363 debugger: The server address is now configurabl
Node.js — Node v6.2.0 (Current)
Notable Changes buffer: fix lastIndexOf and indexOf in various edge cases (Anna Henningsen) #6511 child_process: use /system/bin/sh on android (Ben Noordhuis) #6745 deps: upgrade npm to 3.8.9 (Rebecca Turner) #6664 upgrade to V8 5.0.71.47 (Ali Ijaz Sheikh) #6572 upgrade libuv to 1.9.1 (Saúl Ibarra Corretgé) #6796 Intl: ICU 57 bump (Steven R. Loomis) #6088 repl: copying tabs shouldn't trigger compl
Node.js — Node v6.0.0 (Current)
It's here! Just three days shy of exactly six months after we released v5.0.0, the Node.js Foundation is happy to announce that Node.js v6 is available and ready for use! This new major version of Node.js delivers significant improvements in performance, reliability, usability and security. Module loading is nearly four times faster than in Node.js v4, tests and documentation have seen significant
Node.js — Node v5.1.0 (Current)
Notable changes buffer: The noAssert option for many buffer functions will now silently drop invalid write values rather than crashing (P.S.V.R) #3767. This makes the behavior match what the docs suggest. child_process: child.send() now properly returns a boolean like the docs suggest (Rich Trott) #3577. doc: All of the API docs have been re-ordered so as to read in alphabetical order (Tristian Fl
Node v5.0.0 (Current) | Node.js
Say hello to Node.js v5! It's true that we only recently released Node.js v4.0.0, however this new release doesn't mean that v4 is going away. In fact, v4 is going to live for a lot longer than v5. According to our new LTS (Long-term Support) plan, Node.js v4 Argon will continue to be supported for 30 months, ending in April 2018. This new version of Node.js, however, will only be supported for 8
Node.js — Node v4.1.0 (Current)
2015-09-17, Version 4.1.0 (Current), @Fishrock123 Notable changes buffer: Buffers are now created in JavaScript, rather than C++. This increases the speed of buffer creation (Trevor Norris) #2866. Buffer#slice() now uses Uint8Array#subarray() internally, increasing slice() performance (Karl Skomski) #2777. fs: fs.utimes() now properly converts numeric strings, NaN, and Infinity (Yazhong Liu) #2387
Node.js — Node v4.0.0 (Current)
The collaborators of the Node.js project and the members of the Node.js Foundation are proud to offer v4.0.0 for general release. This release represents countless hours of hard work encapsulated in both the Node.js project and the io.js project that are now combined in a single codebase. The Node.js project is now operated by a team of 44 collaborators, 15 of which form its Technical Steering Com
Node.js — Node v0.12.0 (Stable)
We are excited to announce the availability of Node.js v0.12! It has been a long process, and we want to thank contributors and all of the community who waited patiently for this event. Node.js has such a vibrant and enthusiastic community, and we're very lucky to have you all supporting us. Node.js has seen many changes between v0.10 and v0.12. There is a listing of changes documented on the wiki
io.js - JavaScript I/O
Run JavaScript EverywhereNode.js® is a free, open-source, cross-platform JavaScript runtime environment that lets developers create servers, web apps, command line tools and scripts. Download Node.js (LTS)Download Node.js (LTS)Downloads Node.js v20.15.01 with long-term support. Node.js can also be installed via package managers.Want new features sooner? Get Node.js v22.4.01 instead. // server.mjs
Node.js — Blog
The latest Node.js news, case studies, tutorials, and resources.
Node.js — Node v0.10.0 (Stable)
I am pleased to announce a new stable version of Node. This branch brings significant improvements to many areas, with a focus on API polish, ease of use, and backwards compatibility. For a very brief overview of the relevant API changes since v0.8, please see the API changes wiki page. Streams2 In a previous post, we introduced the "Streams2" API changes. If you haven't reviewed the changes, plea
http://nodejs.org/cla.html
NodeJS Contributor License Agreement ("Agreement") Thank you for your interest in the NodeJS open source project being administered by Joyent, Inc , dba NodeJS ("NodeJS"). The form of license below is a document that clarifies the terms under which You, the person listed below, may contribute software, bug fixes, configuration changes, documentation, or any other materials that you send to us rela
Node.js — Node v0.8.0
I am thrilled to announce the arrival of a new stable version of Node.js. Compared with the v0.6 releases of Node, this release brings significant improvements in many key performance metrics, as well as cleanup in several core APIs, and the addition of new debugging features. tl;dr With version 0.8.0: Node got a lot faster. Node got more stable. You can do stuff with file descriptors again. The c
Node.js — HTTP Server Security Vulnerability: Please upgrade to 0.6.17
tl;dr A carefully crafted attack request can cause the contents of the HTTP parser's buffer to be appended to the attacking request's header, making it appear to come from the attacker. Since it is generally safe to echo back contents of a request, this can allow an attacker to get an otherwise correctly designed server to divulge information about other requests. It is theoretically possible that
1
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く
