<commit_before>---
layout: post
title: io.js 주간 뉴스 2015년 6월 26일
author: iojs
ref: io.js Week of June 26th — Node &amp; JavaScript
refurl: https://medium.com/node-js-javascript/
translator:
- <a href="https://github.com/freenice12" target="_blank">freenice12</a>
---

<!--
# io.js and Node.js News
This week we have one io.js [release v2.3.1](https://github.com/nodejs/io.js/blob/master/CHANGELOG.md#2015-06-23-version-231-rvagg), complete changelog from previous releases can be found [on GitHub](https://github.com/nodejs/io.js/blob/master/CHANGELOG.md).
-->

# io.js와 Node.js 소식
이번 주에는 io.js [v2.3.1](https://github.com/nodejs/io.js/blob/master/CHANGELOG.md#2015-06-23-version-231-rvagg) 배포가 있고, 전체 변경사항은 [GitHub](https://github.com/nodejs/io.js/blob/master/CHANGELOG.md)에서 확인할 수 있습니다.

<!--
### Notable changes
* **module**: The number of syscalls made during a `require()` have been significantly reduced again (see [#1801](https://github.com/nodejs/io.js/pull/1801) from v2.2.0 for previous work), which should lead to a performance improvement (<NAME>) [#1920](https://github.com/nodejs/io.js/pull/1920).
* **npm**:
  * Upgrade to [v2.11.2](https://github.com/npm/npm/releases/tag/v2.11.2) (<NAME>) [#1956](https://github.com/nodejs/io.js/pull/1956).
  * Upgrade to [v2.11.3](https://github.com/npm/npm/releases/tag/v2.11.3) (<NAME>vell) [#2018](https://github.com/nodejs/io.js/pull/2018).
* **zlib**: A bug was discovered where the process would abort if the final part of a zlib decompression results in a buffer that would exceed the maximum length of `0x3fffffff` bytes (~1GiB). This was likely to only occur during buffered decompression (rather than streaming). This is now fixed and will instead result in a thrown `RangeError` (<NAME>) [#1811](https://github.com/nodejs/io.js/pull/1811).
-->

### 주요 변경 사항

* **module**: `require()` 수행 중 syscalls의 횟수가 다시 급격하게 감소하게 되었고(참조 [#1801](https://github.com/nodejs/io.js/pull/1801) 이전 작업을 위한 v2.2.0부터 적용), 이로 인해 성능 향상이 있을 것입니다. (<NAME>) [#1920](https://github.com/nodejs/io.js/pull/1920).
* **npm**:
  * [v2.11.2](https://github.com/npm/npm/releases/tag/v2.11.2)로 업그레이드했습니다. (<NAME>) [#1956](https://github.com/nodejs/io.js/pull/1956).
  * [v2.11.3](https://github.com/npm/npm/releases/tag/v2.11.3)로 업그레이드했습니다. (<NAME>) [#2018](https://github.com/nodejs/io.js/pull/2018).
* **zlib**: 버퍼 안에서 zlib의 압축 해제 결과의 마지막 부분이 최대 길이인 `0x3fffffff`바이트 (~1기가)를 초과할 때 프로세스가 종료되던 버그가 발견되었습니다. 이 버그는 버퍼를 이용한(스트리밍을 이용하는 것보다는) 압축 해제에서만 나타나는 것 같습니다. 이 버그는 이제 해결되었고 앞으로는 `RangeError`가 발생할 것입니다. (<NAME>) [#1811](https://github.com/nodejs/io.js/pull/1811).

<!--
### Known issues
See https://github.com/nodejs/io.js/labels/confirmed-bug for complete and current list of known issues.
* Some problems with unreferenced timers running during `beforeExit` are still to be resolved. See [#1264](https://github.com/nodejs/io.js/issues/1264).
* Surrogate pair in REPL can freeze terminal [#690](https://github.com/nodejs/io.js/issues/690)
* `process.send()` is not synchronous as the docs suggest, a regression introduced in 1.0.2, see [#760](https://github.com/nodejs/io.js/issues/760) and fix in [#774](https://github.com/nodejs/io.js/issues/774)
* Calling `dns.setServers()` while a DNS query is in progress can cause the process to crash on a failed assertion [#894](https://github.com/nodejs/io.js/issues/894)
* `url.resolve` may transfer the auth portion of the url when resolving between two full hosts, see [#1435](https://github.com/nodejs/io.js/issues/1435).
-->

### 알려진 이슈

현재 알려진 이슈의 전체 목록은 [https://github.com/nodejs/io.js/labels/confirmed-bug](https://github.com/nodejs/io.js/labels/confirmed-bug)에서 보실 수 있습니다.

* `beforeExit` 중에 참조 해제된 타이머에 대한 문제가 아직 남아 있습니다. [#1264](https://github.com/iojs/io.js/issues/1264)
* REPL에 입력된 서로게이트 페어가 터미널을 얼릴 수 있습니다. [#690](https://github.com/iojs/io.js/issues/690)
* `process.send()`가 문서에 쓰인 것처럼 동기적이지 않으며, 이 문제는 1.0.2에서 발생했습니다. [#760](https://github.com/iojs/io.js/issues/760)과 [#774](https://github.com/iojs/io.js/issues/774)에서 해결했습니다.
* DNS 질의 진행 중에 호출된 `dns.setServers()`가 assertion 실패로 프로세스를 크래시시킬 수 있습니다. [#894](https://github.com/iojs/io.js/issues/894)
* `url.resolve`가 다른 두 호스트 사이를 해석하는 중 URL의 인증 정보 부분을 교환할 수 있습니다. [#1435](https://github.com/iojs/io.js/issues/1435)

<!--
### Community Updates
* Slide deck: [Bluemix Webinar: Deploying a Full Stack Node.js Application to IBM Bluemix](https://speakerdeck.com/bradleyholt/bluemix-webinar-deploying-a-full-stack-node-dot-js-application-to-ibm-bluemix)
* Article by RisingStack: [How to Use Rust with Node.js When Performance Matters](http://blog.risingstack.com/how-to-use-rust-with-node-when-performance-matters/)
* Device Atlas API now [supports Node.js](https://deviceatlas.com/blog/deviceatlas-api-node-js?utm_source=twitter&utm_medium=update&utm_campaign=node%20js%20support)
* [On Maintaining a Native Node Module](http://www.voodootikigod.com/on-maintaining-a-native-node-module/) by <NAME>
* [nodei.co](http://twitter.com/rvagg/status/613688739030679552) is running with io.js
* npm [3.0.0 pre-release](https://github.com/npm/npm/releases/tag/v3.0.0)
-->

### 커뮤니티 업데이트

* Slide deck(슬라이드): [Bluemix Webinar: IBM Bluemix에 풀 스택 Node.js 애플리케이션 배치하기](https://speakerdeck.com/bradleyholt/bluemix-webinar-deploying-a-full-stack-node-dot-js-application-to-ibm-bluemix)
* RisingStack의 글: [성능 문제가 있을 때 Rust와 Node.js를 사용하는 방법](http://blog.risingstack.com/how-to-use-rust-with-node-when-performance-matters/)
* Atlas 장치의 API가 이제 [Node.js를 지원합니다.](https://deviceatlas.com/blog/deviceatlas-api-node-js?utm_source=twitter&utm_medium=update&utm_campaign=node%20js%20support)
* <NAME>의 [Native 노드 모듈 유지하기](http://www.voodootikigod.com/on-maintaining-a-native-node-module/)
* [nodei.co](http://twitter.com/rvagg/status/613688739030679552)는 io.js와 함께 운영됩니다.
* npm [3.0.0 pre-release](https://github.com/npm/npm/releases/tag/v3.0.0)

<!--
### Upcoming Events
* [CascadiaJS](http://2015.cascadiajs.com/) tickets are on sale, July 8th - 10th at Washington State
* [BrazilJS Conf](http://braziljs.com.br/) tickets are on sale, August 21st - 22nd at Shopping Center BarraShoppingSul
* [NodeConf EU](http://nodeconf.eu/) tickets are on sale, September 6th - 9th at Waterford, Ireland
* [Node.js Italian Conference](http://nodejsconf.it/) tickets are on sale, October 10th at Desenzano - Brescia, Italy
* [JSConf CO](http://www.jsconf.co/), October 16th - 17th at Ruta N, Medellin<commit_msg>번역 수정 : io.js Week of June 26th 2015 ( #82 ) #84<commit_after>---
layout: post
title: io.js 주간 뉴스 2015년 6월 26일
author: iojs
ref: io.js Week of June 26th — Node &amp; JavaScript
refurl: https://medium.com/node-js-javascript/
translator:
- <a href="https://github.com/freenice12" target="_blank">freenice12</a>
---

<!--
# io.js and Node.js News
This week we have one io.js [release v2.3.1](https://github.com/nodejs/io.js/blob/master/CHANGELOG.md#2015-06-23-version-231-rvagg), complete changelog from previous releases can be found [on GitHub](https://github.com/nodejs/io.js/blob/master/CHANGELOG.md).
-->

# io.js와 Node.js 소식
이번 주에는 io.js [v2.3.1 배포](https://github.com/nodejs/io.js/blob/master/CHANGELOG.md#2015-06-23-version-231-rvagg)가 있고, 전체 변경사항은 [GitHub](https://github.com/nodejs/io.js/blob/master/CHANGELOG.md)에서 확인할 수 있습니다.

<!--
### Notable changes
* **module**: The number of syscalls made during a `require()` have been significantly reduced again (see [#1801](https://github.com/nodejs/io.js/pull/1801) from v2.2.0 for previous work), which should lead to a performance improvement (P<NAME>bert) [#1920](https://github.com/nodejs/io.js/pull/1920).
* **npm**:
  * Upgrade to [v2.11.2](https://github.com/npm/npm/releases/tag/v2.11.2) (<NAME>) [#1956](https://github.com/nodejs/io.js/pull/1956).
  * Upgrade to [v2.11.3](https://github.com/npm/npm/releases/tag/v2.11.3) (<NAME>) [#2018](https://github.com/nodejs/io.js/pull/2018).
* **zlib**: A bug was discovered where the process would abort if the final part of a zlib decompression results in a buffer that would exceed the maximum length of `0x3fffffff` bytes (~1GiB). This was likely to only occur during buffered decompression (rather than streaming). This is now fixed and will instead result in a thrown `RangeError` (<NAME>) [#1811](https://github.com/nodejs/io.js/pull/1811).
-->

### 주요 변경 사항

* **module**: `require()` 수행 중 시스템 콜의 횟수가 다시 급격하게 감소하게 되었고(v2.2.0부터 적용된 작업은 [#1801](https://github.com/nodejs/io.js/pull/1801)을 참조하세요), 이로 인해 성능 향상이 있을 것입니다. (<NAME>) [#1920](https://github.com/nodejs/io.js/pull/1920).
* **npm**:
  * [v2.11.2](https://github.com/npm/npm/releases/tag/v2.11.2)로 업그레이드했습니다. (<NAME>) [#1956](https://github.com/nodejs/io.js/pull/1956).
  * [v2.11.3](https://github.com/npm/npm/releases/tag/v2.11.3)로 업그레이드했습니다. (<NAME>) [#2018](https://github.com/nodejs/io.js/pull/2018).
* **zlib**: 버퍼 안에서 zlib의 압축 해제 결과의 마지막 부분이 최대 길이인 `0x3fffffff`바이트(~1기가)를 초과할 때 프로세스가 종료되던 버그가 발견되었습니다. 이 버그는 버퍼를 이용한(스트리밍을 이용하는 것보다는) 압축 해제에서만 나타나는 것 같습니다. 이 버그는 이제 해결되었고 앞으로는 `RangeError`가 발생할 것입니다. (<NAME>) [#1811](https://github.com/nodejs/io.js/pull/1811).

<!--
### Known issues
See https://github.com/nodejs/io.js/labels/confirmed-bug for complete and current list of known issues.
* Some problems with unreferenced timers running during `beforeExit` are still to be resolved. See [#1264](https://github.com/nodejs/io.js/issues/1264).
* Surrogate pair in REPL can freeze terminal [#690](https://github.com/nodejs/io.js/issues/690)
* `process.send()` is not synchronous as the docs suggest, a regression introduced in 1.0.2, see [#760](https://github.com/nodejs/io.js/issues/760) and fix in [#774](https://github.com/nodejs/io.js/issues/774)
* Calling `dns.setServers()` while a DNS query is in progress can cause the process to crash on a failed assertion [#894](https://github.com/nodejs/io.js/issues/894)
* `url.resolve` may transfer the auth portion of the url when resolving between two full hosts, see [#1435](https://github.com/nodejs/io.js/issues/1435).
-->

### 알려진 이슈

현재 알려진 이슈의 전체 목록은 [https://github.com/nodejs/io.js/labels/confirmed-bug](https://github.com/nodejs/io.js/labels/confirmed-bug)에서 보실 수 있습니다.

* `beforeExit` 중에 참조 해제된 타이머에 대한 문제가 아직 남아 있습니다. [#1264](https://github.com/iojs/io.js/issues/1264)
* REPL에 입력된 서로게이트 페어가 터미널을 얼릴 수 있습니다. [#690](https://github.com/iojs/io.js/issues/690)
* `process.send()`가 문서에 쓰인 것처럼 동기적이지 않으며, 이 문제는 1.0.2에서 발생했습니다. [#760](https://github.com/iojs/io.js/issues/760)과 [#774](https://github.com/iojs/io.js/issues/774)에서 해결했습니다.
* DNS 질의 진행 중에 호출된 `dns.setServers()`가 assertion 실패로 프로세스를 크래시시킬 수 있습니다. [#894](https://github.com/iojs/io.js/issues/894)
* `url.resolve`가 다른 두 호스트 사이를 해석하는 중 URL의 인증 정보 부분을 교환할 수 있습니다. [#1435](https://github.com/iojs/io.js/issues/1435)

<!--
### Community Updates
* Slide deck: [Bluemix Webinar: Deploying a Full Stack Node.js Application to IBM Bluemix](https://speakerdeck.com/bradleyholt/bluemix-webinar-deploying-a-full-stack-node-dot-js-application-to-ibm-bluemix)
* Article by RisingStack: [How to Use Rust with Node.js When Performance Matters](http://blog.risingstack.com/how-to-use-rust-with-node-when-performance-matters/)
* Device Atlas API now [supports Node.js](https://deviceatlas.com/blog/deviceatlas-api-node-js?utm_source=twitter&utm_medium=update&utm_campaign=node%20js%20support)
* [On Maintaining a Native Node Module](http://www.voodootikigod.com/on-maintaining-a-native-node-module/) by <NAME>
* [nodei.co](http://twitter.com/rvagg/status/613688739030679552) is running with io.js
* npm [3.0.0 pre-release](https://github.com/npm/npm/releases/tag/v3.0.0)
-->

### 커뮤니티 업데이트

* Slide deck(슬라이드): [Bluemix Webinar: IBM Bluemix에 풀 스택 Node.js 애플리케이션 배치하기](https://speakerdeck.com/bradleyholt/bluemix-webinar-deploying-a-full-stack-node-dot-js-application-to-ibm-bluemix)
* RisingStack의 글: [성능 문제가 있을 때 Rust와 Node.js를 사용하는 방법](http://blog.risingstack.com/how-to-use-rust-with-node-when-performance-matters/)
* Device Atlas의 API가 이제 [Node.js를 지원합니다.](https://deviceatlas.com/blog/deviceatlas-api-node-js?utm_source=twitter&utm_medium=update&utm_campaign=node%20js%20support)
* <NAME>의 [Native 노드 모듈 유지하기](http://www.voodootikigod.com/on-maintaining-a-native-node-module/)
* [nodei.co](http://twitter.com/rvagg/status/613688739030679552)는 io.js와 함께 운영됩니다.
* npm [사전 릴리스 3.0.0](https://github.com/npm/npm/releases/tag/v3.0.0)

<!--
### Upcoming Events
* [CascadiaJS](http://2015.cascadiajs.com/) tickets are on sale, July 8th - 10th at Washington State
* [BrazilJS Conf](http://braziljs.com.br/) tickets are on sale, August 21st - 22nd at Shopping Center BarraShoppingSul
* [NodeConf EU](http://nodeconf.eu/) tickets are on sale, September 6th - 9th at Waterford, Ireland
* [Node.js Italian Conference](http://nodejsconf.it/) tickets are on sale, October 10th at Desenzano - Brescia, Italy
* [JSConf CO](http://www.jsconf.co/), October 16th - 17th at Ruta N, Medellin
{'fraction_non_alphanumeric': 0.171026000311381, 'fraction_numerical': 0.05153355130001557, 'mean_word_length': 4.286831275720164, 'pattern_counts': {'":': 0, '<': 37, '<?xml version=': 0, '>': 35, 'https://': 82, 'lorem ipsum': 0, 'www.': 6, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 4, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '4919751', 'n_tokens_mistral': 6122, 'n_tokens_neox': 6069, 'n_words': 1117}