Please send spam and suggestions to webmaster@prcn.co.cc. You can also support us financially by sending us a bitcoin anonymous P2P payment to 145fgRHuMQJ9sHUVqAtmhhQz2vKGbAj88K, by You like it - you tip it bitcoin donation system or by Flattr social donation system:

Downloads

0.4.12
complete. The latest NPM is installed without any third-party patches.
0.4.11
complete. The latest NPM is installed without any third-party patches.
0.4.9
complete.
0.4.8
complete. This release uses the NPM 1.x patched by Rafal Jonca. NPM support is largely untested, so please report.
0.4.7
complete.
0.4.6
complete.
0.4.5
complete.
0.4.4
complete. This release uses the patched NPM of Rafal Jonca.
0.4.3
complete. NPM 0.3.12 is included, but please test and report.

Older binaries (0.1.x-0.3.x)

How to use

Download the latest 'complete' package, unpack into any folder, read documentation (doc/index.html) and enjoy. No Cygwin installation is required as Cygwin dll and Cygwin gcc/g++ runtime libraries are shipped along. Everything else is statically linked in (those are default build parameters, I didn't change anything). HTTPS and other cryptographic APIs are supported by the binaries since 0.2.0.

Complete
This package must be enough for most users to start experiments. It contains node.exe + dll dependencies + documentation. It's not truly 'complete' as you cannot extend Node with modules written in C++, but that requires full Cygwin installation anyway.

News And Updates

2011-10-03
Node.js gets support from Microsoft. No wonder that operation under Cygwin is abolished. Now node 0.5.8 is out, and it's the first native Windows version to be supported by NPM: there is an Official NPM installation instruction. The instruction requires you to git clone, so I prepared tiny git binaries for you: minimal Git for Windows. Download the "clone" package.
2011-09-27
Node 0.4.12 binaries were released. Note that we are all doomed: the upstream Node.js community dropped support for Cygwin in 0.5.x and future versions. They believe that a fully working native Win32 port is a better idea than a Cygwin port, but in many cases it's not the case. For example, many binary libraries and tools do not yet support Win32 but work under Cygwin. Cygwin is a PITA to support, so I understand them to some extent. Also, NPM seems to have a bug with piping data to tar and gzip which only manifests itself on Cygwin. So NPM almost dropped support for Cygwin too by refusing to look closer at it or implementing workarounds. So feel free to create npm-cygwin fork on GitHub and let me use that patched version in my binaries. One quick fix would be to use tar -z instead of launching separate tar and gz executables and piping data between them using Node.JS facilities.
2011-08-29
A workaround for previous issues was found, but Node.js issue #1602 still prevents Node 0.5.5 to be built. Please help Node.js developers to resolve the crash.
2011-08-28
Node 0.5.5 cannot be built on Cygwin because ld segfaults (Node.js issue #1599). NPM is unstable on Cygwin (tarball extractions fails sometimes) because of the following problem (see NPM issue #1305):
Cygwin's handling of child procs is terrible. Until npm can do tar completely in JS, it's going to remain a source of pain.
Please, help with fixing those issues so I can build 0.5.x.
2011-08-23
Node 0.4.11 binaries were released. The version was tested with a large bunch of NPM libraries: q, qq, async, request, socket.io, socketstream, express, connect, jade, dirty, redis, openid, vows ... DLLs for ZeroMQ (zmq module) and contextify (required by recent jsdom) can be provided on demand. The 0.5.x branch is too unstable yet to be useful - 0.5.4 is the first version that builds, but segfaults during installation of NPM. I will try to install NPM with the native windows binaries in near future.
2011-07-10
Node 0.4.9 binaries were released.
2011-06-19
Node 0.4.8 binaries were released.
2011-04-27
Node 0.4.7 binaries were released. Cygwin DLLs were updated too.
2011-04-15
Node 0.4.6 binaries were released.
2011-04-04
Node 0.4.4 binaries were released. I also shamelessly advertise my other projects: MRTG Online and A catalog of Cheapest VPS. Enjoy!
2011-03-22
Node 0.4.3 binaries were released.
2011-03-07
Node 0.4.1 binaries were released. NPM seems to be broken - please report here and suggest a solution to the NPM author. As a workaround you can copy the new exe to older releases of the binaries with older NPM. The problems are: 1) NPM relies on sh and a few other tools for non-critical tasks like displaying its own installation logs. These tools don't exist in our stripped package. 2) Newer releases of NPM perform setuid operations which are not necessary in our single-user xcopy-style installation.
2011-02-16
Node 0.4.0 binaries were released.
2011-01-18

Node Package Manager (NPM) support was added. Run bin/shell.cmd, and then node npm install <package_name>.

Note that node.exe requires POSIX paths - use either runnode.cmd c:\foo\bar\baz.js or node.exe /cygdrive/c/foo/bar/baz.js.

2011-01-15
Outgoing connections to host names (as opposed to numeric IP addresses) were not working in earlier releases because of missing resolv.conf. Node 0.3.1 was re-released with proper resolv.conf having Google DNS servers. The binaries are the same. Everyone is suggested to upgrade or at least to rearrange the files in his installation like in this distribution and add resolv.conf.
2011-01-14
The 0.3.2, 0.3.3, 0.3.4 source releases of Node.JS all cannot be compiled under Cygwin out of the box. That's why there were no new binary releases. Please submit a patch to the official codebase and force the developers to accept and integrate it :-)
2010-12-16
An experimental Arch Linux PKGBUILD for 0.3.1 is available. It is basically a version from AUR for 0.2.5 patched for node-waf located at different place in the 0.3.x branch. Please test and report.

Older news (since 2010-08-03)

Contact Us

Your feedback is always welcomed.

О проекте node.js

Учите английский, блядь! Это серверный однопоточный джаваскрипт-движок на событиях (libev), состоящий из гугловского якобы высокопроизводительного JIT-компилятора V8 и библиотеки асинхронного ввода-вывода к нему. В библиотеке присутствует HTTP-сервер, что позволяет получить что-то в духе эрланговского MochiWeb и питоновского TornadoWeb, но позволяющее писать клиентский (браузерный/AJAX) и серверный ('cкрипты') код на одном языке. Ну и конечно геморрой в стиле mod_perl + POE вам обеспечен. Тем не менее, говорят, это прогрессивно и круто. (Шутка)

Для особо одарённых, уточняю. Вышеперечисленное включает: вонючую, но встроенную вариацию memcached; невозможность без плясок с бубном, не снившихся питоновцам, задействовать более одного ядра; новые уязвимости из-за паразитной передачи данных в параллельно исполняющийся запрос; падучесть всей VM вместе с вашими фронт-эндом и бэк-эндом в стиле легендарной DOS при зацикливании или непойманном исключении в любом из обработчиков событий; возможность неправильно реализовать HTTP; феерический пул потоков для исполнения в нём unlink(); развесистые монады при вводе-выводе, не снившиеся хаскеллистам; ну и, конечно же, необходимость писать юнит-тесты на каждый чих, потому что только джедаи в состоянии безошибочно разыменовать хеш массивов хешей хешей массивов, а а компилятор попытки присвоить ёжику зайчика не ловит.

Но и это ещё не всё! Для затягивания сроков и удорожания разработки система включает: иллюзию эрланговской изоляции посредством порождения дочерних песочниц в рамках одного потока; циклы перебора байтиков в буфере в стиле Паскаля с неявным алиасингом; отсутствие возможности читать файлы построчно.

About this page design

We don't care about design. So we went to a free designs catalog and picked one named "Simplicity 2.0".