- #1233 Fix os.totalmem on FreeBSD amd64 (Artem Zaytsev) 14 |
- #1149 IDNA and Punycode support in url.parse (Jeremy Selier, Ben Noordhuis, isaacs) 15 |
- Export $CC and $CXX to uv and V8's build systems 16 |
- Include pthread-win32 static libraries in build (Igor Zinkovsky) 17 |
- #1199, #1094 Fix fs can't handle large file on 64bit platform (koichik) 18 |
- #1281 Make require a public member of module (isaacs) 19 |
- #1303 Stream.pipe returns the destination (Elijah Insua) 20 |
- #1229 Addons should not -DEV_MULTIPLICITY=0 (Brian White) 21 |
- libuv backend improvements 22 |
- Upgrade V8 to 3.4.10
- Remove cmake build system, support for Cygwin, legacy code base, process.ENV, process.ARGV, process.memoryUsage().vsize, os.openOSHandle 14 |
- Documentation improvments (Igor Zinkovsky, Bert Belder, Ilya Dmitrichenko, koichik, Maciej Małecki, Guglielmo Ferri, isaacs) 15 |
- Performance improvements (Daniel Ennis, Bert Belder, Ben Noordhuis) 16 |
- Long process.title support (Ben Noordhuis) 17 |
- net: register net.Server callback only once (Simen Brekken) 18 |
- net: fix connect queue bugs (Ben Noordhuis) 19 |
- debugger: fix backtrace err handling (Fedor Indutny) 20 |
- Use getaddrinfo instead of c-ares for dns.lookup 21 |
- Emit 'end' from crypto streams on close 22 |
- repl: print out `undefined` (Nathan Rajlich) 23 |
- #1902 buffer: use NO_NULL_TERMINATION flag (koichik) 24 |
- #1907 http: Added support for HTTP PATCH verb (Thomas Parslow) 25 |
- #1644 add GetCPUInfo on windows (Karl Skomski) 26 |
- #1484, #1834, #1482, #771 Don't use a separate context for the repl. (isaacs) 27 |
- #1882 zlib Update 'availOutBefore' value, and test (isaacs) 28 |
- #1888 child_process.fork: don't modify args (koichik) 29 |
- #1516 tls: requestCert unusable with Firefox and Chrome (koichik) 30 |
- #1467 tls: The TLS API is inconsistent with the TCP API (koichik) 31 |
- #1894 net: fix error handling in listen() (koichik) 32 |
- #1860 console.error now goes through uv_tty_t 33 |
- Upgrade V8 to 3.7.0 34 |
- Upgrade GYP to r1081
- libuv improvements; named pipe support 14 |
- #1242 check for SSL_COMP_get_compression_methods() (Ben Noordhuis) 15 |
- #1348 remove require.paths (isaacs) 16 |
- #1349 Delimit NODE_PATH with ; on Windows (isaacs) 17 |
- #1335 Remove EventEmitter from C++ 18 |
- #1357 Load json files with require() (isaacs) 19 |
- #1374 fix setting ServerResponse.statusCode in writeHead (Trent Mick) 20 |
- Fixed: GC was being run too often. 21 |
- Upgrade V8 to 3.4.14 22 |
- doc improvements
- Fix crypto encryption/decryption with Base64. (SAWADA Tadashi) 15 | 16 |
- #243 Add an optional length argument to Buffer.write() (koichik) 17 | 18 |
- #657 convert nonbuffer data to string in fs.writeFile/Sync (Daniel Pihlström) 19 | 20 |
- Add process.features, remove process.useUV (Ben Noordhuis) 21 | 22 |
- #324 Fix crypto hmac to accept binary keys + add test cases from rfc 2202 and 4231 (Stefan Bühler) 23 | 24 |
- Add Socket::bytesRead, Socket::bytesWritten (Alexander Uvarov) 25 | 26 |
- #572 Don't print result of --eval in CLI (Ben Noordhuis) 27 | 28 |
- #1223 Fix http.ClientRequest crashes if end() was called twice (koichik) 29 | 30 |
- #1383 Emit 'close' after all connections have closed (Felix Geisendörfer) 31 | 32 |
- Add sprintf-like util.format() function (Ben Noordhuis) 33 | 34 |
- Add support for TLS SNI (Fedor Indutny) 35 | 36 |
- New http agent implementation. Off by default the command line flag
--use-http2will enable it.make test-http2will run the tests for the new implementation. (Mikeal Rogers) 37 | 38 | - Revert AMD compatibility. (isaacs) 39 | 40 |
- Windows: improvements, child_process support. 41 | 42 |
- Remove pkg-config file. 43 | 44 |
- Fix startup time regressions. 45 | 46 |
- doc improvements
- libuv/Windows compatibility improvements 15 | 16 |
- Build on Microsoft Visual Studio via GYP. Use generate-projects.bat in the to build sln files. (Peter Bright, Igor Zinkovsky) 17 | 18 |
- Make Mikeal's HTTP agent client the default. Use old HTTP client with
--use-http119 | 20 | - Fixes https host header default port handling. (Mikeal Rogers) 21 | 22 |
- #1440 strip byte order marker when loading *.js and *.json files (Ben Noordhuis) 23 | 24 |
- #1434 Improve util.format() compatibility with browser. (Koichi Kobayashi) 25 | 26 |
- Provide unchecked uint entry points for integer Buffer.read/writeInt methods. (Robert Mustacchi) 27 | 28 |
- CMake improvements (Tom Huges) 29 | 30 |
- Upgrade V8 to 3.5.4.
2011.08.26, Version 0.5.5 (unstable)
13 |-
14 |
- typed arrays, implementation from Plesk 15 |
- fix IP multicast on SunOS 16 |
- fix DNS lookup order: IPv4 first, IPv6 second (--use-uv only) 17 |
- remove support for UNIX datagram sockets (--use-uv only) 18 |
- UDP support for Windows (Bert Belder) 19 |
- #1572 improve tab completion for objects in the REPL (Nathan Rajlich) 20 |
- #1563 fix buffer overflow in child_process module (reported by Dean McNamee) 21 |
- #1546 fix performance regression in http module (reported by Brian Geffon) 22 |
- #1491 add PBKDF2 crypto support (Glen Low) 23 |
- #1447 remove deprecated http.cat() function (Mikeal Rogers) 24 |
- #1140 fix incorrect dispatch of vm.runInContext's filename argument
25 | (Antranig Basman) 26 | - #1140 document vm.runInContext() and vm.createContext() (Antranig Basman) 27 |
- #1428 fix os.freemem() on 64 bits freebsd (Artem Zaytsev) 28 |
- #1164 make all DNS lookups async, fixes uncatchable exceptions
29 | (Koichi Kobayashi) 30 | - fix incorrect ssl shutdown check (Tom Hughes) 31 |
- various cmake fixes (Tom Hughes) 32 |
- improved documentation (Koichi Kobayashi, Logan Smyth, Fedor Indutny,
33 | Mikeal Rogers, Maciej Małecki, Antranig Basman, Mickaël Delahaye) 34 | - upgrade libuv to commit 835782a 35 |
- upgrade V8 to 3.5.8 36 |
Download: https://nodejs.org/dist/node-v0.5.5.tar.gz
38 |Windows Executable: https://nodejs.org/dist/v0.5.5/node.exe
39 |Website: https://nodejs.org/docs/v0.5.5/
40 |Documentation: https://nodejs.org/docs/v0.5.5/api/
41 |42 | 43 | Update: The
.exe has a bug that results in incompatibility with Windows XP and Server 2003. This has been reported in issue #1592 and fixed. A new binary was made that is compatibile with the older Windows: https://nodejs.org/dist/v0.5.5/node-186364e.exe.
44 |
--------------------------------------------------------------------------------
/nodejs.org/locale/uk/blog/release/v0.5.7.md:
--------------------------------------------------------------------------------
1 | ---
2 | version: 0.5.7
3 | title: Node v0.5.7 (unstable)
4 | author: ryandahl
5 | date: 2011-09-17T01:57:03.000Z
6 | status: publish
7 | category: release
8 | slug: node-v0-5-7-unstable
9 | layout: blog-post.hbs
10 | ---
11 |
12 | 2011.09.16, Version 0.5.7 (unstable)
13 | -
14 |
- Upgrade V8 to 3.6.4 15 |
- Improve Windows compatibility 16 |
- Documentation improvements 17 |
- Debugger and REPL improvements (Fedor Indutny) 18 |
- Add legacy API support: net.Stream(fd), process.stdout.writable, process.stdout.fd 19 |
- Fix mkdir EEXIST handling (isaacs) 20 |
- Use net_uv instead of net_legacy for stdio 21 |
- Do not load readline from util.inspect 22 |
- #1673 Fix bug related to V8 context with accessors (Fedor Indutny) 23 |
- #1634 util: Fix inspection for Error (koichik) 24 |
- #1645 fs: Add positioned file writing feature to fs.WriteStream (Thomas Shinnick) 25 |
- #1637 fs: Unguarded fs.watchFile cache statWatchers checking fixed (Thomas Shinnick) 26 |
- #1695 Forward customFds to ChildProcess.spawn 27 |
- #1707 Fix hasOwnProperty security problem in querystring (isaacs) 28 |
- #1719 Drain OpenSSL error queue
- zlib bindings (isaacs) 13 |
- Windows supports TTY ANSI escape codes (Bert Belder) 14 |
- Debugger improvements (Fedor Indutny) 15 |
- crypto: look up SSL errors with ERR_print_errors() (Ben Noordhuis) 16 |
- dns callbacks go through MakeCallback now 17 |
- Raise an error when a malformed package.json file is found. (Ben Leslie) 18 |
- buffers: handle bad length argument in constructor (Ben Noordhuis) 19 |
- #1726, unref process.stdout 20 |
- Doc improvements (Ben Noordhuis, Fedor Indutny, koichik) 21 |
- Upgrade libuv to fe18438
- fs.watch interface backed by kqueue, inotify, and ReadDirectoryChangesW (Igor Zinkovsky, Ben Noordhuis) 14 |
- add dns.resolveTxt (Christian Tellnes) 15 |
- Remove legacy http library (Ben Noordhuis) 16 |
- child_process.fork returns and works on Windows. Allows passing handles. (Igor Zinkovsky, Bert Belder) 17 |
- #1774 Lint and clean up for --harmony_block_scoping (Tyler Larson, Colton Baker) 18 |
- #1813 Fix ctrl+c on Windows (Bert Belder) 19 |
- #1844 unbreak --use-legacy (Ben Noordhuis) 20 |
- process.stderr now goes through libuv. Both process.stdout and process.stderr are blocking when referencing a TTY. 21 |
- net_uv performance improvements (Ben Noordhuis, Bert Belder)
- doc improvements (Eric Lovett, Ben Noordhuis, Scott Anderson, Yoji SHIDARA) 14 |
- crypto: make thread-safe (Ben Noordhuis) 15 |
- fix process.kill error object 16 |
- debugger: correctly handle source with multi-byte characters (Shigeki Ohtsu) 17 |
- make stdout and stderr non-destroyable (Igor Zinkovsky) 18 |
- fs: don't close uninitialized fs.watch handle (Ben Noordhuis) 19 |
- #2026 fix man page install on BSDs (Ben Noordhuis) 20 |
- #2040 fix unrecognized errno assert in uv_err_name 21 |
- #2043 fs: mkdir() should call callback if mode is omitted 22 |
- #2045 fs: fix fs.realpath on windows to return on error (Benjamin Pasero) 23 |
- #2047 minor cluster improvements 24 |
- #2052 readline get window columns correctly 25 |
- Upgrade V8 to 3.6.6.7
2012.02.02, Version 0.6.10 (stable)
13 | 14 |-
15 |
Update V8 to 3.6.6.20
16 | Add npm msysgit bash shim to msi installer (isaacs)
17 | buffers: fix intermittent out of bounds error (Ben Noordhuis)
18 | buffers: honor length argument in base64 decoder (Ben Noordhuis)
19 | windows: Fix path.exists regression (Bert Belder)
20 | Make QueryString.parse run faster (Philip Tellis)
21 | http: avoid freeing http-parser objects too early (koichik)
22 | timers: add v0.4 compatibility hack (Ben Noordhuis)
23 | Proper EPERM error code support (Igor Zinkovsky, Brandon Philips)
24 | dgram: Implement udp multicast methods on windows (Bert Belder)
25 |
Source Code: https://nodejs.org/dist/v0.6.10/node-v0.6.10.tar.gz
26 | 27 |Windows Installer: https://nodejs.org/dist/v0.6.10/node-v0.6.10.msi
28 | 29 |Macintosh Installer: https://nodejs.org/dist/v0.6.10/node-v0.6.10.pkg
30 | 31 |Website: https://nodejs.org/docs/v0.6.10/
32 | 33 |Documentation: https://nodejs.org/docs/v0.6.10/api/
34 | -------------------------------------------------------------------------------- /nodejs.org/locale/uk/blog/release/v0.6.13.md: -------------------------------------------------------------------------------- 1 | --- 2 | version: 0.6.13 3 | title: Version 0.6.13 (stable) 4 | author: Isaac Schlueter 5 | date: 2012-03-15T17:37:02.000Z 6 | status: publish 7 | category: release 8 | slug: version-0-6-13-stable 9 | layout: blog-post.hbs 10 | --- 11 | 12 |2012.03.15 Version 0.6.13 (stable) 13 | 14 |
15 |-
16 |
Windows: Many libuv test fixes (Bert Belder)
17 |
18 | Windows: avoid uv_guess_handle crash in when fd < 0 (Bert Belder)
19 |
20 | Map EBUSY and ENOTEMPTY errors (Bert Belder)
21 |
22 | Windows: include syscall in fs errors (Bert Belder)
23 |
24 | Fix fs.watch ENOSYS on Linux kernel version mismatch (Ben Noordhuis)
25 |
26 | Update npm to 1.1.9
27 |28 | - upgrade node-gyp to 0.3.5 (Nathan Rajlich)
38 |
29 | - Fix isaacs/npm#2249 Add cache-max and cache-min configs
30 | - Properly redirect across https/http registry requests
31 | - log config usage if undefined key in set function (Kris Windham)
32 | - Add support for os/cpu fields in package.json (Adam Blackburn)
33 | - Automatically node-gyp packages containing a binding.gyp
34 | - Fix failures unpacking in UNC shares
35 | - Never create un-listable directories
36 | - Handle cases where an optionalDependency fails to build 37 |
39 |
Source Code: https://nodejs.org/dist/v0.6.13/node-v0.6.13.tar.gz 41 | 42 |
43 |Windows Installer: https://nodejs.org/dist/v0.6.13/node-v0.6.13.msi 44 | 45 |
46 |Macintosh Installer: https://nodejs.org/dist/v0.6.13/node-v0.6.13.pkg 47 | 48 |
49 |Website: https://nodejs.org/docs/v0.6.13/ 50 | 51 |
52 |Documentation: https://nodejs.org/docs/v0.6.13/api/ 53 |
54 | -------------------------------------------------------------------------------- /nodejs.org/locale/uk/blog/release/v0.6.14.md: -------------------------------------------------------------------------------- 1 | --- 2 | version: 0.6.14 3 | title: Version 0.6.14 (stable) 4 | author: Isaac Schlueter 5 | date: 2012-03-23T18:22:22.000Z 6 | status: publish 7 | category: release 8 | slug: version-0-6-14-stable 9 | layout: blog-post.hbs 10 | --- 11 | 12 |2012.03.22 Version 0.6.14 (stable) 13 | 14 |
15 |-
16 |
net: don't crash when queued write fails (Igor Zinkovsky)
17 |
18 | sunos: fix EMFILE on process.memoryUsage() (Bryan Cantrill)
19 |
20 | crypto: fix compile-time error with openssl 0.9.7e (Ben Noordhuis)
21 |
22 | unix: ignore ECONNABORTED errors from accept() (Ben Noordhuis)
23 |
24 | Add UV_ENOSPC and mappings to it (Bert Belder)
25 |
26 | http-parser: Fix response body is not read (koichik)
27 |
28 | Upgrade npm to 1.1.12
29 |30 | - upgrade node-gyp to 0.3.7
37 |
31 | - work around AV-locked directories on Windows
32 | - Fix isaacs/npm#2293 Don't try to 'uninstall' /
33 | - Exclude symbolic links from packages.
34 | - Fix isaacs/npm#2275 Spurious 'unresolvable cycle' error.
35 | - Exclude/include dot files as if they were normal files 36 |
38 |
Source Code: https://nodejs.org/dist/v0.6.14/node-v0.6.14.tar.gz 40 | 41 |
42 |Windows Installer: https://nodejs.org/dist/v0.6.14/node-v0.6.14.msi 43 | 44 |
45 |Windows x64 Files: https://nodejs.org/dist/v0.6.14/x64/ 46 | 47 |
48 |Macintosh Installer (Universal): https://nodejs.org/dist/v0.6.14/node-v0.6.14.pkg 49 | 50 |
51 |Other release files: https://nodejs.org/dist/v0.6.14/ 52 | 53 |
54 |Website: https://nodejs.org/docs/v0.6.14/ 55 | 56 |
57 |Documentation: https://nodejs.org/docs/v0.6.14/api/ 58 |
59 | -------------------------------------------------------------------------------- /nodejs.org/locale/uk/blog/release/v0.6.15.md: -------------------------------------------------------------------------------- 1 | --- 2 | version: 0.6.15 3 | title: Version 0.6.15 (stable) 4 | author: Isaac Schlueter 5 | date: 2012-04-09T17:39:18.000Z 6 | status: publish 7 | category: release 8 | slug: version-0-6-15-stable 9 | layout: blog-post.hbs 10 | --- 11 | 12 |2012.04.09 Version 0.6.15 (stable) 13 | 14 |
15 |-
16 |
Update npm to 1.1.16
17 |
18 | Show licenses in binary installers.
19 |
20 | unix: add uv_fs_read64, uv_fs_write64 and uv_fs_ftruncate64 (Ben Noordhuis)
21 |
22 | add 64bit offset fs functions (Igor Zinkovsky)
23 |
24 | windows: don't report ENOTSOCK when attempting to bind an udp handle twice (Bert Belder)
25 |
26 | windows: backport pipe-connect-to-file fixes from master (Bert Belder)
27 |
28 | windows: never call fs event callbacks after closing the watcher (Bert Belder)
29 |
30 | fs.readFile: don't make the callback before the fd is closed (Bert Belder)
31 |
32 | windows: use 64bit offsets for uv_fs apis (Igor Zinkovsky)
33 |
34 | Fix #2061: segmentation fault on OS X due to stat size mismatch (Ben Noordhuis)
35 |
36 |
Source Code: https://nodejs.org/dist/v0.6.15/node-v0.6.15.tar.gz 38 | 39 |
40 |Windows Installer: https://nodejs.org/dist/v0.6.15/node-v0.6.15.msi 41 | 42 |
43 |Windows x64 Files: https://nodejs.org/dist/v0.6.15/x64/ 44 | 45 |
46 |Macintosh Installer (Universal): https://nodejs.org/dist/v0.6.15/node-v0.6.15.pkg 47 | 48 |
49 |Other release files: https://nodejs.org/dist/v0.6.15/ 50 | 51 |
52 |Website: https://nodejs.org/docs/v0.6.15/ 53 | 54 |
55 |Documentation: https://nodejs.org/docs/v0.6.15/api/ 56 |
57 | -------------------------------------------------------------------------------- /nodejs.org/locale/uk/blog/release/v0.6.16.md: -------------------------------------------------------------------------------- 1 | --- 2 | version: 0.6.16 3 | title: Version 0.6.16 (stable) 4 | author: Isaac Schlueter 5 | date: 2012-04-30T18:13:50.000Z 6 | status: publish 7 | category: release 8 | slug: version-0-6-16-stable 9 | layout: blog-post.hbs 10 | --- 11 | 12 |2012.04.30 Version 0.6.16 (stable) 13 | 14 |
15 |-
16 |
Upgrade V8 to 3.6.6.25
17 |
18 | Upgrade npm to 1.1.18
19 |
20 | Windows: add mappings for UV_ENOENT (Bert Belder)
21 |
22 | linux: add IN_MOVE_SELF to inotify event mask (Ben Noordhuis)
23 |
24 | unix: call pipe handle connection cb on accept() error (Ben Noordhuis)
25 |
26 | unix: handle EWOULDBLOCK (Ben Noordhuis)
27 |
28 | map EWOULDBLOCK to UV_EAGAIN (Ben Noordhuis)
29 |
30 | Map ENOMEM to UV_ENOMEM (isaacs)
31 |
32 | Child process: support the
33 |gidanduidoptions (Bert Belder)
34 | test: cluster: add worker death event test (Ben Noordhuis)
35 |
36 | typo in node_http_parser (isaacs)
37 |
38 | http_parser: Eat CRLF between requests, even on connection:close. (Ben Noordhuis)
39 |
40 | don't check return value of unsetenv (Ben Noordhuis)
41 |
42 |
Source Code: https://nodejs.org/dist/v0.6.16/node-v0.6.16.tar.gz 44 | 45 |
46 |Windows Installer: https://nodejs.org/dist/v0.6.16/node-v0.6.16.msi 47 | 48 |
49 |Windows x64 Files: https://nodejs.org/dist/v0.6.16/x64/ 50 | 51 |
52 |Macintosh Installer (Universal): https://nodejs.org/dist/v0.6.16/node-v0.6.16.pkg 53 | 54 |
55 |Other release files: https://nodejs.org/dist/v0.6.16/ 56 | 57 |
58 |Website: https://nodejs.org/docs/v0.6.16/ 59 | 60 |
61 |Documentation: https://nodejs.org/docs/v0.6.16/api/ 62 |
63 | -------------------------------------------------------------------------------- /nodejs.org/locale/uk/blog/release/v0.6.17.md: -------------------------------------------------------------------------------- 1 | --- 2 | version: 0.6.17 3 | title: Version 0.6.17 (stable) 4 | author: Isaac Schlueter 5 | date: 2012-05-04T20:33:12.000Z 6 | status: publish 7 | category: release 8 | slug: version-0-6-17-stable 9 | layout: blog-post.hbs 10 | --- 11 | 12 |2012.05.04 Version 0.6.17 (stable) 13 | 14 |
15 |-
16 |
Upgrade npm to 1.1.21
17 |
18 | uv: Add support for EROFS errors (Ben Noordhuis, Maciej Małecki)
19 |
20 | uv: Add support for EIO and ENOSPC errors (Fedor Indutny)
21 |
22 | windows: Add support for EXDEV errors (Bert Belder)
23 |
24 | http: Fix client memory leaks (isaacs, Vincent Voyer)
25 |
26 | fs: fix file descriptor leak in sync functions (Ben Noordhuis)
27 |
28 | fs: fix ReadStream / WriteStream double close bug (Ben Noordhuis)
29 |
30 |
Source Code: https://nodejs.org/dist/v0.6.17/node-v0.6.17.tar.gz 32 | 33 |
34 |Windows Installer: https://nodejs.org/dist/v0.6.17/node-v0.6.17.msi 35 | 36 |
37 |Windows x64 Files: https://nodejs.org/dist/v0.6.17/x64/ 38 | 39 |
40 |Macintosh Installer (Universal): https://nodejs.org/dist/v0.6.17/node-v0.6.17.pkg 41 | 42 |
43 |Other release files: https://nodejs.org/dist/v0.6.17/ 44 | 45 |
46 |Website: https://nodejs.org/docs/v0.6.17/ 47 | 48 |
49 |Documentation: https://nodejs.org/docs/v0.6.17/api/ 50 |
51 | -------------------------------------------------------------------------------- /nodejs.org/locale/uk/blog/release/v0.6.18.md: -------------------------------------------------------------------------------- 1 | --- 2 | version: 0.6.18 3 | title: Version 0.6.18 (stable) 4 | author: Isaac Schlueter 5 | date: 2012-05-15T17:06:13.000Z 6 | status: publish 7 | category: release 8 | slug: version-0-6-18-stable 9 | layout: blog-post.hbs 10 | --- 11 | 12 |2012.05.15 Version 0.6.18 (stable) 13 | 14 |
15 |-
16 |
windows: skip GetFileAttributes call when opening a file (Bert Belder)
17 |
18 | crypto: add PKCS12/PFX support (Sambasiva Suda)
19 |
20 | #3240: child_process: delete NODE_CHANNEL_FD from env in spawn (Ben Noordhuis)
21 |
22 | windows: add test for path.normalize with UNC paths (Bert Belder)
23 |
24 | windows: make path.normalize convert all slashes to backslashes (Bert Belder)
25 |
26 | fs: Automatically close FSWatcher on error (Bert Belder)
27 |
28 | #3258: fs.ReadStream.pause() emits duplicate data event (koichik)
29 |
30 | pipe_wrap: don't assert() on pipe accept errors (Ben Noordhuis)
31 |
32 | Better exception output for module load and process.nextTick (Felix Geisendörfer)
33 |
34 | zlib: fix error reporting (Ben Noordhuis)
35 |
36 | http: Don't destroy on timeout (isaacs)
37 |
38 | #3231: http: Don't try to emit error on a null'ed req object (isaacs)
39 |
40 | #3236: http: Refactor ClientRequest.onSocket (isaacs)
41 |
42 |
Source Code: https://nodejs.org/dist/v0.6.18/node-v0.6.18.tar.gz 44 | 45 |
46 |Windows Installer: https://nodejs.org/dist/v0.6.18/node-v0.6.18.msi 47 | 48 |
49 |Windows x64 Files: https://nodejs.org/dist/v0.6.18/x64/ 50 | 51 |
52 |Macintosh Installer (Universal): https://nodejs.org/dist/v0.6.18/node-v0.6.18.pkg 53 | 54 |
55 |Other release files: https://nodejs.org/dist/v0.6.18/ 56 | 57 |
58 |Website: https://nodejs.org/docs/v0.6.18/ 59 | 60 |
61 |Documentation: https://nodejs.org/docs/v0.6.18/api/ 62 |
63 | -------------------------------------------------------------------------------- /nodejs.org/locale/uk/blog/release/v0.6.2.md: -------------------------------------------------------------------------------- 1 | --- 2 | version: 0.6.2 3 | title: Node v0.6.2 4 | author: bennoordhuis 5 | date: 2011-11-18T23:35:32.000Z 6 | status: publish 7 | category: release 8 | slug: node-v0-6-2 9 | layout: blog-post.hbs 10 | --- 11 | 12 |2011.11.18, Version 0.6.2 (stable)
13 |-
14 |
- doc improvements (Artur Adib, Trevor Burnham, Ryan Emery, Trent Mick) 15 |
- timers: remember extra setTimeout() arguments when timeout==0 16 |
- punycode: use Mathias Bynens's punycode library, it's more compliant 17 |
- repl: improved tab completion (Ryan Emery) 18 |
- buffer: fix range checks in .writeInt() functions (Lukasz Walukiewicz) 19 |
- tls: make cipher list configurable 20 |
- addons: make Buffer and ObjectWrap visible to Windows add-ons (Bert Belder) 21 |
- crypto: add PKCS#1 a.k.a RSA public key verification support 22 |
- windows: fix stdout writes when redirected to nul 23 |
- sunos: fix build on Solaris and Illumos 24 |
- Upgrade V8 to 3.6.6.8 25 |
Source Code: https://nodejs.org/dist/v0.6.2/node-v0.6.2.tar.gz
27 |Windows Installer: https://nodejs.org/dist/v0.6.2/node-v0.6.2.msi
28 |Macintosh Installer: https://nodejs.org/dist/v0.6.2/node-v0.6.2.pkg
29 |Website: https://nodejs.org/docs/v0.6.2/
30 |Documentation: https://nodejs.org/docs/v0.6.2/api/
31 | -------------------------------------------------------------------------------- /nodejs.org/locale/uk/blog/release/v0.6.20.md: -------------------------------------------------------------------------------- 1 | --- 2 | version: 0.6.20 3 | title: Version 0.6.20 (maintenance) 4 | category: release 5 | slug: node-v0-6-20-maintenance 6 | date: 2012-07-10T16:00:00.000Z 7 | layout: blog-post.hbs 8 | --- 9 | 10 | 2012.07.10 Version 0.6.20 (maintenance) 11 | 12 | * npm: Upgrade to 1.1.37 (isaacs) 13 | 14 | * benchmark: Backport improvements made in master (isaacs) 15 | 16 | * build: always link with -lz (Trent Mick) 17 | 18 | * core: use proper #include directives (Ben Noordhuis) 19 | 20 | * cluster: don't silently drop messages when the write queue gets big (Bert Belder) 21 | 22 | * windows: don't print error when GetConsoleTitleW returns an empty string (Bert Belder) 23 | 24 | 25 | Source Code: https://nodejs.org/dist/v0.6.20/node-v0.6.20.tar.gz 26 | 27 | Windows Installer: https://nodejs.org/dist/v0.6.20/node-v0.6.20.msi 28 | 29 | Windows x64 Files: https://nodejs.org/dist/v0.6.20/x64/ 30 | 31 | Macintosh Installer (Universal): https://nodejs.org/dist/v0.6.20/node-v0.6.20.pkg 32 | 33 | Other release files: https://nodejs.org/dist/v0.6.20/ 34 | 35 | Website: https://nodejs.org/docs/v0.6.20/ 36 | 37 | Documentation: https://nodejs.org/docs/v0.6.20/api/ 38 | 39 | Shasums: 40 | 41 | ``` 42 | 5029f30e6af79e7a9a1d45396afbe20229059b47 node-v0.6.20.msi 43 | 370105015bae2a77e4da41564ad3df8fcd0acaec node-v0.6.20.pkg 44 | 91da1dde9badd5250f3d4829c47757de0caab84b node-v0.6.20.tar.gz 45 | efa29addd716c175d945ade5dfa2b9ebd7f6fed8 node.exe 46 | aab0e367adcc9fdee479dbe67a32c6b27ee35960 node.exp 47 | ce6c455937f96eb671f44dc731d628849fa8b350 node.lib 48 | a8db5c269de9c3059684f9aa3de5a4cdbd9b3d12 node.pdb 49 | 22f97ba2c678b4c8a1def251269920ee46c90bca x64/node-v0.6.20.msi 50 | 276136ae7f6e2e59d0ae26d434e4d6ab65769957 x64/node.exe 51 | af56811749aa4fe013a36f7bccecfb94587c0afd x64/node.exp 52 | a629af1b4f6f4b82e332c35695fff956bd555f3b x64/node.lib 53 | 3b2d22b20efeb06bf3d86378168d604dbe52eb08 x64/node.pdb 54 | ``` 55 | -------------------------------------------------------------------------------- /nodejs.org/locale/uk/blog/release/v0.6.21.md: -------------------------------------------------------------------------------- 1 | --- 2 | version: 0.6.21 3 | title: Version 0.6.21 (maintenance) 4 | category: release 5 | slug: node-v0-6-21-maintenance 6 | date: 2012-08-03T21:44:02.000Z 7 | layout: blog-post.hbs 8 | --- 9 | 10 | 2012.08.03 Version 0.6.21 (maintenance) 11 | 12 | * sunos: work around OS bug to prevent fs.watch() from spinning (Bryan Cantrill) 13 | 14 | * net: make pause/resume work with connecting sockets (Bert Belder) 15 | 16 | 17 | Source Code: https://nodejs.org/dist/v0.6.21/node-v0.6.21.tar.gz 18 | 19 | Windows Installer: https://nodejs.org/dist/v0.6.21/node-v0.6.21.msi 20 | 21 | Windows x64 Files: https://nodejs.org/dist/v0.6.21/x64/ 22 | 23 | Macintosh Installer (Universal): https://nodejs.org/dist/v0.6.21/node-v0.6.21.pkg 24 | 25 | Other release files: https://nodejs.org/dist/v0.6.21/ 26 | 27 | Website: https://nodejs.org/docs/v0.6.21/ 28 | 29 | Documentation: https://nodejs.org/docs/v0.6.21/api/ 30 | 31 | Shasums: 32 | 33 | ``` 34 | 04f58b0da23c3db291d84ac55a924332ad83c427 node-v0.6.21.pkg 35 | 31f564bf34c64b07cae3b9a88a87b4a08bab4dc5 node-v0.6.21.tar.gz 36 | 1e3184fe2cfe7140a88b5dcc9c2ec7d32f1f5af5 node.exe 37 | b8887a056152622c08ee10f5867bd27910260477 node.exp 38 | c6468ffe2e145e7db1bb3e2d66adb9f5d50271ad node.lib 39 | 2a896bcb7c83f2fa710650116580daf4ac5e6c4c node.msi 40 | 207441e8c3dc184c478367b775dc7ece1ee36501 node.pdb 41 | 715ad9946db5f97c54a53bdea6bbe9ba69f2f299 x64/node.exe 42 | 2fa2c2d82fedeec1ed8be5d908b790f473d4a7c2 x64/node.exp 43 | b403cb71d4cf21e97a78d446403cedc9795bcf69 x64/node.lib 44 | ef47520dbc6a1a68ec37d290c421031cfd670048 x64/node.msi 45 | fb15e3991c420f3ae67ade92b11b07bb9112124a x64/node.pdb 46 | ``` 47 | -------------------------------------------------------------------------------- /nodejs.org/locale/uk/blog/release/v0.6.3.md: -------------------------------------------------------------------------------- 1 | --- 2 | version: 0.6.3 3 | title: Node v0.6.3 4 | author: piscisaureus 5 | date: 2011-11-25T10:54:08.000Z 6 | status: publish 7 | category: release 8 | slug: node-v0-6-3 9 | layout: blog-post.hbs 10 | --- 11 | 12 | 2011.11.25, Version 0.6.3 (stable) 13 |-
14 |
- #2083 Land NPM in Node. It is included in packages/installers and installed on `make install`. 15 |
- #2076 Add logos to windows installer. 16 |
- #1711 Correctly handle http requests without headers. (Ben Noordhuis, Felix Geisendörfer) 17 |
- TLS: expose more openssl SSL context options and constants. (Ben Noordhuis) 18 |
- #2177 Windows: don't kill UDP socket when a packet fails to reach its destination. (Bert Belder) 19 |
- Windows: support paths longer than 260 characters. (Igor Zinkovsky) 20 |
- Windows: correctly resolve drive-relative paths. (Bert Belder) 21 |
- #2166 Don't leave file descriptor open after lchmod. (Isaac Schlueter) 22 |
- #2084 Add OS X .pkg build script to make file. 23 |
- #2160 Documentation improvements. (Ben Noordhuis) 24 |
-
14 |
- doc improvements (Kyle Young, Tim Oxley, Roman Shtylman, Mathias Bynens) 15 |
- upgrade bundled npm (Isaac Schlueter) 16 |
- polish Windows installer (Igor Zinkovsky, Isaac Schlueter) 17 |
- punycode: upgrade to v0.2.1 (Mathias Bynens) 18 |
- build: add --without-npm flag to configure script 19 |
- sys: deprecate module some more, print stack trace if NODE_DEBUG=sys 20 |
- cli: add -p switch, prints result of --eval 21 |
- #1997: fix Blowfish ECB encryption and decryption (Ingmar Runge) 22 |
- #2223: fix socket 'close' event being emitted twice 23 |
- #2224: fix RSS memory usage > 4 GB reporting (Russ Bradberry) 24 |
- #2225: fix util.inspect() object stringification bug (Nathan Rajlich) 25 |
- npm workaround Windows antivirus software (isaacs) 14 |
- Upgrade V8 to 3.6.6.11
-
15 |
- npm update to 1.1.0-beta-4 (Isaac Z. Schlueter) 16 |
- cli: fix output of --help (Ben Noordhuis) 17 |
- new website 18 |
- pause/resume semantics for stdin (Isaac Z. Schlueter) 19 |
- Travis CI integration (Maciej Małecki) 20 |
- child_process: Fix bug regarding closed stdin (Ben Noordhuis) 21 |
- Enable upgrades in MSI. (Igor Zinkovsky) 22 |
- net: Fixes memory leak (Ben Noordhuis) 23 |
- fs: handle fractional or NaN ReadStream buffer size (Ben Noordhuis) 24 |
- crypto: fix memory leaks in PBKDF2 error path (Ben Noordhuis) 25 |
2012.01.06, Version 0.6.7 (stable)
13 | 14 |-
15 |
V8 hash collision fix (Breaks MIPS) (Bert Belder, Erik Corry)
16 | Upgrade V8 to 3.6.6.15
17 | Upgrade npm to 1.1.0-beta-10 (isaacs)
18 | many doc updates (Ben Noordhuis, Jeremy Martin, koichik, Dave Irvine, 19 | Seong-Rak Choi, Shannen, Adam Malcontenti-Wilson, koichik)
20 | Fix segfault in
node_http_parser.cc
21 | dgram, timers: fix memory leaks (Ben Noordhuis, Yoshihiro Kikuchi)
22 | repl: fix repl.start not passing the
ignoreUndefinedarg (Damon Oehlman)
23 | #1980: Socket.pause null reference when called on a closed Stream (koichik)
24 | #2263: XMLHttpRequest piped in a writable file stream hang (koichik)
25 | #2069: http resource leak (koichik)
26 | buffer.readInt global pollution fix (Phil Sung)
27 | timers: fix performance regression (Ben Noordhuis)
28 | #2308, #2246: node swallows openssl error on request (koichik)
29 | #2114: timers: remove _idleTimeout from item in .unenroll() (James Hartig)
30 | #2379: debugger: Request backtrace w/o refs (Fedor Indutny)
31 | simple DTrace ustack helper (Dave Pacheco)
32 | crypto: rewrite HexDecode without snprintf (Roman Shtylman)
33 | crypto: don’t ignore DH init errors (Ben Noordhuis)
34 |
Source Code: https://nodejs.org/dist/v0.6.7/node-v0.6.7.tar.gz
37 | 38 |Windows Installer: https://nodejs.org/dist/v0.6.7/node-v0.6.7.msi
39 | 40 |Macintosh Installer: https://nodejs.org/dist/v0.6.7/node-v0.6.7.pkg
41 | 42 |Website: https://nodejs.org/docs/v0.6.7/
43 | 44 |Documentation: https://nodejs.org/docs/v0.6.7/api/
45 | -------------------------------------------------------------------------------- /nodejs.org/locale/uk/blog/release/v0.6.8.md: -------------------------------------------------------------------------------- 1 | --- 2 | version: 0.6.8 3 | title: Node v0.6.8 4 | author: Isaac Schlueter 5 | date: 2012-01-20T03:59:53.000Z 6 | status: publish 7 | category: release 8 | slug: node-v0-6-8 9 | layout: blog-post.hbs 10 | --- 11 | 12 |2012.01.19, Version 0.6.8 (stable)
13 | 14 |-
15 |
Update V8 to 3.6.6.19
16 | Numeric key hash collision fix for V8 (Erik Corry, Fedor Indutny)
17 | Add missing TTY key translations for F1-F5 on Windows (Brandon Benvie)
18 | path.extname bugfix with . and .. paths (Bert Belder)
19 | cluster: don't always kill the master on uncaughtException (Ben Noordhuis)
20 | Update npm to 1.1.0-2 (isaacs)
21 | typed arrays: set class name (Ben Noordhuis)
22 | zlib binding cleanup (isaacs, Bert Belder)
23 | dgram: use slab memory allocator (Michael Bernstein)
24 | fix segfault #2473
25 | #2521 60% improvement in fs.stat on Windows (Igor Zinkovsky)
26 |
Source Code: https://nodejs.org/dist/v0.6.8/node-v0.6.8.tar.gz
27 | 28 |Windows Installer: https://nodejs.org/dist/v0.6.8/node-v0.6.8.msi
29 | 30 |Macintosh Installer: https://nodejs.org/dist/v0.6.8/node-v0.6.8.pkg
31 | 32 |Website: https://nodejs.org/docs/v0.6.8/
33 | 34 |Documentation: https://nodejs.org/docs/v0.6.8/api/
35 | -------------------------------------------------------------------------------- /nodejs.org/locale/uk/blog/release/v0.6.9.md: -------------------------------------------------------------------------------- 1 | --- 2 | version: 0.6.9 3 | title: Node v0.6.9 4 | author: Isaac Schlueter 5 | date: 2012-01-28T00:58:18.000Z 6 | status: publish 7 | category: release 8 | slug: node-v0-6-9 9 | layout: blog-post.hbs 10 | --- 11 | 12 |2012.01.27, Version 0.6.9 (stable)
13 | 14 |-
15 |
-
16 |
dgram: Bring back missing functionality for Unix (Dan VerWeire, 17 | Roman Shtylman, Ben Noordhuis)
18 |- Note: Windows UDP support not yet complete.
19 | http: Fix parser memory leak (koichik)
20 | zlib: Fix #2365 crashes on invalid input (Nicolas LaCasse)
21 | module: fix --debug-brk on symlinked scripts (Fedor Indutny)
22 | Documentation Restyling (Matthew Fitzsimmons)
23 | Update npm to 1.1.0-3 (isaacs)
24 | Windows: fix regression in stat() calls to C:\ (Bert Belder)
25 |
Source Code: https://nodejs.org/dist/v0.6.9/node-v0.6.9.tar.gz
26 | 27 |Windows Installer: https://nodejs.org/dist/v0.6.9/node-v0.6.9.msi
28 | 29 |Macintosh Installer: https://nodejs.org/dist/v0.6.9/node-v0.6.9.pkg
30 | 31 |Website: https://nodejs.org/docs/v0.6.9/
32 | 33 |Documentation: https://nodejs.org/docs/v0.6.9/api/
34 | -------------------------------------------------------------------------------- /nodejs.org/locale/uk/blog/release/v0.7.0.md: -------------------------------------------------------------------------------- 1 | --- 2 | version: 0.7.0 3 | title: Node v0.7.0 (Unstable) 4 | author: ryandahl 5 | date: 2012-01-17T03:58:28.000Z 6 | status: publish 7 | category: release 8 | slug: node-v0-7-0-unstable 9 | layout: blog-post.hbs 10 | --- 11 | 12 | This is the first release in the unstable v0.7 series. Almost all users will want to remain using the stable v0.6 releases. 13 | 14 | 2012.01.16, Version 0.7.0 (unstable) 15 |-
16 |
- Upgrade V8 to 3.8.6 17 |
- Use GYP build system on unix (Ben Noordhuis) 18 |
- Experimental isolates support (Ben Noordhuis) 19 |
- Improvements to Cluster API (Andreas Madsen) 20 |
- Use isolates for internal debugger (Fedor Indutny) 21 |
- Bug fixes
2012.01.23, Version 0.7.1 (unstable)
13 | 14 |-
15 |
Update V8 to 3.8.8
16 | Install node-waf by default (Fedor Indutny)
17 | crypto: Add ability to turn off PKCS padding (Ingmar Runge)
18 | v8: implement VirtualMemory class on SunOS (Ben Noordhuis)
19 | Add cluster.setupMaster (Andreas Madsen)
20 | move
path.exists*tofs.exists*(Maciej Małecki)
21 | typed arrays: set class name (Ben Noordhuis)
22 | libuv bug fixes (Igor Zinkovsky, Ben Noordhuis, Dan VerWeire)
23 |
Source: https://nodejs.org/dist/v0.7.1/node-v0.7.1.tar.gz
26 | 27 |Windows Installer: https://nodejs.org/dist/v0.7.1/node-v0.7.1.msi
28 | 29 |Macintosh Installer: https://nodejs.org/dist/v0.7.1/node-v0.7.1.pkg
30 | 31 |Website: https://nodejs.org/docs/v0.7.1/
32 | 33 |Documentation: https://nodejs.org/docs/v0.7.1/api/
34 | -------------------------------------------------------------------------------- /nodejs.org/locale/uk/blog/release/v0.7.2.md: -------------------------------------------------------------------------------- 1 | --- 2 | version: 0.7.2 3 | title: Node v0.7.2 (unstable) 4 | author: Isaac Schlueter 5 | date: 2012-02-01T21:13:04.000Z 6 | status: publish 7 | category: release 8 | slug: node-v0-7-2-unstable 9 | layout: blog-post.hbs 10 | --- 11 | 12 |2012.02.01, Version 0.7.2 (unstable)
13 | 14 |-
15 |
Update V8 to 3.8.9
16 | Support for sharing streams across Isolates (Igor Zinkovsky)
17 | #2636 - Fix case where http_parsers are freed too early (koichik)
18 | url: Support for IPv6 addresses in URLs (Łukasz Walukiewicz)
19 | child_process: Add disconnect() method to child processes (Andreas Madsen)
20 | fs: add O_EXCL support, exclusive open file (Ben Noordhuis)
21 | fs: more specific error messages (Tj Holowaychuk)
22 | tty: emit 'unknown' key event if key sequence not found (Dan VerWeire, Nathan Rajlich)
23 | build: compile release build too if BUILDTYPE=Debug (Ben Noordhuis)
24 | module: fix --debug-brk on symlinked scripts (Fedor Indutny)
25 | zlib: fix
Failed to set dictionaryissue (Fedor Indutny)
26 | waf: predict target arch for OS X (Fedor Indutny)
27 |
Source Code: https://nodejs.org/dist/v0.7.2/node-v0.7.2.tar.gz
28 | 29 |Windows Installer: https://nodejs.org/dist/v0.7.2/node-v0.7.2.msi
30 | 31 |Macintosh Installer: https://nodejs.org/dist/v0.7.2/node-v0.7.2.pkg
32 | 33 |Website: https://nodejs.org/docs/v0.7.2/
34 | 35 |Documentation: https://nodejs.org/docs/v0.7.2/api/
36 | -------------------------------------------------------------------------------- /nodejs.org/locale/uk/blog/release/v0.7.3.md: -------------------------------------------------------------------------------- 1 | --- 2 | version: 0.7.3 3 | title: Node v0.7.3 (unstable) 4 | author: Isaac Schlueter 5 | date: 2012-02-08T01:08:27.000Z 6 | status: publish 7 | category: release 8 | slug: node-v0-7-3 9 | layout: blog-post.hbs 10 | --- 11 | 12 |2012.02.07, Version 0.7.3 (unstable) 13 | 14 |
15 |-
16 |
Upgrade V8 to 3.9.2
17 |
18 | Revert support for isolates. (Ben Noordhuis)
19 |
20 | cluster: Cleanup docs, event handling, and process.disconnect (Andreas Madsen)
21 |
22 | gyp_addon: link with node.lib on Windows (Nathan Rajlich)
23 |
24 | http: fix case where http-parser is freed twice (koichik)
25 |
26 | Windows: disable RTTI and exceptions (Bert Belder)
27 |
28 |
Source Code: https://nodejs.org/dist/v0.7.3/node-v0.7.3.tar.gz 30 | 31 |
32 |Windows Installer: https://nodejs.org/dist/v0.7.3/node-v0.7.3.msi 33 | 34 |
35 |Macintosh Installer: https://nodejs.org/dist/v0.7.3/node-v0.7.3.pkg 36 | 37 |
38 |Website: https://nodejs.org/docs/v0.7.3/ 39 | 40 |
41 |Documentation: https://nodejs.org/docs/v0.7.3/api/ 42 |
43 | -------------------------------------------------------------------------------- /nodejs.org/locale/uk/blog/release/v0.7.4.md: -------------------------------------------------------------------------------- 1 | --- 2 | version: 0.7.4 3 | title: Node v0.7.4 (unstable) 4 | author: Isaac Schlueter 5 | date: 2012-02-15T19:38:35.000Z 6 | status: publish 7 | category: release 8 | slug: version-0-7-4-unstable 9 | layout: blog-post.hbs 10 | --- 11 | 12 |2012.02.14, Version 0.7.4 (unstable) 13 | 14 |
15 |-
16 |
Upgrade V8 to 3.9.5
17 |
18 | Upgrade npm to 1.1.1
19 |
20 | build: Detect host_arch better (Karl Skomski)
21 |
22 | debugger: export
23 |debug_porttoprocess(Fedor Indutny)
24 | api docs: CSS bug fixes (isaacs)
25 |
26 | build: use -fPIC for native addons on UNIX (Nathan Rajlich)
27 |
28 | Re-add top-level v8::Locker (Marcel Laverdet)
29 |
30 | Move images out of the dist tarballs (isaacs)
31 |
32 | libuv: Remove uv_export and uv_import (Ben Noordhuis)
33 |
34 | build: Support x64 build on Windows (Igor Zinkovsky)
35 |
36 |
Source Code: https://nodejs.org/dist/v0.7.4/node-v0.7.4.tar.gz 38 | 39 |
40 |Windows Installer: https://nodejs.org/dist/v0.7.4/node-v0.7.4.msi 41 | 42 |
43 |Macintosh Installer: https://nodejs.org/dist/v0.7.4/node-v0.7.4.pkg 44 | 45 |
46 |Other release files: https://nodejs.org/dist/v0.7.4/ 47 | 48 |
49 |Website: https://nodejs.org/docs/v0.7.4/ 50 | 51 |
52 |Documentation: https://nodejs.org/docs/v0.7.4/api/ 53 |
54 | -------------------------------------------------------------------------------- /nodejs.org/locale/uk/blog/release/v0.7.5.md: -------------------------------------------------------------------------------- 1 | --- 2 | version: 0.7.5 3 | title: Version 0.7.5 (unstable) 4 | author: Isaac Schlueter 5 | date: 2012-02-23T22:45:21.000Z 6 | status: publish 7 | category: release 8 | slug: version-0-7-5-unstable 9 | layout: blog-post.hbs 10 | --- 11 | 12 |2012.02.23, Version 0.7.5 (unstable) 13 | 14 |
15 |-
16 |
startup speed improvements (Maciej Małecki)
17 |
18 | crypto: add function getDiffieHellman() (Tomasz Buchert)
19 |
20 | buffer: support decoding of URL-safe base64 (Ben Noordhuis)
21 |
22 | Make QueryString.parse() even faster (Brian White)
23 |
24 | url: decode url entities in auth section (Ben Noordhuis)
25 |
26 | http: support PURGE request method (Ben Noordhuis)
27 |
28 | http: Generate Date headers on responses (Mark Nottingham)
29 |
30 | Fix #2762: Add callback to close function. (Mikeal Rogers)
31 |
32 | dgram: fix out-of-bound memory read (Ben Noordhuis)
33 |
34 | repl: add automatic loading of built-in libs (Brandon Benvie)
35 |
36 | repl: remove double calls where possible (Fedor Indutny)
37 |
38 | Readline improvements. Related: #2737 #2756 (Colton Baker)
39 |
40 | build: disable -fomit-frame-pointer on solaris (Dave Pacheco)
41 |
42 | build: arch detection improvements (Nathan Rajlich)
43 |
44 | build: Make a fat binary for the OS X
45 |make pkg. (Nathan Rajlich)
46 | jslint src/ and lib/ on 'make test' (isaacs)
47 |
48 |
Source Code: https://nodejs.org/dist/v0.7.5/node-v0.7.5.tar.gz 50 | 51 |
52 |Windows Installer: https://nodejs.org/dist/v0.7.5/node-v0.7.5.msi 53 | 54 |
55 |Macintosh Installer: https://nodejs.org/dist/v0.7.5/node-v0.7.5.pkg 56 | 57 |
58 |Other release files: https://nodejs.org/dist/v0.7.5/ 59 | 60 |
61 |Website: https://nodejs.org/docs/v0.7.5/ 62 | 63 |
64 |Documentation: https://nodejs.org/docs/v0.7.5/api/ 65 |
66 | -------------------------------------------------------------------------------- /nodejs.org/locale/uk/blog/release/v0.8.4.md: -------------------------------------------------------------------------------- 1 | --- 2 | category: release 3 | date: 2012-07-25T17:21:16.176Z 4 | version: 0.8.4 5 | title: Version 0.8.4 (Stable) 6 | slug: node-v0-8-4-stable 7 | layout: blog-post.hbs 8 | --- 9 | 10 | 2012.07.25, Version 0.8.4 (Stable) 11 | 12 | * V8: Upgrade to 3.11.10.17 13 | 14 | * npm: Upgrade to 1.1.45 15 | 16 | * net: fix Socket({ fd: 42 }) api (Ben Noordhuis) 17 | 18 | * readline: Remove event listeners on close (isaacs) 19 | 20 | * windows: correctly prep long path for fs.exists(Sync) (Bert Belder) 21 | 22 | * debugger: wake up the event loop when a debugger command is dispatched (Peter Rybin) 23 | 24 | * tls: verify server's identity (Fedor Indutny) 25 | 26 | * net: ignore socket.setTimeout(Infinity or NaN) (Fedor Indutny) 27 | 28 | 29 | Source Code: https://nodejs.org/dist/v0.8.4/node-v0.8.4.tar.gz 30 | 31 | Macintosh Installer (Universal): https://nodejs.org/dist/v0.8.4/node-v0.8.4.pkg 32 | 33 | Windows Installer: https://nodejs.org/dist/v0.8.4/node-v0.8.4-x86.msi 34 | 35 | Windows x64 Installer: https://nodejs.org/dist/v0.8.4/x64/node-v0.8.4-x64.msi 36 | 37 | Windows x64 Files: https://nodejs.org/dist/v0.8.4/x64/ 38 | 39 | Other release files: https://nodejs.org/dist/v0.8.4/ 40 | 41 | Website: https://nodejs.org/docs/v0.8.4/ 42 | 43 | Documentation: https://nodejs.org/docs/v0.8.4/api/ 44 | 45 | Shasums: 46 | 47 | ``` 48 | 387d7ac58d79dac301960510dfb7ee96fbf39072 node-v0.8.4-x86.msi 49 | 66687da0ef190e8c07d5499ae3c408a6cca7ac30 node-v0.8.4.pkg 50 | 8473e3dd48ab3734e2c92de0518cb80c2cdf750f node-v0.8.4.tar.gz 51 | 724ec6dc5e86805bfac79c8a702638c353850ea3 node.exe 52 | 9bf483f72ad7884988d0678f7dc5bc000f4d21d2 node.exp 53 | 3b7bd3915b62896e5c2f5701fd5d1c7fb53cdd27 node.lib 54 | 9c3079ee727d471cef9fd91c7067d0a72349bfcb node.pdb 55 | 236a693074f2c69157e2918d1342a7850fc939ca npm-1.1.45.tgz 56 | 7126700cb321f688901e7773785eb88274906d50 npm-1.1.45.zip 57 | e9f414ba043f1daa5eee65506ef33c5377d87a09 x64/node-v0.8.4-x64.msi 58 | 4cc86f21285b7f3d3cbd594ba604f06fb3434502 x64/node.exe 59 | 6bf207a6b587bf1b01f18e9d0f2eefb528d82c2f x64/node.exp 60 | e7b0d65992324b0688c61f6e534f3527e7e0b59f x64/node.lib 61 | 9a0072f528f9055531dee2bfa991882836b235de x64/node.pdb 62 | ``` 63 | -------------------------------------------------------------------------------- /nodejs.org/locale/uk/blog/release/v0.9.0.md: -------------------------------------------------------------------------------- 1 | --- 2 | category: release 3 | version: 0.9.0 4 | date: 2012-07-20T18:37:15.000Z 5 | title: Version 0.9.0 (Unstable) 6 | slug: version-0-9-0-unstable 7 | layout: blog-post.hbs 8 | --- 9 | 10 | 2012.07.20, Version 0.9.0 (Unstable) 11 | 12 | * punycode: update to v1.1.1 (Mathias Bynens) 13 | 14 | * c-ares: upgrade to 1.9.0 (Saúl Ibarra Corretgé) 15 | 16 | * dns: ignore rogue DNS servers reported by windows (Saúl Ibarra Corretgé) 17 | 18 | * unix: speed up uv_async_send() (Ben Noordhuis) 19 | 20 | * darwin: get cpu model correctly on mac (Xidorn Quan) 21 | 22 | * nextTick: Handle tick callbacks before any other I/O (isaacs) 23 | 24 | * Enable color customization of `util.inspect` (Pavel Lang) 25 | 26 | * tls: Speed and memory improvements (Fedor Indutny) 27 | 28 | * readline: Use one history item for reentered line (Vladimir Beloborodov) 29 | 30 | * Fix #3521 Make process.env more like a regular Object (isaacs) 31 | 32 | 33 | Source Code: https://nodejs.org/dist/v0.9.0/node-v0.9.0.tar.gz 34 | 35 | Macintosh Installer (Universal): https://nodejs.org/dist/v0.9.0/node-v0.9.0.pkg 36 | 37 | Windows Installer: https://nodejs.org/dist/v0.9.0/node-v0.9.0-x86.msi 38 | 39 | Windows x64 Installer: https://nodejs.org/dist/v0.9.0/x64/node-v0.9.0-x64.msi 40 | 41 | Windows x64 Files: https://nodejs.org/dist/v0.9.0/x64/ 42 | 43 | Other release files: https://nodejs.org/dist/v0.9.0/ 44 | 45 | Website: https://nodejs.org/docs/v0.9.0/ 46 | 47 | Documentation: https://nodejs.org/docs/v0.9.0/api/ 48 | 49 | Shasums: 50 | 51 | ``` 52 | 4d6881934f5e41da651b478f914f71543d21d3cc node-v0.9.0-x86.msi 53 | ec00cc6f0830f64cd9e8246a299abf9a2a6ed73e node-v0.9.0.pkg 54 | 912d0eb3139b8f6f99199dae5ec1ecb300ed9c9b node-v0.9.0.tar.gz 55 | 7e56dddbb1d3e243549db7182f1bf2dd4518eaae node.exe 56 | 31718ad3e0de9b0ea6c207966a13d4bafaf9ef64 node.exp 57 | 0738b4d91de4c87cdee2547d83144668cb232c24 node.lib 58 | baca86ec3c12a5261abb940cd8107bdeb40713cc node.pdb 59 | cf3892596a7d2a27a63672b537b06b8828125fe9 x64/node-v0.9.0-x64.msi 60 | cad4bf9b2be85476d1a897ea17b3f927ec49c96a x64/node.exe 61 | 29ea3654f7728efef6fa046943ded57af42b91f3 x64/node.exp 62 | 1dfa57b111d5942b4fe701b625176eae73c82d82 x64/node.lib 63 | 9093b2120f8adf0236f965982e4a32697af2af5d x64/node.pdb 64 | ``` 65 | -------------------------------------------------------------------------------- /nodejs.org/locale/uk/blog/uncategorized/an-easy-way-to-build-scalable-network-programs.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: An Easy Way to Build Scalable Network Programs 3 | author: ryandahl 4 | date: 2011-10-04T22:39:56.000Z 5 | status: publish 6 | category: Uncategorized 7 | slug: an-easy-way-to-build-scalable-network-programs 8 | layout: blog-post.hbs 9 | --- 10 | 11 | Suppose you're writing a web server which does video encoding on each file upload. Video encoding is very much compute bound. Some recent blog posts suggest that Node.js would fail miserably at this. 12 | 13 | Using Node does not mean that you have to write a video encoding algorithm in JavaScript (a language without even 64 bit integers) and crunch away in the main server event loop. The suggested approach is to separate the I/O bound task of receiving uploads and serving downloads from the compute bound task of video encoding. In the case of video encoding this is accomplished by forking out to ffmpeg. Node provides advanced means of asynchronously controlling subprocesses for work like this. 14 | 15 | It has also been suggested that Node does not take advantage of multicore machines. Node has long supported load-balancing connections over multiple processes in just a few lines of code - in this way a Node server will use the available cores. In coming releases we'll make it even easier: just pass--balance on the command line and Node will manage the cluster of processes.
16 |
17 | Node has a clear purpose: provide an easy way to build scalable network programs. It is not a tool for every problem. Do not write a ray tracer with Node. Do not write a web browser with Node. Do however reach for Node if tasked with writing a DNS server, DHCP server, or even a video encoding server.
18 |
19 | By relying on the kernel to schedule and preempt computationally expensive tasks and to load balance incoming connections, Node appears less magical than server platforms that employ userland scheduling. So far, our focus on simplicity and transparency has paid off: the number of success stories from developers and corporations who are adopting the technology continues to grow.
20 |
--------------------------------------------------------------------------------
/nodejs.org/locale/uk/blog/uncategorized/bnoordhuis-departure.md:
--------------------------------------------------------------------------------
1 | ---
2 | title: Ben Noordhuis's Departure
3 | date: 2013-12-03T22:13:57.000Z
4 | slug: bnoordhuis-departure
5 | layout: blog-post.hbs
6 | ---
7 |
8 | As of this past weekend, Ben Noordhuis has decided to step away from
9 | Node.js and libuv, and is no longer acting as a core committer.
10 |
11 | Ben has done a tremendous amount of great work in the past. We're sad
12 | to lose the benefit of his continued hard work and expertise, and
13 | extremely grateful for what he has added to Node.js and libuv over the
14 | years.
15 |
16 | Many of you already have expressed your opinion regarding recent
17 | drama, and I'd like to ask that you please respect our wishes to let
18 | this issue rest, so that we can all focus on the road forward.
19 |
20 | Thanks.
21 |
--------------------------------------------------------------------------------
/nodejs.org/locale/uk/blog/uncategorized/development-environment.md:
--------------------------------------------------------------------------------
1 | ---
2 | title: Development Environment
3 | author: ryandahl
4 | date: 2011-04-05T03:16:27.000Z
5 | status: publish
6 | category: Uncategorized
7 | slug: development-environment
8 | layout: blog-post.hbs
9 | ---
10 |
11 | If you're compiling a software package because you need a particular version (e.g. the latest), then it requires a little bit more maintenance than using a package manager like dpkg. Software that you compile yourself should *not* go into /usr, it should go into your home directory. This is part of being a software developer.
12 |
13 | One way of doing this is to install everything into $HOME/local/$PACKAGE. Here is how I install node on my machine:./configure --prefix=$HOME/local/node-v0.4.5 && make install14 | 15 | To have my paths automatically set I put this inside my
$HOME/.zshrc:PATH="$HOME/local/bin:/opt/local/bin:/usr/bin:/sbin:/bin"
16 | LD_LIBRARY_PATH="/opt/local/lib:/usr/local/lib:/usr/lib"
17 | for i in $HOME/local/*; do
18 | [ -d $i/bin ] && PATH="${i}/bin:${PATH}"
19 | [ -d $i/sbin ] && PATH="${i}/sbin:${PATH}"
20 | [ -d $i/include ] && CPATH="${i}/include:${CPATH}"
21 | [ -d $i/lib ] && LD_LIBRARY_PATH="${i}/lib:${LD_LIBRARY_PATH}"
22 | [ -d $i/lib/pkgconfig ] && PKG_CONFIG_PATH="${i}/lib/pkgconfig:${PKG_CONFIG_PATH}"
23 | [ -d $i/share/man ] && MANPATH="${i}/share/man:${MANPATH}"
24 | done
25 |
26 | Node is under sufficiently rapid development that everyone should be compiling it themselves. A corollary of this is that npm (which should be installed alongside Node) does not require root to install packages.
27 |
28 | CPAN and RubyGems have blurred the lines between development tools and system package managers. With npm we wish to draw a clear line: it is not a system package manager. It is not for installing firefox or ffmpeg or OpenSSL; it is for rapidly downloading, building, and setting up Node packages. npm is a development tool. When a program written in Node becomes sufficiently mature it should be distributed as a tarball, .deb, .rpm, or other package system. It should not be distributed to end users with npm.
29 |
--------------------------------------------------------------------------------
/nodejs.org/locale/uk/blog/uncategorized/growing-up.md:
--------------------------------------------------------------------------------
1 | ---
2 | title: Growing up
3 | author: ryandahl
4 | date: 2011-12-15T19:59:15.000Z
5 | status: publish
6 | category: Uncategorized
7 | slug: growing-up
8 | layout: blog-post.hbs
9 | ---
10 |
11 | This week Microsoft announced support for Node in Windows Azure, their cloud computing platform. For the Node core team and the community, this is an important milestone. We've worked hard over the past six months reworking Node's machinery to support IO completion ports and Visual Studio to provide a good native port to Windows. The overarching goal of the port was to expand our user base to the largest number of developers. Happily, this has paid off in the form of being a first class citizen on Azure. Many users who would have never used Node as a pure unix tool are now up and running on the Windows platform. More users translates into a deeper and better ecosystem of modules, which makes for a better experience for everyone.
12 |
13 | We also redesigned our website - something that we've put off for a long time because we felt that Node was too nascent to dedicate marketing to it. But now that we have binary distributions for Macintosh and Windows, have bundled npm, and are serving millions of users at various companies, we felt ready to indulge in a new website and share of a few of our success stories on the home page.
14 |
15 | Work is on-going. We continue to improve the software, making performance improvements and adding isolate support, but Node is growing up.
16 |
--------------------------------------------------------------------------------
/nodejs.org/locale/uk/blog/uncategorized/index.md:
--------------------------------------------------------------------------------
1 | ---
2 | title: Uncategorized
3 | layout: category-index.hbs
4 | listing: true
5 | robots: noindex, follow
6 | ---
7 |
--------------------------------------------------------------------------------
/nodejs.org/locale/uk/blog/uncategorized/jobs-nodejs-org.md:
--------------------------------------------------------------------------------
1 | ---
2 | title: jobs.nodejs.org
3 | author: ryandahl
4 | date: 2011-03-25T06:05:22.000Z
5 | status: publish
6 | category: Uncategorized
7 | slug: jobs-nodejs-org
8 | layout: blog-post.hbs
9 | ---
10 |
11 | We are starting an official jobs board for Node. There are two goals for this
12 |
13 | 1. Promote the small emerging economy around this platform by having a central space for employers to find Node programmers.
14 |
15 | 2. Make some money. We work hard to build this platform and taking a small tax for job posts seems a like reasonable "tip jar".
16 |
17 | jobs.nodejs.org
18 |
--------------------------------------------------------------------------------
/nodejs.org/locale/uk/blog/uncategorized/node-meetup-this-thursday.md:
--------------------------------------------------------------------------------
1 | ---
2 | title: Node Meetup this Thursday
3 | author: ryandahl
4 | date: 2011-08-03T04:37:02.000Z
5 | status: publish
6 | category: Uncategorized
7 | slug: node-meetup-this-thursday
8 | layout: blog-post.hbs
9 | ---
10 |
11 | https://nodejs.org/meetup/
12 | http://nodemeetup.eventbrite.com/
13 |
14 | Three companies will describe their distributed Node applications. Sign up soon, space is limited!
15 |
--------------------------------------------------------------------------------
/nodejs.org/locale/uk/blog/uncategorized/node-office-hours-cut-short.md:
--------------------------------------------------------------------------------
1 | ---
2 | title: Node Office Hours Cut Short
3 | author: ryandahl
4 | date: 2011-04-28T16:04:35.000Z
5 | status: publish
6 | category: Uncategorized
7 | slug: node-office-hours-cut-short
8 | layout: blog-post.hbs
9 | ---
10 |
11 | This week office hours are only from 4pm to 6pm. Isaac will be in the Joyent office in SF - everyone else is out of town. Sign up at http://nodeworkup.eventbrite.com/ if you would like to come.
12 |
13 | The week after, Thursday May 5th, we will all be at NodeConf in Portland.
14 |
15 | Normal office hours resume Thursday May 12th.
16 |
--------------------------------------------------------------------------------
/nodejs.org/locale/uk/blog/uncategorized/office-hours.md:
--------------------------------------------------------------------------------
1 | ---
2 | title: Office Hours
3 | author: ryandahl
4 | date: 2011-03-24T04:42:47.000Z
5 | status: publish
6 | category: Uncategorized
7 | slug: office-hours
8 | layout: blog-post.hbs
9 | ---
10 |
11 | Starting next Thursday Isaac, Tom, and I will be holding weekly office hours at Joyent HQ in San Francisco. Office hours are meant to be subdued working time - there are no talks and no alcohol. Bring your bugs or just come and hack with us.
12 |
13 | Our building requires that everyone attending be on a list so you must sign up at Event Brite.
14 |
15 | We start at 4p and end promptly at 8p.
16 |
--------------------------------------------------------------------------------
/nodejs.org/locale/uk/blog/uncategorized/porting-node-to-windows-with-microsofts-help.md:
--------------------------------------------------------------------------------
1 | ---
2 | title: Porting Node to Windows With Microsoft’s Help
3 | author: ryandahl
4 | date: 2011-06-23T22:22:58.000Z
5 | status: publish
6 | category: Uncategorized
7 | slug: porting-node-to-windows-with-microsofts-help
8 | layout: blog-post.hbs
9 | ---
10 |
11 | I'm pleased to announce that Microsoft is partnering with Joyent in formally contributing resources towards porting Node to Windows. As you may have heard in a talk we gave earlier this year, we have started the undertaking of a native port to Windows - targeting the high-performance IOCP API.
12 |
13 | This requires a rather large modification of the core structure, and we're very happy to have official guidance and engineering resources from Microsoft. Rackspace is also contributing Bert Belder's time to this undertaking.
14 |
15 | The result will be an official binary node.exe releases on nodejs.org, which will work on Windows Azure and other Windows versions as far back as Server 2003.
16 |
--------------------------------------------------------------------------------
/nodejs.org/locale/uk/blog/uncategorized/some-new-node-projects.md:
--------------------------------------------------------------------------------
1 | ---
2 | title: Some New Node Projects
3 | author: ryandahl
4 | date: 2011-08-29T15:30:41.000Z
5 | status: publish
6 | category: Uncategorized
7 | slug: some-new-node-projects
8 | layout: blog-post.hbs
9 | ---
10 |
11 | -
12 |
- Superfeedr released a Node XMPP Server. "Since astro had been doing an amazing work with his node-xmpp library to build Client, Components and even Server to server modules, the logical next step was to try to build a Client to Server module so that we could have a full blown server. That’s what we worked on the past couple days, and it’s now on Github! 13 | 14 |
- Joyent's Mark Cavage released LDAP.js. "ldapjs is a pure JavaScript, from-scratch framework for implementing LDAP clients and servers in Node.js. It is intended for developers used to interacting with HTTP services in node and express. 15 | 16 |
- Microsoft's Tomasz Janczuk released iisnode "The iisnode project provides a native IIS 7.x module that allows hosting of node.js applications in IIS.
Scott Hanselman posted a detailed walkthrough of how to get started with iisnode 17 | -------------------------------------------------------------------------------- /nodejs.org/locale/uk/blog/uncategorized/the-videos-from-node-meetup.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: The Videos from the Meetup 3 | author: ryandahl 4 | date: 2011-08-12T07:14:34.000Z 5 | status: publish 6 | category: Uncategorized 7 | slug: the-videos-from-node-meetup 8 | layout: blog-post.hbs 9 | --- 10 | 11 | Uber, Voxer, and Joyent described how they use Node in production 12 | 13 | http://www.joyent.com/blog/node-js-meetup-distributed-web-architectures/ 14 | -------------------------------------------------------------------------------- /nodejs.org/locale/uk/blog/uncategorized/trademark.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Trademark 3 | author: ryandahl 4 | date: 2011-04-29T08:54:18.000Z 5 | status: publish 6 | category: Uncategorized 7 | slug: trademark 8 | layout: blog-post.hbs 9 | --- 10 | 11 | One of the things Joyent accepted when we took on the Node project was to provide resources to help the community grow. The Node project is amazing because of the expertise, dedication and hard work of the community. However in all communities there is the possibility of people acting inappropriately. We decided to introduce trademarks on the “Node.js” and the “Node logo” in order to ensure that people or organisations who are not investing in the Node community misrepresent, or create confusion about the role of themselves or their products with Node. 12 | 13 | We are big fans of the people who have contributed to Node and we have worked hard to make sure that existing members of the community will be unaffected by this change. For most people they don’t have to do anything they are free to use the Node.js marks in their free open source projects (see guidelines). For others we’ve already granted them licenses to use Node.js marks in their domain names and their businesses. We value all of these contributions to the Node community and hope that we can continue to protect their good names and hard work. 14 | 15 | Where does our trademark policy come from? We started by looking at popular open source foundations like the Apache Software Foundation and Linux. By strongly basing our policy on the one used by the Apache Software Foundation we feel that we’ve created a policy which is liberal enough to allow the open source community to easily make use of the mark in the context of free open source software, but secure enough to protect the community’s work from being misrepresented by other organisations. 16 | 17 | While we realize that any changes involving lawyers can be intimidating to the community we want to make this transition as smoothly as possible and welcome your questions and feedback on the policy and how we are implementing it. 18 | 19 | trademark-policy.pdf 20 | trademark@joyent.com 21 | -------------------------------------------------------------------------------- /nodejs.org/locale/uk/blog/uncategorized/version-0-6.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Version 0.6 Coming Soon 3 | author: ryandahl 4 | date: 2011-10-25T22:26:23.000Z 5 | status: publish 6 | category: Uncategorized 7 | slug: version-0-6 8 | layout: blog-post.hbs 9 | --- 10 | 11 | Version 0.6.0 will be released next week. Please spend some time this 12 | week upgrading your code to v0.5.10. Report any API differences at https://github.com/joyent/node/wiki/API-changes-between-v0.4-and-v0.6 14 | or report a bug to us at http://github.com/joyent/node/issues 16 | if you hit problems. 17 | 18 | The API changes between v0.4.12 and v0.5.10 are 99% cosmetic, minor, 19 | and easy to fix. Most people are able to migrate their code in 10 20 | minutes. Don't fear. 21 | 22 | Once you've ported your code to v0.5.10 please help out by testing 23 | third party modules. Make bug reports. Encourage authors to publish 24 | new versions of their modules. Go through the list of modules at npmjs.com and try out random 26 | ones. This is especially encouraged of Windows users! 27 | -------------------------------------------------------------------------------- /nodejs.org/locale/uk/blog/video/bert-belder-libuv-lxjs-2012.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Bert Belder - libuv at LXJS 2012 3 | slug: bert-belder-libuv-lxjs-2012 4 | category: video 5 | date: 2012-09-30T17:28:45.000Z 6 | layout: blog-post.hbs 7 | --- 8 | 9 | Node core committer Bert Belder gave a talk at 10 | [LXJS](http://2012.lxjs.org/). If you are interested in how Node does 11 | asynchronous I/O across platforms, then you should definitely watch 12 | this video. 13 | 14 | 17 | -------------------------------------------------------------------------------- /nodejs.org/locale/uk/blog/video/bryan-cantrill-instrumenting-the-real-time-web.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "Bryan Cantrill: Instrumenting the Real Time Web" 3 | author: Isaac Schlueter 4 | date: 2012-05-08T17:00:34.000Z 5 | status: publish 6 | category: video 7 | slug: bryan-cantrill-instrumenting-the-real-time-web 8 | layout: blog-post.hbs 9 | --- 10 | Bryan Cantrill, VP of Engineering at Joyent, describes the challenges of instrumenting a distributed, dynamic, highly virtualized system -- and what their experiences taught them about the problem, the technologies used to tackle it, and promising approaches. 11 | 12 | This talk was given at Velocity Conf in 2011. 13 | 14 | 17 | 18 | 19 | -------------------------------------------------------------------------------- /nodejs.org/locale/uk/blog/video/index.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Videos 3 | layout: category-index.hbs 4 | listing: true 5 | robots: noindex, follow 6 | --- 7 | -------------------------------------------------------------------------------- /nodejs.org/locale/uk/blog/video/welcome-to-the-node-blog.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Welcome to the Node blog 3 | author: ryandahl 4 | date: 2011-03-18T03:17:12.000Z 5 | status: publish 6 | category: video 7 | slug: welcome-to-the-node-blog 8 | layout: blog-post.hbs 9 | --- 10 | Since Livejournal is disintegrating into Russian spam, I'm moving my technical blog to http://blog.nodejs.org/. I hope to do frequent small posts about what's going on in Node development and include posts from other core Node developers. Please subscribe to the RSS feed. 11 | 12 | To avoid making this post completely devoid of content, here is a new video from a talk I gave at the SF PHP group tastefully produced by Marakana: 13 | 16 | -------------------------------------------------------------------------------- /nodejs.org/locale/uk/blog/vulnerability/http-server-pipeline-flood-dos.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: DoS Vulnerability (fixed in Node v0.8.26 and v0.10.21) 3 | date: 2013-10-22T17:42:10.000Z 4 | slug: cve-2013-4450-http-server-pipeline-flood-dos 5 | category: vulnerability 6 | layout: blog-post.hbs 7 | --- 8 | Node.js is vulnerable to a denial of service attack when a client 9 | sends many pipelined HTTP requests on a single connection, and the 10 | client does not read the responses from the connection. 11 | 12 | We recommend that anyone using Node.js v0.8 or v0.10 to run HTTP 13 | servers in production please update as soon as possible. 14 | 15 | * v0.10.21
22 | ### Upcoming Events
23 |
24 | * [NodeConf Adventure 2016](https://ti.to/nodeconf/adventure-2016), "First batch of NodeConf Adventure tickets are up!", June 9th–12th, 2016 - Walker Creek Ranch, Marin, CA, USA
25 | * [NationJS Node Day Conference](http://nationjs.com/), TICKETS ARE AVAILABLE NOW, March 11, 2016 - Washington, DC
26 |
27 | Have an event about Node.js coming up? You can put your events here through the [Evangelism team repo](https://github.com/nodejs/evangelism) and announce it in the [Issues page](https://github.com/nodejs/evangelism/issues), specifically the Weekly Updates issue.
28 |
--------------------------------------------------------------------------------
/nodejs.org/locale/uk/blog/weekly-updates/weekly-update.2016-04-17.md:
--------------------------------------------------------------------------------
1 | ---
2 | title: Weekly Update - Apr 17th, 2016
3 | author: Minwoo Jung (github.com/JungMinu)
4 | date: 2016-04-17T12:00:00.000Z
5 | status: publish
6 | category: weekly
7 | slug: weekly-update-2016-04-17
8 | layout: blog-post.hbs
9 | ---
10 |
11 | ### Node.js News
12 | Node v4.4.3 (LTS) is released.
13 |
14 | ### Node v4.4.3 (LTS) Release
15 |
16 | We have one release: [Node v4.4.3 (LTS)](https://nodejs.org/en/blog/release/v4.4.3/). Complete changelog from previous releases can be found [on GitHub](https://github.com/nodejs/node/blob/master/CHANGELOG.md).
17 |
18 | ### New Node.js Foundation Survey Reports New “Full Stack” In Demand Among Enterprise Developers
19 |
20 | The Node.js User Survey report features insights on emerging trends happening in this massive community that serves as a leading indicator on trends like microservices architectures, real-time web applications, Internet of Things (IoT). The report paints a detailed picture of the technologies that are being used, in particular, with Node.js in production and language preferences (current and future) for front end, back end and IoT developers.
21 |
22 | See https://nodejs.org/en/blog/announcements/nodejs-foundation-survey/ for more information.
23 |
24 | ### Community Updates
25 |
26 | * [NodeUp podcast episode 100](http://nodeup.com/onehundred): A Creative Coding Show with Mariko Kosaka, Kassandra Perch, Myles Borins, and Rich Trott.
27 | * [A Quick Guide To Reading Node.js Core Source](https://medium.com/@Trott/a-quick-guide-to-reading-node-js-core-source-c968d83e4194#.mmontrmvg): One person's approach to understanding the source code that makes up Node.js core. "Your mileage may vary. Warranty void if seal is broken."
28 |
29 | If you have spotted or written something about Node.js, do come over to our [Evangelism team repo](https://github.com/nodejs/evangelism) and suggest it on the [Issues page](https://github.com/nodejs/evangelism/issues), specifically the Weekly Updates issue.
30 |
31 | ### Upcoming Events
32 |
33 | * [NodeConf Adventure 2016](https://ti.to/nodeconf/adventure-2016), "First batch of NodeConf Adventure tickets are up!", June 9th–12th, 2016 - Walker Creek Ranch, Marin, CA, USA
34 |
35 | Have an event about Node.js coming up? You can put your events here through the [Evangelism team repo](https://github.com/nodejs/evangelism) and announce it in the [Issues page](https://github.com/nodejs/evangelism/issues), specifically the Weekly Updates issue.
36 |
--------------------------------------------------------------------------------
/nodejs.org/locale/uk/blog/weekly-updates/weekly-update.2016-04-23.md:
--------------------------------------------------------------------------------
1 | ---
2 | title: Weekly Update - Apr 23rd, 2016
3 | author: Minwoo Jung (github.com/JungMinu)
4 | date: 2016-04-23T12:00:00.000Z
5 | status: publish
6 | category: weekly
7 | slug: weekly-update-2016-04-23
8 | layout: blog-post.hbs
9 | ---
10 |
11 | ### Node v5.11.0 (Stable) Release
12 |
13 | [Node v5.11.0 (Stable)](https://nodejs.org/en/blog/release/v5.11.0/). Complete changelog from previous releases can be found [on GitHub](https://github.com/nodejs/node/blob/master/CHANGELOG.md).
14 |
15 | ### Community Updates
16 |
17 | * [NodeUp podcast episode 100](http://nodeup.com/onehundred): A Creative Coding Show with Mariko Kosaka, Kassandra Perch, Myles Borins, and Rich Trott.
18 | * [A Quick Guide To Reading Node.js Core Source](https://medium.com/@Trott/a-quick-guide-to-reading-node-js-core-source-c968d83e4194#.mmontrmvg): One person's approach to understanding the source code that makes up Node.js core. "Your mileage may vary. Warranty void if seal is broken."
19 |
20 | If you have spotted or written something about Node.js, do come over to our [Evangelism team repo](https://github.com/nodejs/evangelism) and suggest it on the [Issues page](https://github.com/nodejs/evangelism/issues), specifically the Weekly Updates issue.
21 |
22 | ### Upcoming Events
23 |
24 | * [NodeConf Adventure 2016](https://ti.to/nodeconf/adventure-2016), "First batch of NodeConf Adventure tickets are up!", June 9th–12th, 2016 - Walker Creek Ranch, Marin, CA, USA
25 |
26 | Have an event about Node.js coming up? You can put your events here through the [Evangelism team repo](https://github.com/nodejs/evangelism) and announce it in the [Issues page](https://github.com/nodejs/evangelism/issues), specifically the Weekly Updates issue.
27 |
--------------------------------------------------------------------------------
/nodejs.org/locale/uk/blog/weekly-updates/weekly-update.2016-05-30.md:
--------------------------------------------------------------------------------
1 | ---
2 | title: Weekly Update - May 30th, 2016
3 | author: Minwoo Jung (github.com/JungMinu)
4 | date: 2016-05-30T12:00:00.000Z
5 | status: publish
6 | category: weekly
7 | slug: weekly-update-2016-05-30
8 | layout: blog-post.hbs
9 | ---
10 |
11 | ### Node v4.4.5 (LTS) Release
12 |
13 | [Node v4.4.5 (LTS)](https://nodejs.org/en/blog/release/v4.4.5/). Complete changelog from previous releases can be found [on GitHub](https://github.com/nodejs/node/blob/master/CHANGELOG.md).
14 |
15 | ### Community Updates
16 |
17 | * [NodeUp podcast episode 102](http://nodeup.com/onehundredtwo): A Node v6.0 Show with Anna Henningsen, James Snell, Rich Trott, and Rod Vagg.
18 | * [Node Hero - Getting Started With Node.js](https://blog.risingstack.com/node-hero-tutorial-getting-started-with-node-js/): you can learn how to get started with Node.js and deliver software products using it.
19 | * [A Quick Guide To Reading Node.js Core Source](https://medium.com/@Trott/a-quick-guide-to-reading-node-js-core-source-c968d83e4194#.mmontrmvg): One person's approach to understanding the source code that makes up Node.js core. "Your mileage may vary. Warranty void if seal is broken."
20 |
21 | If you have spotted or written something about Node.js, do come over to our [Evangelism team repo](https://github.com/nodejs/evangelism) and suggest it on the [Issues page](https://github.com/nodejs/evangelism/issues), specifically the Weekly Updates issue.
22 |
23 | ### Upcoming Events
24 |
25 | * [NodeConf Brazil](http://brazil.nodeconf.com) - June 4th - 5th, 2016
26 | * [NodeConf Adventure 2016](https://ti.to/nodeconf/adventure-2016), "First batch of NodeConf Adventure tickets are up!", June 9th–12th, 2016 - Walker Creek Ranch, Marin, CA, USA
27 | * [Node PDX](http://nodepdx.org) - June 19-21st, 2016
28 | * [NodeConf Argentina](https://2016.nodeconf.com.ar) - 18 - 19th November, 2016
29 |
30 | Have an event about Node.js coming up? You can put your events here through the [Evangelism team repo](https://github.com/nodejs/evangelism) and announce it in the [Issues page](https://github.com/nodejs/evangelism/issues), specifically the Weekly Updates issue.
31 |
--------------------------------------------------------------------------------
/nodejs.org/locale/uk/blog/weekly-updates/weekly-update.2016-06-16.md:
--------------------------------------------------------------------------------
1 | ---
2 | title: Weekly Update - June 16th, 2016
3 | author: Minwoo Jung (github.com/JungMinu)
4 | date: 2016-06-16T12:00:00.000Z
5 | status: publish
6 | category: weekly
7 | slug: weekly-update-2016-06-16
8 | layout: blog-post.hbs
9 | ---
10 |
11 | ### Node v6.2.1 (Current) Release
12 |
13 | [Node v6.2.1 (Current)](https://nodejs.org/en/blog/release/v6.2.1/). Complete changelog from previous releases can be found [on GitHub](https://github.com/nodejs/node/blob/master/CHANGELOG.md).
14 |
15 | ### Binaries for Linux on Power Systems
16 |
17 | Community downloads now include binaries for Linux on Power Systems with big endian in addition to the existing little endian binaries.
18 |
19 | See https://nodejs.org/en/download/.
20 |
21 | ### Security updates for all active release lines, June 2016
22 |
23 | We now intend to make releases available on or soon after **Thursday, the 23rd of June, 2016, UTC**.
24 |
25 | See https://nodejs.org/en/blog/vulnerability/june-2016-security-releases/ for more information.
26 |
27 | ### Community Updates
28 |
29 | * [How to Get Node.js Logging Right](https://blog.risingstack.com/node-js-logging-tutorial/): The aim of this article is to provide help with logging in Node.js modules, applications and distributed systems
30 | * [Node Hero - Node.js Unit Testing Tutorial](https://blog.risingstack.com/node-hero-node-js-unit-testing-tutorial/): you can learn how to get started with Node.js and deliver software products using it.
31 | If you have spotted or written something about Node.js, do come over to our [Evangelism team repo](https://github.com/nodejs/evangelism) and suggest it on the [Issues page](https://github.com/nodejs/evangelism/issues), specifically the Weekly Updates issue.
32 |
33 | ### Upcoming Events
34 |
35 | * [Node PDX](http://nodepdx.org) - June 19-21st, 2016
36 | * [NodeConf Argentina](https://2016.nodeconf.com.ar) - 18 - 19th November, 2016
37 |
38 | Have an event about Node.js coming up? You can put your events here through the [Evangelism team repo](https://github.com/nodejs/evangelism) and announce it in the [Issues page](https://github.com/nodejs/evangelism/issues), specifically the Weekly Updates issue.
39 |
--------------------------------------------------------------------------------
/nodejs.org/locale/uk/docs/faq.md:
--------------------------------------------------------------------------------
1 | ---
2 | title: FAQ
3 | layout: docs.hbs
4 | ---
5 | # FAQ
6 |
7 | ## Як я можу допомогти?
8 |
9 | Будь–хто може допомогти. Node.js дотримується [правил поведінки](https://github.com/nodejs/node/blob/master/CONTRIBUTING.md#code-of-conduct), а співпраця, релізи та внески від спільноти керуються моделлю [відкритого керівництва](https://github.com/nodejs/node/blob/master/GOVERNANCE.md#readme).
10 |
11 | Щоб почати, почніть нову [дискусію на GitHub](https://github.com/nodejs/node/issues) — ми раді почути ваші думки. Залучення у дискусію є хорошим способом отримати розуміння того, як ви можете допомогти в подальшому. Якщо є щось, що ви можете, будь–ласка, відкрийте [зробіть пул–реквест](https://github.com/nodejs/node/blob/master/CONTRIBUTING.md#code-contributions).
12 |
13 | ## Де відбуваються дискусії?
14 |
15 | На Freenode IRC є канал #node.js. Ми зберігаємо записи з цього каналу [тут](http://logs.libuv.org/node.js/latest).
16 |
17 | ## Що таке відкрите управління?
18 |
19 | Відкрите управління виступає за застосування філософії відкритого коду та відкритого вмісту, щоб дати змогу будь–якій зацікавленій особі долучатись до створення кінцевого продукту так, як і з вікі–документом. Юридичні аспекти демократично відкриті для широких мас, що використовують свою колективну мудрість, щоб принести користь процесу прийняття рішень і вдосконалення демократії. [[source]](https://en.wikipedia.org/wiki/Open-source_governance)
20 |
--------------------------------------------------------------------------------
/nodejs.org/locale/uk/docs/guides/index.md:
--------------------------------------------------------------------------------
1 | ---
2 | title: Керівництва
3 | layout: guides-index.hbs
4 | ---
5 |
6 | # Guides
7 |
--------------------------------------------------------------------------------
/nodejs.org/locale/uk/docs/index.md:
--------------------------------------------------------------------------------
1 | ---
2 | title: Документація
3 | layout: docs.hbs
4 | labels:
5 | lts: LTS
6 | ---
7 |
8 | # Про документацію
9 |
10 | Є три типи документації, що доступні на цьому сайті:
11 |
12 | * довідкова документація про API;
13 | * функціонал ES6;
14 | * часті запитання.
15 |
16 | ### Довідкова документація про API
17 |
18 | [Довідкова документація про API](/api/) надає детальну інформацію про функції та об’єкти у Node.js. Ця документація показує які аргументи приймають методи, які значення ці методи повертають та які помилки пов'язані з цими методами. Вона також показує які методи доступні для різних версій Node.js.
19 |
20 | Ця документація описує вбудовані модулі, які надаються Node.js. Вона не документує модулі, що надаються спільнотою.
21 |
22 | 23 |32 | 33 | ### Функціонал ES6 34 | 35 | [Секція ES6](/en/docs/es6/) описує три групи функціоналу ES6 і описує який функціонал наразі доступний у Node.js за замовчуванням разом з пояснювальними посиланнями. Вона також показує звідки дізнатись яка версія V8 постачається з певним релізом Node.js. 36 | 37 | ### Часті запитання 38 | 39 | [FAQ](/en/docs/faq/) покриває ту частину інформації, яка пояснює як будь–хто може зробити свій внесок у Node.js, наші правила поведінки та модель управління, як бути в курсі справ на GitHub та IRC і як допомогти з впорядкуванням іш’ю. 40 | -------------------------------------------------------------------------------- /nodejs.org/locale/uk/download/current.md: -------------------------------------------------------------------------------- 1 | --- 2 | layout: download-current.hbs 3 | title: Завантажити 4 | download: Завантажити 5 | downloads: 6 | headline: Завантаження 7 | lts: LTS 8 | current: Поточна 9 | tagline-current: Найновіші можливості 10 | tagline-lts: Рекомандовано для більшості 11 | display-hint: Показати завантаження для 12 | intro: > 13 | Завантажте початковий код Node.js або інсталятор для вашої платформи та почніть розробку сьогодні. 14 | currentVersion: Поточна версія 15 | buildDisclaimer: "Зауважте: Для побудови з початкового коду необхідний Python 2.6 або 2.7." 16 | additional: 17 | headline: Додаткові платформи 18 | intro: > 19 | Учасники спільноти Node.js підтримують неофіційні збірки Node.js для додаткових платформ. Майте на увазі, що ці збірки не підтримуються основною командою Node.js і можуть не мати того ж функціоналу що й поточний реліз Node.js. 20 | platform: Платформа 21 | provider: Провайдер 22 | --- 23 | -------------------------------------------------------------------------------- /nodejs.org/locale/uk/download/index.md: -------------------------------------------------------------------------------- 1 | --- 2 | layout: download.hbs 3 | title: Завантажити 4 | download: Завантажити 5 | downloads: 6 | headline: Завантаження 7 | lts: LTS 8 | current: Поточна 9 | tagline-current: Найновіші можливості 10 | tagline-lts: Рекомандовано для більшості 11 | display-hint: Показати завантаження для 12 | intro: > 13 | Завантажте початковий код Node.js або інсталятор для вашої платформи та почніть розробку сьогодні. 14 | currentVersion: Поточна версія 15 | buildDisclaimer: "Зауважте: Для побудови з початкового коду необхідний Python 2.6 або 2.7." 16 | additional: 17 | headline: Додаткові платформи 18 | intro: > 19 | Учасники спільноти Node.js підтримують неофіційні збірки Node.js для додаткових платформ. Майте на увазі, що ці збірки не підтримуються основною командою Node.js і можуть не мати тієї ж функціональності що й поточний реліз Node.js. 20 | platform: Платформа 21 | provider: Провайдер 22 | --- 23 | -------------------------------------------------------------------------------- /nodejs.org/locale/uk/download/releases.md: -------------------------------------------------------------------------------- 1 | --- 2 | layout: download-releases.hbs 3 | title: Previous Releases 4 | modules: "Шукаєте документацію про API для попередніх релізів?
24 | 25 |-
26 |
- Node.js 5.x 27 |
- Node.js 0.12.x 28 |
- Node.js 0.10.x 29 |
- всі версії 30 |
NODE_MODULE_VERSIONrefers to the ABI (application binary interface) version number of Node.js, used to determine which versions of Node.js compiled C++ add-on binaries can be loaded in to without needing to be re-compiled. It used to be stored as hex value in earlier versions, but is now represented as an integer." 5 | --- 6 | 7 | ### io.js та Node.js 8 | Релізи від 1.x до 3.x називались "io.js", оскільки вони були частиною форку io.js. Node.js 4.0.0 є загальним релізом io.js об'єднаного з Node.js 0.12.x у спільні релізи Node.js. 9 | 10 |11 | Шукаєте останній реліз певної версії? 12 | 13 |21 | -------------------------------------------------------------------------------- /nodejs.org/locale/uk/foundation/announcements.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Анонси 3 | layout: announcements.hbs 4 | --- 5 | -------------------------------------------------------------------------------- /nodejs.org/locale/uk/foundation/board.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Рада директорів Node.js Foundation 3 | layout: foundation.hbs 4 | --- 5 | 6 | Рада директорів складається з представників від корпоративних учасників, представників Технічного виконавчого комітету (Technical Steering Committee (TSC)), та представників, що обираються окремими учасниками. 7 | 8 | * Голова: **Danese Cooper**, шановний член технічного персоналу - open source в PayPal. 9 | * Заступник голови: **Scott Hammond**, головний виконавчий директор (CTO) в Joyent. 10 | * Директор TSC: **Rod Vagg**, директор стосовно node в NodeSource. 11 | * Золотий директор: **Charlie Robbins**, директор з інженерії в GoDaddy.com. 12 | * Срібний директор: **Brian McCallister**, головний виконавчий директор (CTO) платформ в Groupon. 13 | * Директор: **Todd Moore**, заступник президента стосовно відкритих технологій в IBM. 14 | * Директор: **Colleen Evans**, провідний програмний менеджер в Microsoft. 15 | * Директор: **Rich Sharples**, старший директор з управління продуктами компанії Red Hat. 16 | * Директор: **Imad Sousou**, заступник президента та генеральний менеджер в Intel. 17 | * Директор: **Ashley Williams**, директор від індивідуальних членів. 18 | * Директор: **Feross Aboukhadijeh**, директор від індивідуальних членів. 19 | 20 | Незалежно від ради, технічний виконавчий комітет встановлює напрямок технічного розвитку проекту, включаючи релізи, стандарти якості, управління проектом, хостинг репозиторіїв на GitHub тощо. Rod Vagg є членом та представником Технічного виконавчого комітету у раді директорів. 21 | -------------------------------------------------------------------------------- /nodejs.org/locale/uk/foundation/case-studies.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Ресурси Node.js Foundation 3 | layout: foundation.hbs 4 | --- 5 | 6 | ## Результати опитування Node.js Foundation 7 | 8 | З понад 3,5 мільйонами користувачів та постійним щорічним зростанням на 9 | 100%, Node.js стає універсальною платформою для веб–додатків, IoT 10 | та підприємництва. Звіт про результати опитування Node.js стосовно 11 | нових тенденцій, що відбуваються в цій величезній спільноті, 12 | служить ключовим індикатором тенденцій, як от архітектура мікросервісів, 13 | real-time веб–додатки, та інтернету речей (IOT). Звіт створює 14 | детальну картину технологій, що використовуються, зокрема, 15 | стосовно Node.js у production та мов, яким надають переваги 16 | (зараз і в майбутньому) у фронт–енді, бек—енді та IoT розробці. 17 | 18 | * [Читати повний анонс.](/en/blog/announcements/nodejs-foundation-survey/) 19 | * [Подивитись інфографіку.](/static/documents/2016-survey-infographic.png) 20 | * [Читати повний звіт.](/static/documents/2016-survey-report.pdf) 21 | 22 | ## Node.js забезпечує масштабованість та надійність в Uber 23 | 24 | Транспортна платформа Uber має амбітну мету: зробити транспорт надійним 25 | скрізь і для всіх. Дізнайтеся, чому Uber обрав Node.js для побудови 26 | своєї платформи і масивної системи для пошуку співпадінь. 27 | 28 | Читайте [повне дослідження](/static/documents/casestudies/Nodejs-at-Uber.pdf). 29 | -------------------------------------------------------------------------------- /nodejs.org/locale/uk/foundation/in-the-news.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Node.js Foundation у новинах 3 | layout: in-the-news.hbs 4 | --- 5 | -------------------------------------------------------------------------------- /nodejs.org/locale/uk/foundation/newsletter.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Підписка на поштове розсилання 3 | layout: foundation.hbs 4 | --- 5 | 6 | Щоб отримувати новини про Node.js Foundation зареєструйтесь нижче: 7 | 8 | 9 | -------------------------------------------------------------------------------- /nodejs.org/locale/uk/foundation/resources.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Node.js Foundation дослідження 3 | layout: foundation.hbs 4 | --- 5 | 6 | ## Node.js забезпечує масштабованість та надійність в Uber 7 | 8 | Транспортна платформа Uber має амбітну мету: зробити транспорт надійним скрізь і для всіх. Дізнайтеся, чому Uber обрав Node.js для побудови своєї платформи і масивної системи для пошуку співпадінь. 9 | 10 | Читайте [повне дослідження](/static/documents/casestudies/Nodejs-at-Uber.pdf). 11 | -------------------------------------------------------------------------------- /nodejs.org/locale/uk/foundation/tsc/index.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Технічний виконавчий комітет 3 | layout: foundation.hbs 4 | --- 5 | 6 | # Співавтори та Технічний виконавчий комітет 7 | 8 | Проект Node.js спонсорується Node.js Foundation і підтримується окремими 9 | учасниками. Технічний керівний комітет (Technical Steering Committee (TSC)) 10 | складається з ключових учасників, що продемонстрували як свої спеціальні 11 | технічні знання і практичну підтримку, так і сприяння поступальному розвиткові 12 | проекту та спільноті. 13 | 14 | Ви можете дізнатись більше про те, як стати учасником та членом TSC у 15 | [розділі для учасників](/uk/get-involved/contribute/). 16 | 17 | ### Поточні учасники 18 | 19 | На разі, проект Node.js має понад 300 учасників, що активно працюють над різними 20 | частинами проекту. Поточний список учасників можна знайти у 21 | [профілі проекту на GitHub](https://github.com/orgs/nodejs/people). 22 | 23 | ### Поточні члени Технічного керівного комітету 24 | 25 | * Alexis Campailla ([orangemocha](https://github.com/orangemocha)) 26 | * Ben Noordhuis ([bnoordhuis](https://github.com/bnoordhuis)) 27 | * Bert Belder ([piscisaureus](https://github.com/piscisaureus)) 28 | * Brian White ([mscdex](https://github.com/mscdex)) 29 | * Chris Dickinson ([chrisdickinson](https://github.com/chrisdickinson)) 30 | * Colin Ihrig ([cjihrig](https://github.com/cjihrig)) 31 | * Fedor Indutny ([indutny](https://github.com/indutny)) 32 | * James M Snell ([jasnell](https://github.com/jasnell)) 33 | * Jeremiah Senkpiel ([Fishrock123](https://github.com/Fishrock123)) 34 | * Julien Gilli ([misterdjules](https://github.com/misterdjules)) 35 | * Michael Dawson ([mhdawson](https://github.com/mhdawson)) 36 | * Rod Vagg ([rvagg](https://github.com/rvagg)) 37 | * Shigeki Ohtsu ([shigeki](https://github.com/shigeki)) 38 | * Steven R Loomis ([srl295](https://github.com/srl295)) 39 | * Trevor Norris ([trevnorris](https://github.com/trevnorris)) 40 | 41 | ## Зустрічі Технічного виконавчого комітету 42 | 43 | [Meeting minutes](minutes/) 44 | -------------------------------------------------------------------------------- /nodejs.org/locale/uk/foundation/tsc/minutes.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Зустрічі Технічного виконавчого комітету 3 | layout: foundation-tsc-minutes-index.hbs 4 | --- 5 | -------------------------------------------------------------------------------- /nodejs.org/locale/uk/foundation/tsc/minutes/2014-12-10.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Minutes for the Node.js core team meeting of 12/10/2014 3 | date: 2014-12-10 4 | layout: foundation-tsc-minutes-post.hbs 5 | --- 6 | 7 | ## Team announcements 8 | 9 | Colin Ihrig is promoted to apprentice. Chris Dickinson and Julien Gilli are 10 | promoted from apprentice to core team members. 11 | 12 | ## Next releases 13 | 14 | ### 0.10.34 15 | 16 | The next stable release, 0.10.34, is imminent and should be available in the 17 | next few days. The only issue remaining is that recently libuv added an entry 18 | to the public API (see https://github.com/libuv/libuv/commit/9da5fd443ebc2c56a 19 | 7f5946f0a1e04801b370a33). Node will need to find a way to not cause any 20 | problems for users who link node with a dynamic shared libuv. 21 | 22 | ### 0.11.15 23 | 24 | Nobody had any blocker for the next developement release, whose release is 25 | also scheduled to happen in the next few days. The priority is given to 26 | releasing 0.10.34 first though. 27 | 28 | ### 0.12 29 | 30 | #### Potential V8 upgrade 31 | 32 | During the previous meeting, the possibility of upgrading V8 to a more recent 33 | release was discussed. While everyone agreed that upgrading V8 to a version 34 | that is closer to what the V8 team considers to be stable would benefit all 35 | users in terms of new features (e.g generators), several concerns were 36 | expressed: 37 | 38 | * It is not clear what impact it would have on binary modules. 39 | 40 | * Users would need to upgrade their toolchain, as V8 moved to C++11. It's not a 41 | problem for individual developers, as they can upgrade easily most of the 42 | time. However, it could be a problem for distributions (an example is CentOS), 43 | and people who followed the 0.11.x branch for a long time and don't expect 44 | such a change. 45 | 46 | Moreover, everyone agreed that performing this upgrade that late in the 47 | development process and so close to a new stable relase is risky. 48 | 49 | The consensus seems to be leaning towards not upgrading V8 again before 0.12, 50 | and instead having a smaller list of features and fixes for the next stable 51 | release, with a much shorter release time. One of the first thing that would 52 | be done in the next unstable branch (0.13) would be a V8 upgrade. 53 | 54 | ## TODO for next meeting 55 | 56 | Next meeting is December 11th at 9:00AM PST. 57 | 58 | * Come up with a list of the following GitHub issues: 59 | * Needed for 0.12.0. 60 | * Needed 0.12.1. 61 | -------------------------------------------------------------------------------- /nodejs.org/locale/uk/foundation/tsc/minutes/2015-01-15.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Minutes for the Node.js core team meeting of 01/15/2015 3 | date: 2015-01-15 4 | layout: foundation-tsc-minutes-post.hbs 5 | --- 6 | 7 | ## Participants 8 | 9 | * Timothy J Fontaine 10 | * Julien Gilli 11 | * Robert Kowalski 12 | 13 | ## Topics 14 | 15 | ### Website 16 | 17 | The only topic that was discussed during this meeting was the Node.js website. 18 | 19 | #### HTTPS access 20 | 21 | Robert suggested adding HTTPS access for Node.js' website. TJ mentioned that 22 | there is already a HTTPS endpoint on the website, but that clients (browsers, 23 | etc.) are not *redirected* by default from http to https, because doing so was 24 | breaking a lot of people (e.g nvm). 25 | 26 | Proposed solution by TJ: redirect everything by default to https except 27 | nodejs.org/dist. 28 | 29 | Robert proposed to setup a clone of the website with this change to be able to 30 | test it. 31 | 32 | #### Documentation versions 33 | 34 | Robert suggested a new feature for the documentation available on Node.js' 35 | website: accessing docs for different versions. 36 | 37 | Robert asked if regenerating the documentation for versions older than 0.10 38 | makes sense. TJ mentioned that we probably don't want to go back further than 39 | 0.10. However, participants agreed that in the future, publishing older 40 | documentation could be fun and/or interesting. 41 | 42 | TJ suggested that documentation generation tools could be refactored and 43 | published as npm packages so that they can work standalone. That could make 44 | generating documentation for different versions easier. 45 | 46 | TJ also pointed out that a significant SEO effort went into making sure that 47 | the latest Node.js documentation shows up when searching for Node 48 | documentation, and that any change to the website's documentation should 49 | preserve that. 50 | 51 | -------------------------------------------------------------------------------- /nodejs.org/locale/uk/foundation/tsc/minutes/2015-01-29.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Minutes for the Node.js core team meeting of 01/29/2015 3 | date: 2015-01-29 4 | layout: foundation-tsc-minutes-post.hbs 5 | --- 6 | 7 | ## Participants 8 | 9 | * Michal Dawson 10 | * TJ Fontaine 11 | * Colin Ihrig 12 | * Julien Gilli 13 | * Robert Kowalski 14 | * James Snell 15 | 16 | ## Website 17 | 18 | Robert: Partially redirected http -> https for api docs and docs. Only blog 19 | page missing. Learning about SNI. Documentation generation tool: created a 20 | tests suite that runs some smoke tests. Hopes to get a PR for that next week. 21 | 22 | TJ: We have a wildcard cert for the blog, so using this cert might be easier 23 | than using SNI. 24 | 25 | ## 0.11.16 release 26 | 27 | Colin: has two bug fixes not API breaking that could go in for 0.11.16. 28 | 29 | TJ: Would like to put https://github.com/joyent/node/pull/8966 in v0.10. Colin 30 | hasn't tried to rebase it on v0.10, but will do today. 31 | 32 | ## Building dependencies 33 | 34 | James: Working on refactoring the way dependencies (deps/) are built. 35 | 36 | TJ: The build refactoring should target the master branch, and then might get 37 | backported to v0.12. 38 | 39 | ## PRs/Issues in io.js 40 | 41 | TJ: When we see bugs in io.js that are also in Node.js, then please report 42 | these bugs. 43 | 44 | James: I'm going to go through the recent changes in io.js and will report 45 | issues/PRs. 46 | 47 | ## PowerPC support 48 | 49 | Michael, James and TJ: Jenkins agents building and running tests for the Power 50 | platform will be hooked up asap. 51 | -------------------------------------------------------------------------------- /nodejs.org/locale/uk/foundation/tsc/minutes/2015-02-05.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Minutes for the Node.js core team meeting of 02/05/2015 3 | date: 2015-02-05 4 | layout: foundation-tsc-minutes-post.hbs 5 | --- 6 | 7 | ## Participants 8 | 9 | * Michael Dawson 10 | * TJ Fontaine 11 | * Julien Gilli 12 | * Colin Ihrig 13 | * Trevor Norris 14 | * Wyatt Preul 15 | * James Snell 16 | 17 | ## Discussions 18 | 19 | ### 0.12.0 release 20 | 21 | Julien: Remaining issues to release 0.12.0 are in the 0.11.17 milestone on GitHub. 22 | Everyone agreed that there's no blocker for this release. 23 | 24 | TJ: will put a draft for blog post for release notes up and the rest of the team will review it. 25 | 26 | #### Native modules breakage 27 | 28 | TJ: some modules that don't use nan or other ways to build with V8 shipped by 29 | node v0.12.x will break. These modules will need to be fixed on a case by case 30 | basis. 31 | 32 | ### Website 33 | 34 | Wyatt: security page published. 35 | 36 | ### Post 0.12.0 37 | 38 | TJ: From now on, it would be nice if core team members would use 39 | https://github.com/joyent/git-apply-pr to land PRs/contributions. It's a work 40 | in progress, bug fixes/improvements are more than welcome! 41 | 42 | TJ: We may discuss what to integrate from the core team working group of the 43 | Node.js Advisory Board (https://github.com/joyent/nodejs-advisory-board) 44 | during the next core team call. 45 | 46 | ### Testing downstream modules and applications 47 | 48 | Michael Dawson: need for higher level benchmarks (for upper layers like 49 | express, etc.). 50 | 51 | TJ: Some people have been working on downstream integration tests (for 52 | instance, Julien with test-node-apps) 53 | 54 | TJ: Downstream integration tests, downstream benchmarking desirable in the 55 | future. 56 | 57 | James: identify the top 120 most depended on modules, determine what core 58 | modules they use, and create a tests framework around that. 59 | 60 | Michael: Michael and James already have something simple that run tests for 61 | some npm modules. 62 | 63 | ### Node summit 64 | 65 | TJ: Tentative meeting on Monday 2pm to 4pm: purely technical meeting about 66 | roadmap, not a meeting about governance. 67 | -------------------------------------------------------------------------------- /nodejs.org/locale/uk/foundation/tsc/minutes/2015-06-04.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Minutes for the joyent/node TSC meeting of 06/04/2015 3 | date: 2015-06-04 4 | layout: foundation-tsc-minutes-post.hbs 5 | --- 6 | 7 | ## Participants 8 | 9 | * Colin Ihrig 10 | * James Snell 11 | * Julien Gilli 12 | * Michael Dawson 13 | 14 | ## Discussions 15 | 16 | ### Weekly calls 17 | 18 | Julien: Do we want to keep doing weekly calls with the current contributors to 19 | joyent/node, or should all discussions be moved to the combined Node.js TSC 20 | meeting? 21 | 22 | James: Still has value in the short term. Maybe have them not every week but 23 | when needed? 24 | 25 | Michael: Maybe part of the LTS working group? 26 | 27 | Colin: Need to make sure we bring joyent/node issues to the combined TSC call, 28 | during the last two calls we had no discussions around joyent/node. 29 | 30 | Julien: For instance adding collaborators from io.js to joyent/node is a topic 31 | that I'd like to discuss in the combined call. 32 | 33 | Michael: Actually another topic could be this very discussion that we have now 34 | about transitioning this weekly call into the LTS working group call. 35 | 36 | Action item: propose during next combined TSC call that this weekly call be 37 | transitioned to the LTS working group call. 38 | 39 | ### Upgrade to libuv 1.6.0 40 | 41 | Julien: the issue with OSX and tty is not severe to me. It's been present 42 | since v0.11.12, happens on OSX only and is specific to TTY handling. 43 | 44 | Michael: It seems that there's no need to rush the next v0.12.x release for 45 | this particular issue, we should aim at including the fix in the next one when 46 | it's ready. 47 | 48 | James, Colin, Julien: agreed. 49 | 50 | ### Security report from HP 51 | 52 | Julien: HP recently sent a security report mentioning potential security 53 | issues, but all of them seem to be false positives. Currently finishing 54 | investigations to be sure of that and communicating with them. 55 | 56 | ### RC4 deprecation fixes 57 | 58 | Julien: Did another round of review and we're making progress. James will be 59 | on vacation for the next 2 weeks so I'll do my best to take it from there. 60 | We'll revert what's landed in v0.10 so far to prevent this from holding back 61 | other changes, and submit a new single PR that contains all changes so that 62 | there's only one place to comment. 63 | 64 | Michael: If you need help with this just let us know. 65 | -------------------------------------------------------------------------------- /nodejs.org/locale/uk/foundation/tsc/minutes/2015-06-11.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Node 0.10.X/0.12.X LTS team meeting 06/11/2015 3 | date: 2015-06-11 4 | layout: foundation-tsc-minutes-post.hbs 5 | --- 6 | 7 | ## Participants 8 | 9 | * Julien Gilli 10 | * Alexis Campailla 11 | * Michael Dawson 12 | * Colin Ihrig 13 | 14 | ## Agenda 15 | 16 | * Logjam/openssl upgrade 17 | * Upgrade of libuv to 1.6.1 18 | * First draft of breaking changes between io.js/Node 0.12 19 | * Windows Installer Changes 20 | 21 | 22 | ## Minutes 23 | 24 | ### Logjam/openssl upgrade 25 | 26 | Michael: Expect OpenSSL upgrade imminently. Just drop support for smaller size. Do we expect that to break users? 27 | 28 | Michael: should also consider including: 29 | 30 | * https://github.com/nodejs/node/pull/1739 31 | * https://github.com/nodejs/node/pull/1831 32 | * https://github.com/joyent/node/issues/25366 (checked and docs for io.js indicate modp1 is still there) 33 | 34 | Michael: Stewart on my team has volunteered to create a PR against Node.js to upgrade OpenSSL. 35 | 36 | ### Libuv upgrade to 1.6.1 37 | 38 | Julien: Libuv PR, fixes annoying issue on OSX 10. Worth reviewing soon. 39 | 40 | Colin: PR already landed in io.js 41 | 42 | Julien: top priority to review that ABI/API hasn.t changed in a breaking way. 43 | 44 | Julien: Julien to try and review today, likely to be included in release for openssl upgrade 45 | 46 | ### Breaking changes between io.js and Node 0.12.X 47 | 48 | First draft of doc of breaking changes between 0.12 and next LTS. 49 | 50 | Julien: https://github.com/nodejs/node/wiki/Breaking-changes-between-v0.12-and-next-LTS-release 51 | 52 | Based on io.js issue tracker, joyent\node backport commit log. v8 breaking changes from release notes (?) 53 | 54 | Please review and comment on issue. 55 | 56 | ### Debug port issues 57 | 58 | Colin working to fix https://github.com/nodejs/node/pull/1949 - new debug port for each worker. 59 | 60 | ### Windows installer changes 61 | 62 | Alexis: https://github.com/joyent/node/issues/5849 - currently a hybrid/broken, will submit PR to do full install for all users, to be added to next milestone 63 | 64 | https://github.com/joyent/node/issues/25087, same upgrade code used for 32/64 bit which is not good practice. Can result in binaries from one (32/64) being put into the other. Will move to use 2 upgrade codes, but this will break upgrade. Going to add manual action to check for old code and give message saying you cannot upgrade and that you should un-install and install again 65 | 66 | -------------------------------------------------------------------------------- /nodejs.org/locale/uk/get-involved/code-and-learn.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Code + Learn 3 | layout: contribute.hbs 4 | --- 5 | 6 | # Code + Learn 7 | 8 | Code + Learn це всесвітня ініціатива воркшопів, що мають за мету познайомити нових розробників з тим, як працювати з Node.js. Консультуючі практичні сесії під наставництвом поточних співавторів та вирішення реальних проблем. 9 | 10 | Запущені у вересні 2015–го, воркшопи відбуваються у Дубліні та Лондоні (під керівництвом [LNUG](http://lnug.org/)). 11 | 12 | - [Code + Learn event listings](https://ti.to/code-and-learn) 13 | -------------------------------------------------------------------------------- /nodejs.org/locale/uk/index.md: -------------------------------------------------------------------------------- 1 | --- 2 | layout: index.hbs 3 | labels: 4 | current-version: Поточна версія 5 | download: Завантажити 6 | download-for: Завантажити для 7 | other-downloads: Інші завантаження 8 | other-lts-downloads: Інші LTS завантаження 9 | other-current-downloads: Інші поточні завантаження 10 | current: Поточна 11 | lts: LTS 12 | tagline-current: Найновіші можливості 13 | tagline-lts: Рекомандовано для більшості 14 | changelog: Список змін 15 | api: Документація API 16 | version-schedule-prompt: Або подивіться на 17 | version-schedule-prompt-link-text: графік LTS 18 | --- 19 | 20 | Node.js® — це JavaScript–оточення побудоване на JavaScript–рушієві [Chrome's V8](https://developers.google.com/v8/). 21 | Node.js використовує подієву, неблокуючу I/O модель, що робить його легким та ефективним. Пакетна екосистема Node.js, [npm](https://www.npmjs.com/), є найбільшою у світі екосистемою бібліотек з відкритим кодом. 22 | -------------------------------------------------------------------------------- /nodejs.org/locale/uk/knowledge/HTTP/clients/how-to-access-query-string-parameters.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: How to access query string parameters 3 | date: '2011-08-26T10:08:50.000Z' 4 | tags: 5 | - http 6 | difficulty: 1 7 | layout: knowledge-post.hbs 8 | --- 9 | 10 | In Node.js, functionality to aid in the accessing of URL query string parameters is built into the standard library. The built-in `url.parse` method takes care of most of the heavy lifting for us. Here is an example script using this handy function and an explanation on how it works: 11 | 12 | var fs = require('fs'); 13 | var http = require('http'); 14 | var url = require('url') ; 15 | 16 | http.createServer(function (req, res) { 17 | var queryObject = url.parse(req.url,true).query; 18 | console.log(queryObject); 19 | 20 | res.writeHead(200); 21 | res.end('Feel free to add query parameters to the end of the url'); 22 | }).listen(8080); 23 | 24 | The key part of this whole script is this line: `var queryObject = url.parse(req.url,true).query;`. Let's take a look at things from the inside-out. First off, `req.url` will look like `/app.js?foo=bad&baz=foo`. This is the part that is in the URL bar of the browser. Next, it gets passed to `url.parse` which parses out the various elements of the URL (NOTE: the second paramater is a boolean stating whether the method should parse the query string, so we set it to true). Finally, we access the `.query` property, which returns us a nice, friendly Javascript object with our query string data. 25 | 26 | 27 | -------------------------------------------------------------------------------- /nodejs.org/locale/uk/knowledge/HTTP/servers/how-to-create-a-HTTP-server.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: How do I create a HTTP server? 3 | date: '2011-08-26T10:08:50.000Z' 4 | tags: 5 | - http 6 | difficulty: 1 7 | layout: knowledge-post.hbs 8 | --- 9 | 10 | 11 | Making a simple HTTP server in Node.js has become the de facto 'hello world' for the platform. On the one hand, Node.js provides extremely easy-to-use HTTP APIs; on the other hand, a simple web server also serves as an excellent demonstration of Node's asynchronous strengths. 12 | 13 | Let's take a look at a very simple example: 14 | 15 | var http = require('http'); 16 | var requestListener = function (req, res) { 17 | res.writeHead(200); 18 | res.end('Hello, World!\n'); 19 | } 20 | 21 | var server = http.createServer(requestListener); 22 | server.listen(8080); 23 | 24 | Save this in a file called `server.js` - run `node server.js`, and your program will hang there... it's waiting for connections to respond to, so you'll have to give it one if you want to see it do anything. Try opening up a browser, and typing `localhost:8080` into the location bar. If everything has been set up correctly, you should see your server saying hello! 25 | 26 | Let's take a more in-depth look at what the above code is doing. First, a function is defined called `requestListener` that takes a request object and a response object as parameters. 27 | 28 | The request object contains things such as the requested URL, but in this example we ignore it and always return "Hello World". 29 | 30 | The response object is how we send the headers and contents of the response back to the user making the request. Here we return a 200 response code (signaling a successful response) with the body "Hello World". Other headers, such as `Content-type`, would also be set here. 31 | 32 | Next, the `http.createServer` method creates a server that calls `requestListener` whenever a request comes in. The next line, `server.listen(8080)`, calls the `listen` method, which causes the server to wait for incoming requests on the specified port - 8080, in this case. 33 | 34 | There you have it - your most basic Node.js HTTP server. 35 | -------------------------------------------------------------------------------- /nodejs.org/locale/uk/knowledge/REPL/how-to-use-nodejs-repl.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "How do I use node's REPL?" 3 | date: '2011-08-26T10:08:50.000Z' 4 | tags: 5 | - cli 6 | - repl 7 | difficulty: 1 8 | layout: knowledge-post.hbs 9 | --- 10 | 11 | 12 | 13 | Node.js ships with a REPL, which is short for 'Read-Eval-Print Loop'. It is the Node.js shell; any valid Javascript which can be written in a script can be passed to the REPL. It can be extremely useful for experimenting with node.js, debugging code, and figuring out some of Javascript's more eccentric behaviors. 14 | 15 | Running it is simple - just run node without a filename. 16 | 17 | docs@nodejitsu:~/$ node 18 | 19 | It then drops you into a simple prompt ('>') where you can type any Javascript command you wish. As in most shells, you can press the up and down arrow keys to scroll through your command history and modify previous commands. The REPL also `Tab` to make the REPL try to autocomplete the command. 20 | 21 | Whenever you type a command, it will print the return value of the command. If you want to reuse the previous return value, you can use the special `_` variable. 22 | 23 | For example: 24 | 25 | node 26 | > 1+1 27 | 2 28 | > _+1 29 | 3 30 | 31 | One thing worth noting where REPL return values are concerned: 32 | 33 | > x = 10 34 | 10 35 | > var y = 5 36 | > x 37 | 10 38 | > y 39 | 5 40 | 41 | When the `var` keyword is used, the value of the expression is stored, but *NOT* returned. When a bare identifier is used, the value is also returned, as well as stored. 42 | 43 | If you need to access any of the builtin modules, or any third party modules, they can be accessed with `require`, just like in the rest of Node. 44 | 45 | For example: 46 | 47 | node 48 | > path = require('path') 49 | { resolve: [Function], 50 | normalize: [Function], 51 | join: [Function], 52 | dirname: [Function], 53 | basename: [Function], 54 | extname: [Function], 55 | exists: [Function], 56 | existsSync: [Function] } 57 | > path.basename("/a/b/c.txt") 58 | 'c.txt' 59 | 60 | Note once again that without the `var` keyword, the contents of the object are returned immediately and displayed to `stdout`. 61 | -------------------------------------------------------------------------------- /nodejs.org/locale/uk/knowledge/advanced/streams/how-to-use-fs-create-read-stream.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: How to use fs.createReadStream? 3 | date: '2011-08-26T10:08:50.000Z' 4 | tags: 5 | - core 6 | - streams 7 | - fs 8 | difficulty: 3 9 | layout: knowledge-post.hbs 10 | --- 11 | 12 | The function `fs.createReadStream()` allows you to open up a readable stream in a very simple manner. All you have to do is pass the path of the file to start streaming in. It turns out that the response (as well as the request) objects are streams. So we will use this fact to create a http server that streams the files to the client. Since the code is simple enough, it is pretty easy just to read through it and comment why each line is necessary. 13 | 14 | var http = require('http'); 15 | var fs = require('fs'); 16 | 17 | http.createServer(function(req, res) { 18 | // The filename is simple the local directory and tacks on the requested url 19 | var filename = __dirname+req.url; 20 | 21 | // This line opens the file as a readable stream 22 | var readStream = fs.createReadStream(filename); 23 | 24 | // This will wait until we know the readable stream is actually valid before piping 25 | readStream.on('open', function () { 26 | // This just pipes the read stream to the response object (which goes to the client) 27 | readStream.pipe(res); 28 | }); 29 | 30 | // This catches any errors that happen while creating the readable stream (usually invalid names) 31 | readStream.on('error', function(err) { 32 | res.end(err); 33 | }); 34 | }).listen(8080); 35 | 36 | -------------------------------------------------------------------------------- /nodejs.org/locale/uk/knowledge/advanced/streams/how-to-use-fs-create-write-stream.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: How to use fs.createWriteStream? 3 | date: '2011-08-26T10:08:50.000Z' 4 | tags: 5 | - core 6 | - streams 7 | - fs 8 | difficulty: 3 9 | layout: knowledge-post.hbs 10 | --- 11 | 12 | The function `fs.createWriteStream()` creates a writable stream in a very simple manner. After a call to `fs.createWriteStream` with the filepath, you have a writeable stream to work with. It turns out that the response (as well as the request) objects are streams. So we will stream the `POST` data to the file `output`. Since the code is simple enough, it is pretty easy just to read through it and comment why each line is necessary. 13 | 14 | var http = require('http'); 15 | var fs = require('fs'); 16 | 17 | http.createServer(function(req, res) { 18 | // This opens up the writeable stream to `output` 19 | var writeStream = fs.createWriteStream('./output'); 20 | 21 | // This pipes the POST data to the file 22 | req.pipe(writeStream); 23 | 24 | // After all the data is saved, respond with a simple html form so they can post more data 25 | req.on('end', function () { 26 | res.writeHead(200, {"content-type":"text/html"}); 27 | res.end(''); 28 | }); 29 | 30 | // This is here incase any errors occur 31 | writeStream.on('error', function (err) { 32 | console.log(err); 33 | }); 34 | }).listen(8080); 35 | -------------------------------------------------------------------------------- /nodejs.org/locale/uk/knowledge/child-processes/how-to-spawn-a-child-process.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: How to spawn a child process - the basics 3 | date: '2011-08-26T10:08:50.000Z' 4 | tags: 5 | - core 6 | - child_process 7 | difficulty: 2 8 | layout: knowledge-post.hbs 9 | --- 10 | 11 | 12 | If you find yourself wishing you could have your Node.js process start another program for you, then look no further than the `child_process` module. 13 | 14 | The simplest way is the "fire, forget, and buffer" method using `child_process.exec`. It runs your process, buffers its output (up to a default maximum of 200kb), and lets you access it from a callback when it is finished. Let us take a look at an example: 15 | 16 | var childProcess = require('child_process'), 17 | ls; 18 | 19 | ls = childProcess.exec('ls -l', function (error, stdout, stderr) { 20 | if (error) { 21 | console.log(error.stack); 22 | console.log('Error code: '+error.code); 23 | console.log('Signal received: '+error.signal); 24 | } 25 | console.log('Child Process STDOUT: '+stdout); 26 | console.log('Child Process STDERR: '+stderr); 27 | }); 28 | 29 | ls.on('exit', function (code) { 30 | console.log('Child process exited with exit code '+code); 31 | }); 32 | 33 | NODE PRO TIP: `error.stack` is a stack trace to the point that the [Error object](/what-is-the-error-object) was created. 34 | 35 | It should be noted that the `STDERR` of a given process is not exclusively reserved for error messages. Many programs use it as a channel for secondary data instead. As such, when trying to work with a program that you have not previously spawned as a child process, it can be helpful to start out dumping both `STDOUT` and `STDERR`, as shown above, to avoid any surprises. 36 | 37 | While `child_process.exec` buffers the output of the child process for you, it also returns a `ChildProcess` object, Node's way of wrapping a still-running process. In the example above, since we are using `ls`, a program that will exit immediately regardless, the only part of the `ChildProcess` object worth worrying about is the `on exit` handler. It is not necessary here - the process will still exit and the error code will still be shown on errors. 38 | 39 | 40 | -------------------------------------------------------------------------------- /nodejs.org/locale/uk/knowledge/errors/what-are-the-error-conventions.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: What are the error conventions? 3 | date: '2011-08-26T10:08:50.000Z' 4 | tags: 5 | - errors 6 | - conventions 7 | difficulty: 1 8 | layout: knowledge-post.hbs 9 | --- 10 | 11 | 12 | In node.js, it is considered standard practice to handle errors in asynchronous functions by returning them as the first argument to the current function's callback. If there is an error, the first parameter is passed an `Error` object with all the details. Otherwise, the first parameter is null. 13 | 14 | It's simpler than it sounds; let's demonstrate. 15 | 16 | var isTrue = function(value, callback) { 17 | if (value === true) { 18 | callback(null, "Value was true."); 19 | } 20 | else { 21 | callback(new Error("Value is not true!")); 22 | } 23 | } 24 | 25 | var callback = function (error, retval) { 26 | if (error) { 27 | console.log(error); 28 | return; 29 | } 30 | console.log(retval); 31 | } 32 | 33 | // Note: when calling the same asynchronous function twice like this, you are in a race condition. 34 | // You have no way of knowing for certain which callback will be called first when calling the functions in this manner. 35 | 36 | isTrue(false, callback); 37 | isTrue(true, callback); 38 | 39 | { stack: [Getter/Setter], 40 | arguments: undefined, 41 | type: undefined, 42 | message: 'Value is not true!' } 43 | Value was true. 44 | 45 | As you can see from the example, the callback is called with null as its first argument if there is no error. However, if there is an error, you create an `Error` object, which then becomes the callback's only parameter. 46 | 47 | The `callback` function shows the reason for this: it allows a user to easily know whether or not an error occurred. If `null` was not the first argument passed on success, the user would need to check the object being returned and determine themselves whether or not the object constituted an error - a much more complex and less user-friendly approach. 48 | 49 | So to wrap it all up, when using callbacks, if an error comes up, then pass it as the first argument. Otherwise, pass `null` first, and then your return arguments. On the receiving end, inside the callback function, check if the first parameter is non-null; if it is, handle it as an error. 50 | -------------------------------------------------------------------------------- /nodejs.org/locale/uk/knowledge/errors/what-is-the-error-object.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: What is the error object? 3 | date: '2011-08-26T10:08:50.000Z' 4 | tags: 5 | - errors 6 | - builtin 7 | difficulty: 1 8 | layout: knowledge-post.hbs 9 | --- 10 | 11 | The error object is a built-in object that provides a standard set of useful information when an error occurs, such as a stack trace and the error message. For example: 12 | 13 | Code: 14 | 15 | var error = new Error("The error message"); 16 | console.log(error); 17 | console.log(error.stack); 18 | 19 | Result: 20 | 21 | { stack: [Getter/Setter], 22 | arguments: undefined, 23 | type: undefined, 24 | message: 'The error message' } 25 | Error: The error message 26 | at Object.-
14 |
- Node.js 6.x 15 |
- Node.js 5.x 16 |
- Node.js 0.12.x 17 |
- Node.js 0.10.x 18 |
- усі версії 19 |
(/home/nico/example.js:1:75) 27 | at Module._compile (module.js:407:26) 28 | at Object..js (module.js:413:10) 29 | at Module.load (module.js:339:31) 30 | at Function._load (module.js:298:12) 31 | at Array.0 (module.js:426:10) 32 | at EventEmitter._tickCallback (node.js:126:26) 33 | 34 | `error.stack` shows you where an error came from, as well as a list of the function calls that preceded it - for your convenience, `error.stack` always prints `error.message` as the first line of its output, making `error.stack` a convenient single property to log during debugging. 35 | 36 | If you want to add more information to the Error object, you can always add properities, just as with any other Javascript object: 37 | 38 | var error = new Error("The error message"); 39 | error.http_code = 404; 40 | console.log(error); 41 | 42 | For more details how to use the Error object, check out the [article on error conventions](/articles/errors/what-are-the-error-conventions) 43 | -------------------------------------------------------------------------------- /nodejs.org/locale/uk/knowledge/errors/what-is-try-catch.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: What is try-catch? 3 | date: '2011-08-26T10:08:50.000Z' 4 | tags: 5 | - errors 6 | - builtin 7 | difficulty: 1 8 | layout: knowledge-post.hbs 9 | --- 10 | 11 | Example: 12 | 13 | console.log("entering try-catch statement"); 14 | 15 | try { 16 | console.log("entering try block"); 17 | throw "thrown message"; 18 | console.log("this message is never seen"); 19 | } 20 | catch (e) { 21 | console.log("entering catch block"); 22 | console.log(e); 23 | console.log("leaving catch block"); 24 | } 25 | finally { 26 | console.log("entering and leaving the finally block"); 27 | } 28 | 29 | console.log("leaving try-catch statement"); 30 | 31 | Results: 32 | 33 | entering try-catch statement 34 | entering try block 35 | entering catch block 36 | thrown message 37 | leaving catch block 38 | entering and leaving the finally block 39 | leaving try-catch statement 40 | 41 | Javascript's `try-catch-finally` statement works very similarly to the `try-catch-finally` encountered in C++ and Java. First, the try block is executed until and unless the code in it throws an exception (whether it is an explicit `throw` statement, the code has an uncaught native exception, or if the code calls a function that uses `throw`). 42 | 43 | If the code doesn't throw an exception, then the whole try block is executed. If the code threw an exception inside the try block, then the catch block is executed. Last of all, the finally block is always executed, subsequent to the other blocks but prior to any subsequent code located outside of the `try-catch-finally` blocks. The `finally` block will just about always execute, no matter what kind of throwing, catching, or returning one might be trying to do inside the `try` or `catch` blocks. 44 | 45 | Note that you can omit the `catch` or `finally` block, but one of them must be present. 46 | 47 | ## But wait, isn't it Node.js convention to not use try-catch? 48 | 49 | In the core node.js libraries, the only place that one really *needs* to use a try-catch is around `JSON.parse()`. All of the other methods use either the standard Error object through the first parameter of the callback or emit an `error` event. Because of this, it is generally considered [standard](/what-are-the-error-conventions) to return errors through the callback rather than to use the `throw` statement. 50 | -------------------------------------------------------------------------------- /nodejs.org/locale/uk/knowledge/file-system/how-to-read-files-in-nodejs.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: How do I read files in node.js? 3 | date: '2011-08-26T10:08:50.000Z' 4 | tags: 5 | - filesystem 6 | difficulty: 2 7 | layout: knowledge-post.hbs 8 | --- 9 | 10 | Reading the contents of a file into memory is a very common programming task, and, as with many other things, the Node.js core API provides methods to make this trivial. There are a variety of file system methods, all contained in the `fs` module. The easiest way to read the entire contents of a file is with `fs.readFile`, as follows: 11 | 12 | fs = require('fs'); 13 | fs.readFile(file, [encoding], [callback]); 14 | 15 | // file = (string) filepath of the file to read 16 | 17 | `encoding` is an optional parameter that specifies the type of encoding to read the file. Possible encodings are 'ascii', 'utf8', and 'base64'. If no encoding is provided, the default is `null`. 18 | 19 | `callback` is a function to call when the file has been read and the contents are ready - it is passed two arguments, `error` and `data`. If there is no error, `error` will be `null` and `data` will contain the file contents; otherwise `err` contains the error message. 20 | 21 | So if we wanted to read `/etc/hosts` and print it to stdout (just like UNIX `cat`): 22 | 23 | fs = require('fs') 24 | fs.readFile('/etc/hosts', 'utf8', function (err,data) { 25 | if (err) { 26 | return console.log(err); 27 | } 28 | console.log(data); 29 | }); 30 | 31 | The contents of `/etc/hosts` should now be visible to you, provided you have permission to read the file in the first place. 32 | 33 | Let's now take a look at an example of what happens when you try to read an invalid file - the easiest example is one that doesn't exist. 34 | 35 | fs = require('fs'); 36 | fs.readFile('/doesnt/exist', 'utf8', function (err,data) { 37 | if (err) { 38 | return console.log(err); 39 | } 40 | console.log(data); 41 | }); 42 | 43 | This is the output: 44 | 45 | { stack: [Getter/Setter], 46 | arguments: undefined, 47 | type: undefined, 48 | message: 'ENOENT, No such file or directory \'/doesnt/exist\'', 49 | errno: 2, 50 | code: 'ENOENT', 51 | path: '/doesnt/exist' } 52 | 53 | This is a basic Node.js [Error object](/what-is-the-error-object) - it can often be useful to log `err.stack` directly, since this contains a stack trace to the location in code at which the Error object was created. 54 | -------------------------------------------------------------------------------- /nodejs.org/locale/uk/knowledge/file-system/how-to-search-files-and-directories-in-nodejs.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: How do I search files and directories? 3 | date: '2011-08-26T10:08:50.000Z' 4 | tags: 5 | - filesystem 6 | difficulty: 1 7 | layout: knowledge-post.hbs 8 | --- 9 | 10 | Suppose you want to list all the files in the current directory. One approach is to use the builtin `fs.readdir` [method](/how-do-i-read-files-in-node-js). This will get you an array of all the files and directories on the specified path: 11 | 12 | fs = require('fs'); 13 | 14 | fs.readdir(process.cwd(), function (err, files) { 15 | if (err) { 16 | console.log(err); 17 | return; 18 | } 19 | console.log(files); 20 | }); 21 | 22 | 23 | Unfortunately, if you want to do a recursive list of files, then things get much more complicated very quickly. To avoid all of this scary complexity, this is one of the places where a Node.js user-land library can save the day. [Node-findit](https://github.com/substack/node-findit), by SubStack, is a helper module to make searching for files easier. It has interfaces to let you work with callbacks, events, or just plain old synchronously (not a good idea most of the time). 24 | 25 | To install `node-findit`, simply use npm: 26 | 27 | npm install findit 28 | 29 | In the same folder, create a file called `example.js`, and then add this code. Run it with `node example.js`. This example uses the `node-findit` event-based interface. 30 | 31 | //This sets up the file finder 32 | var finder = require('findit').find(__dirname); 33 | 34 | //This listens for directories found 35 | finder.on('directory', function (dir) { 36 | console.log('Directory: ' + dir + '/'); 37 | }); 38 | 39 | //This listens for files found 40 | finder.on('file', function (file) { 41 | console.log('File: ' + file); 42 | }); 43 | -------------------------------------------------------------------------------- /nodejs.org/locale/uk/knowledge/file-system/how-to-write-files-in-nodejs.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: How do I write files in node.js? 3 | date: '2011-08-26T10:08:50.000Z' 4 | tags: 5 | - filesystem 6 | difficulty: 2 7 | layout: knowledge-post.hbs 8 | --- 9 | 10 | Writing to a file is another of the basic programming tasks that one usually needs to know about - luckily, this task is very simple in Node.js. We can use the handy `writeFile` method inside the standard library's `fs` module, which can save all sorts of time and trouble. 11 | 12 | fs = require('fs'); 13 | fs.writeFile(filename, data, [encoding], [callback]) 14 | 15 | `file = (string)` filepath of the file to read 16 | 17 | `data = (string or buffer)` the data you want to write to the file 18 | 19 | `encoding = (optional string)` the encoding of the `data`. Possible encodings are 'ascii', 'utf8', and 'base64'. If no encoding provided, then 'utf8' is assumed. 20 | 21 | `callback = (optional function (err) {})` If there is no error, `err === null`, otherwise `err` contains the error message. 22 | 23 | So if we wanted to write "Hello World" to `helloworld.txt`: 24 | 25 | fs = require('fs'); 26 | fs.writeFile('helloworld.txt', 'Hello World!', function (err) { 27 | if (err) return console.log(err); 28 | console.log('Hello World > helloworld.txt'); 29 | }); 30 | 31 | [contents of helloworld.txt]: 32 | Hello World! 33 | 34 | If we purposely want to cause an error, we can try to write to a file that we don't have permission to access: 35 | 36 | fs = require('fs') 37 | fs.writeFile('/etc/doesntexist', 'abc', function (err,data) { 38 | if (err) { 39 | return console.log(err); 40 | } 41 | console.log(data); 42 | }); 43 | 44 | { stack: [Getter/Setter], 45 | arguments: undefined, 46 | type: undefined, 47 | message: 'EACCES, Permission denied \'/etc/doesntexist\'', 48 | errno: 13, 49 | code: 'EACCES', 50 | path: '/etc/doesntexist' } 51 | -------------------------------------------------------------------------------- /nodejs.org/locale/uk/knowledge/getting-started/globals-in-node-js.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: The built-in globals in Node.js 3 | date: '2011-08-26T10:08:50.000Z' 4 | tags: 5 | - core 6 | - globals 7 | difficulty: 1 8 | layout: knowledge-post.hbs 9 | --- 10 | 11 | Node.js has a number of built-in global identifiers that every Node.js developer should have some familiarity with. Some of these are true globals, being visible everywhere; others exist at the module level, but are inherent to every module, thus being pseudo-globals. 12 | 13 | First, let's go through the list of 'true globals': 14 | 15 | - `global` - The global namespace. Setting a property to this namespace makes it globally visible within the running process. 16 | - `process` - Node's built-in `process` module, which provides interaction with the current Node process. [Read More](/articles/getting-started/the-process-module) 17 | - `console` - Node's built-in `console` module, which wraps various STDIO functionality in a browser-like way. [Read More](/articles/getting-started/the-console-module) 18 | - `setTimeout()`, `clearTimeout()`, `setInterval()`, `clearInterval()` - The built-in timer functions are globals. [Read More](/articles/javascript-conventions/what-are-the-built-in-timer-functions) 19 | 20 | As mentioned above, there are also a number of 'pseudo-globals' included at the module level in every module: 21 | 22 | - `module`, `module.exports`, `exports` - These objects all pertain to Node's module system. [Read More](/articles/getting-started/what-is-require) 23 | - __filename - The `__filename` keyword contains the path of the currently executing file. Note that this is not defined while running the [Node REPL](/articles/REPL/how-to-use-nodejs-repl). 24 | - __dirname - Like `__filename`, the `__dirname` keyword contains the path to the root directory of the currently executing script. Also not present in the Node REPL. 25 | - require() - The `require()` function is a built-in function, exposed per-module, that allows other valid modules to be included. [Read More](/articles/getting-started/what-is-require) 26 | 27 | Much of this functionality can be extremely useful for a Node.js developer's daily life - but at the very least, remember these as bad names to use for your own functions! 28 | -------------------------------------------------------------------------------- /nodejs.org/locale/uk/knowledge/getting-started/npm/how-to-access-module-package-info.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: How to access module package info 3 | date: '2011-08-26T10:08:50.000Z' 4 | tags: 5 | - core 6 | - npm 7 | difficulty: 1 8 | layout: knowledge-post.hbs 9 | --- 10 | 11 | 12 | There are many situations in the world of software development where using the wrong version of a dependency or submodule can cause all sorts of pain and anguish - luckily for you, node.js has a module available called pkginfo that can help keep these sorts of troubles at bay. 13 | 14 | Let's take a look at pkginfo - first, install via npm: 15 | 16 | npm install pkginfo 17 | 18 | Now all we need to do is require it, and invoke it. 19 | 20 | var pkginfo = require('pkginfo')(module); 21 | 22 | console.dir(module.exports); 23 | 24 | That would show us the entire contents of the package.json, neatly displayed to our console. If we only wanted certain pieces of information, we just specify them like so: 25 | 26 | var pkginfo = require('pkginfo')(module, 'version', 'author'); 27 | 28 | console.dir(module.exports); 29 | 30 | And only the fields we specify will be shown to us. 31 | 32 | For more information, see http://github.com/indexzero/ . 33 | -------------------------------------------------------------------------------- /nodejs.org/locale/uk/knowledge/index.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: База знань 3 | layout: knowledge-base-index.hbs 4 | --- 5 | 6 | # База знань 7 | -------------------------------------------------------------------------------- /nodejs.org/locale/uk/knowledge/javascript-conventions/what-are-truthy-and-falsy-values.md: -------------------------------------------------------------------------------- 1 | --- 2 | date: '2011-08-26T10:08:50.000Z' 3 | tags: 4 | - truthy 5 | - falsy 6 | - types 7 | - coercion 8 | title: 'What are "truthy" and "falsy" values?' 9 | difficulty: 4 10 | layout: knowledge-post.hbs 11 | --- 12 | 13 | 14 | Javascript is weakly typed language. That means different types can be 15 | used in operations and the language will try to convert the types 16 | until the operation makes sense. 17 | 18 | console.log("1" > 0); // true, "1" converted to number 19 | console.log(1 + "1"); // 11, 1 converted to string 20 | 21 | Type conversion also applys when values are used in unary boolean 22 | operations, most notably if statements. If a value converts to the 23 | boolean true, then it is said to be "truthy". If it converts to false 24 | it is "falsy". 25 | 26 | var myval = "value"; 27 | if(myval) { 28 | console.log("This value is truthy"); 29 | } 30 | 31 | myval = 0; 32 | if(!myval) { 33 | console.log("This value is falsy"); 34 | } 35 | 36 | Since most values in javascript are truthy, e.g. objects, arrays, most 37 | numbers and strings, it's easier to identify all of the falsy 38 | values. These are: 39 | 40 | false // obviously 41 | 0 // The only falsy number 42 | "" // the empty string 43 | null 44 | undefined 45 | NaN 46 | 47 | Note that all objects and arrays are truthy, even empty ones. 48 | 49 | Truthiness and Falsiness also come into play with logical 50 | operators. When using logical AND/OR, the values will be converted 51 | based on truthiness or falsyness and then the expression will resolve 52 | to the last truthy value. Short circuit rules apply. Here's an 53 | extended example. 54 | 55 | var first = "truthy" 56 | , second = "also truthy"; 57 | 58 | var myvalue = first && second; 59 | console.log(myvalue); // "also truthy" 60 | 61 | first = null; 62 | second = "truthy"; 63 | 64 | myvalue = first || second; 65 | console.log(myvalue); // "truthy" 66 | 67 | myvalue2 = second || first; 68 | console.log(myvalue2); // "truthy" 69 | 70 | var truthy = "truthy" 71 | , falsy = 0; 72 | 73 | myvalue = truthy ? true : false; 74 | myvalue = falsy ? true : false; 75 | -------------------------------------------------------------------------------- /nodejs.org/locale/uk/knowledge/other-resources/tutorials-and-how-tos.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Tutorials and How-Tos 3 | date: '2011-09-15T23:04:37.000Z' 4 | tags: 5 | - help 6 | - resources 7 | difficulty: 1 8 | layout: knowledge-post.hbs 9 | --- 10 | 11 | ## [Nodejitsu Blog](http://blog.nodejitsu.com) 12 | 13 | Nodejitsu's developers blog regularly about how to use node.js libraries, best practices *and* community news! 14 | 15 | ## [How To Node](http://howtonode.org) 16 | 17 | How To Node is a community-driven blog with lots of node.js tutorials, complete with code snippets. 18 | 19 | ## [The Node Beginner Book](http://nodebeginner.org/) 20 | 21 | The Node Beginner Book is a free book that teaches how to program with javascript and node.js by having the reader build a fully-functional bare-bones web application. 22 | 23 | ## [Node.js Guide](http://nodeguide.com/) 24 | 25 | Felix Geisendörfer, one of the very first people to use Node in production, assembled an unofficial guide not only on writing node apps, but also on coding style, the Node community and on convincing the boss. 26 | 27 | ## [Node Tuts](http://nodetuts.com/) 28 | 29 | Not only does Node Tuts have nearly two dozen screencasts on node, it also is the home of the e-book "Hands-On Node.js"! 30 | 31 | -------------------------------------------------------------------------------- /nodejs.org/locale/uk/styles.styl: -------------------------------------------------------------------------------- 1 | @import 'base' 2 | --------------------------------------------------------------------------------