diff --git a/.markdownlint.json b/.markdownlint.json index a4f8932e1a2dc..349f6343c010b 100644 --- a/.markdownlint.json +++ b/.markdownlint.json @@ -2,7 +2,6 @@ "default": true, "MD004": false, "MD009": false, - "MD012": false, "MD013": false, "MD022": false, "MD024": false, diff --git a/COLLABORATOR_GUIDE.md b/COLLABORATOR_GUIDE.md index 0e77e287da9ca..caadb31add19c 100644 --- a/COLLABORATOR_GUIDE.md +++ b/COLLABORATOR_GUIDE.md @@ -201,7 +201,6 @@ link to the markup. It's essential to update the handlebars paths to site.json. {{site.locale}}/{{site.getinvolved.events.link}} ``` - ### Translating pages See [TRANSLATION.md](./TRANSLATION.md) for the website translation policy. diff --git a/README.md b/README.md index d689acefb0a93..285a329e62684 100644 --- a/README.md +++ b/README.md @@ -47,7 +47,6 @@ If you want to submit a new feature or a bugfix, the best way is to create the c * `npm run serve -- --preserveLocale` builds all languages and adds the pages present in the english locale that are missing. * Multiple locales can be built by using comma separated values in the DEFAULT_LOCALE option. i.e: DEFAULT_LOCALE=en,es,it - ### Deployment Full set up is in https://github.com/nodejs/build/tree/master/setup/www minus secrets and certificates. The webhook is setup on GitHub for this project and talks to a small Node server on the host which does the work. See the [github-webhook](https://github.com/rvagg/github-webhook) package for this. diff --git a/TRANSLATION.md b/TRANSLATION.md index b2e3294f8e1aa..8725a03826561 100644 --- a/TRANSLATION.md +++ b/TRANSLATION.md @@ -4,7 +4,6 @@ Node.js is a global platform and so this site has many translations. The transla languages other than English is handled by the localization working group of the language in question. If you would like to contribute to the translation of nodejs.org, please refer to the following process: - ## For Individuals wanting to contribute * Contact your appropriate localization group, and discuss with them the best possible way to contribute. A list of the localization groups can be found here (please keep in mind that some groups have not yet taken action upon the project name changes, hence the outdated repository names): @@ -44,7 +43,6 @@ would like to contribute to the translation of nodejs.org, please refer to the f * [`nodejs-uk`](https://github.com/nodejs/nodejs-uk) Ukrainian Community * [`nodejs-vi`](https://github.com/nodejs/nodejs-vi) Vietnamese Community - ## For Localization Groups * Ensure that any site translations are done as pull requests into the appropriate language folder in this repo. This will ensure the build process, layout, and styling, remain consistent across the different translations of the site. diff --git a/locale/ar/about/community.md b/locale/ar/about/community.md index 27afcceda56af..47c84a2cc2087 100644 --- a/locale/ar/about/community.md +++ b/locale/ar/about/community.md @@ -39,7 +39,6 @@ layout: about.hbs إذا كنت مهتما بالانضمام إلى لجنة المجتمع كعضو ، عليك بقراءة القسم المعنون بـ **المراقبون و الأعضاء** ، و إنشاء مشكلة تطلب فيها ان تكون مراقباً في اجتماعنا القادم للجنة المجتمع. يمكنك إيجاد مثال رائعا لمثل هذه الحالة [هنا](https://github.com/nodejs/community-committee/issues/142). - ## المراقبون و الأعضاء أذا كنت راغبا بأن تصبح مساهما بشكل اعمق في لجنة المجتمع و مشروعاتها، فإننا نحثك على ان تكون مراقبا نشيطا و على أن تعمل للحصول على عضويتك، وحتى تصبح عضوا فعليك اتباع القواعد التالية: @@ -59,4 +58,3 @@ layout: about.hbs تتبع لجنة المجتمع نموذج اتخاذ القرارات المسمى [Consensus Seeking](https://en.wikipedia.org/wiki/Consensus-seeking_decision-making) عندما يتم الاتفاق على موضوع معين في الاجندة، يسأل المشرف "هل يعترض أحد؟" كنداء أخير للمعارضة من الإجماع. إذا لم يتم الوصول إلى إجماع كلي يتم الأخذ بتصويت الأغلبية، و من المتوقع أن أغلب القرارات المتخذة من طرف لجنة المجتمع تتم عبر عملية تقصي الإجماع و أن التصويت يتخذ كوسيلة أخيرة لاتخاذ القرار. - diff --git a/locale/ar/about/index.md b/locale/ar/about/index.md index ff3964176fba1..9fd60fca61722 100644 --- a/locale/ar/about/index.md +++ b/locale/ar/about/index.md @@ -48,7 +48,6 @@ server.listen(port, hostname, () => { يجب عليك ان تدرك ان تصميم Node.js بدون خيوط (threads) لا يعني انك لا تستطيع تحقيق الاستفادة الكاملة من الانوية المتعددة في البيئة التي تعمل عليها، فيمكن توليد المعالجات الفرعية عبر واجهة برمجة التطبيقات [`child_process.fork()`][] الخاصة بنا حيث انها مصممة لتكون سهلة التعامل. هناك ايضا نموذج [`cluster`][] المبني على نفس الواجهة والذي يسمح لك بمشاركة المآخذ (sockets) بين العمليات لموازنة الحمل على الانوية الخاصة بك. - [Blocking vs Non-Blocking]: https://nodejs.org/en/docs/guides/blocking-vs-non-blocking/ [`child_process.fork()`]: https://nodejs.org/api/child_process.html#child_process_child_process_fork_modulepath_args_options [`cluster`]: https://nodejs.org/api/cluster.html diff --git a/locale/ar/about/working-groups.md b/locale/ar/about/working-groups.md index da3741341fe13..ef65e60d94fbb 100644 --- a/locale/ar/about/working-groups.md +++ b/locale/ar/about/working-groups.md @@ -29,7 +29,6 @@ title: مجموعات العمل تشمل مسؤوليات هذه المجموعة: * صيانة مستودع [NAN](https://github.com/nodejs/nan) على الـGitHub، بما في ذلك الشفرة البرمجة، والمشاكل و التوثيق الخاص به - * صيانة مستودع [addon-examples](https://github.com/nodejs/node-addon-examples) على الـGitHub، بما في ذلك الشفرة البرمجية، والمشاكل والتوثيق الخاص به * صيانة اضافة واجهة برمجة التطبيق المكتوبة بالـ C++ الخاصة بمشروع Node.js، تحت اشراف لجنة التوجيه التقني. * صيانة التوثيق الخاص بالإضافة في إطار مشروع Node.js تحت اشراف لجنة التوجيه التقني للنود جي اس. diff --git a/locale/ar/docs/guides/abi-stability.md b/locale/ar/docs/guides/abi-stability.md index ddce21b75ba39..1a9c65cd54aa0 100644 --- a/locale/ar/docs/guides/abi-stability.md +++ b/locale/ar/docs/guides/abi-stability.md @@ -14,7 +14,6 @@ layout: docs.hbs يجب على التطبيق الذي يستعمل الواجهة الثنائية للتطبيق أن يُفسر بطريقة تجعل العناوين و الإعدادات المتوقعة و أحجام هياكل الذاكرة و الأنساق متوافقة مع تلك التي تم بواسطتها تفسير مزود الواجهة الثنئاية للتطبيق، ويتم تحقيق هذا عادة عبر التفسير باستخدام الترويس التي تم توفيرها من طرف مزود الواجهة الثنائية للتطبيق. - بما أن مزود الواجهة الثنائية للتطبيق و مستخدم الواجهة الثنائية للتطبيق قد يتم تفسيرهما في أوقات مختلفة باستعمال نسخ مفسرات مختلفة، فإن القطعة المسؤولة عن عن ضمان توافق الواجهة الثنائية للتطبيق تكون داخل المفسر. يجب على النسخ المختلفة من المفسرات التي قد يتم توفيرها من طرف بائعين مختلفين أن تنتج نفس النسخة من الواجهة الثنائية للتطبيق انطلاقا من ملف ترويسة ذو محتوى محدد، كما يجب عليها ان تنتج شيفرة خاصة بالتطبيق باستعمال الواجهة الثنائية للتطبيق التي يمكنها الوصول إلى الواجهة البرمجية @@ -43,6 +42,5 @@ layout: docs.hbs ينطوي الـ N-API على نسخ عدة لكون أن هناك واجهات برمجية جديدة تضاف من وقت ﻵخر، وعكس الترميز الدلالي، فإن تنسيخ الـ N-API هو تراكمي، أي أن كل نسخة منه تمثل نفس المعنى للنسخ الثانوية في نظام الترميز الدلالي و بالتالي فإن كل التغييرات التي يتم إجراؤها على الـ N-API تكون متوافقة مع النسخ الأقدم. إضافة إلى ما سبق، فإن هناك نسخ جديدة من الـ N-API تضاف تحت بند "تجريبي" لإعطاء المجتمع الفرصة لفحصها في بيئة إنتاجية. تعني الحالة التجريبية أنه على الرغم من ان هناك اهتماماً لضمان أن ﻻ يجب تعديل الواجهات البرمجية الجديدة بطريقة تلغي توافق الواجهات الثنائية للتطبيقات مستقبلا، فإنه لم يتم الموافقة على كونها صحيحة و مفيدة بشكل كافٍ في الانتاج كما تم تصميمها، وعليه فيمكنها ان تنطوي على تغييرات غير متوافقة مع الواجهات الثنائية للتطبيق قبل أن يتم دمجها أخيراً مع نسخة قادمة من الـ N-API. بمعنى آخر، فإن نسخة تجريبية من الـ N-API لا يُضمن ان تحقق توافقا متقدما. - [`node_api.h`]: https://github.com/nodejs/node/blob/master/src/node_api.h [`node_api_types.h`]: https://github.com/nodejs/node/blob/master/src/node_api_types.h diff --git a/locale/ar/docs/guides/anatomy-of-an-http-transaction.md b/locale/ar/docs/guides/anatomy-of-an-http-transaction.md index 27de5b12c9f2c..7928c58edd199 100644 --- a/locale/ar/docs/guides/anatomy-of-an-http-transaction.md +++ b/locale/ar/docs/guides/anatomy-of-an-http-transaction.md @@ -10,7 +10,6 @@ layout: docs.hbs بقليلا من Node.js [`EventEmitters`][] و [`Streams`][]. إذا لم تكن فِعْلاً على دِرَايَة بهم وإنه الجَدِير قيام بقراءة سريعة من خلال توثيقات واجهة برمجة التطبيقات (API) لكل منهم. - ## إنشاء الخادم أي تطبيق خادم الويب node وفي نقطة ما لإنشاء كائن خادم الويب، يتم ذلك @@ -29,7 +28,6 @@ const server = http.createServer((request, response) => { بواسطة [`createServer`][] هو مُصدِر الحدث [`EventEmitter`][] و ما لدينا هنا فقط إختزال لإنشاء كائن الخادم `server` وبعدها إضافة المستمع لاحقا. - ```javascript const server = http.createServer(); server.on('request', (request, response) => { @@ -44,7 +42,6 @@ server.on('request', (request, response) => { `server` في أغلب الحالات، كل ماتحتاج لتمريره للمستمع `listen` هو رقم المنفذ "port" الذي تريد الخادم الإستماع إليه، يوجد بعض الخيارات الاخرى أيضا لذا راجع المرجع [API reference][]. - ## طريقة 'Method' و رابط 'URL' و رؤوس 'Headers' عند معالجة الطلب أول حاجَة ربما تود القيام بها هي تفقد الطرق و الرابط URL، لذا @@ -81,7 +78,6 @@ const userAgent = headers['user-agent']; هذا التدفق يمكن الإستماع له أو نقله كأي تدفق أخر. يمكنك أخذ البيانات مباشرة من التدفق عن طريق الإستماع إلى أحداث التدفقات `'data'` و `'end'`. - الأجزاء الباعثة في كل `'data'` والحدث هو [`Buffer`][]. إذا كنت تعرف أنها ستكون سِلْسِلَة من البيانات، أفضل شئ تفعله هو تجميع البيانات في مصفوفة وبعدها في `'end'`، الرصفهم وتحويلهم إلى نصوص. @@ -149,7 +145,6 @@ http.createServer((request, response) => { في حَقِيقَةِ الأمْر إذا عَرَض هذا في المتصفح، طلبك سيكون خارج المهلة ولاشئ يعاد .إرساله للعميل - حتى الآن نحن لم نلمس كائن الجواب `response` كلياً. أَيّما في ما ذاك لـ[`ServerResponse`][] و مِمّ هو [`WritableStream`][]. أنه يحتوي على العديد من الطرق المفيدة لإرسال البيانات الراجعة لعميل و سنقوم بتغطية ذلك لاحقا. @@ -380,8 +375,6 @@ http.createServer((request, response) => { الكثير مثل هذه الأشياء مزودة بـAPIs لذا تأكد من قرأة التوثيقات الAPI منها [`EventEmitters`][] و [`Streams`][] و [`HTTP`][]. - - [`EventEmitters`]: https://nodejs.org/api/events.html [`Streams`]: https://nodejs.org/api/stream.html [`createServer`]: https://nodejs.org/api/http.html#http_http_createserver_requestlistener diff --git a/locale/ar/docs/guides/debugging-getting-started.md b/locale/ar/docs/guides/debugging-getting-started.md index 1aaa3adef8ab2..28e102a93c497 100644 --- a/locale/ar/docs/guides/debugging-getting-started.md +++ b/locale/ar/docs/guides/debugging-getting-started.md @@ -101,8 +101,6 @@ layout: docs.hbs يبين الجدول الآتي تأثير كل تخصيص خاص بوقت التشغيل على تصحيح الأخطاء: - - @@ -174,7 +172,6 @@ layout: docs.hbs فلنفترض أنك قمت بتشغيل الـ Node في حاسوب بعيد، remote.example.com على سبيل المثال، و تريد ان تتمكن من تصحيح الأخطاء فيها. في ذلك الحاسوب البعيد، عليك بدء عملية node مع جعل المدقق يستمع على المضيف المحلي فقط (وهو الافتراضي). - ```bash node --inspect server.js ``` diff --git a/locale/ar/docs/guides/index.md b/locale/ar/docs/guides/index.md index d701fb94c8f32..bd1d76debb13d 100644 --- a/locale/ar/docs/guides/index.md +++ b/locale/ar/docs/guides/index.md @@ -13,17 +13,13 @@ layout: docs.hbs - [عمل دوكر على تطبيق ويب Node.js](nodejs-docker-webapp/) - [ترحيل إلى منشئات Buffer آمنة](buffer-constructor-deprecation/) - ## المفاهيم الأساسية في الـ Node.js - - [مقارنة عامة بين Blocking و Non-Blocking](blocking-vs-non-blocking/) - [الـ Node.js حلقة التكرارية، المؤقتات و process.nextTick()](event-loop-timers-and-nexttick/) - [لا تعرقل الحلقة التكرارية (أو يحشد العمل)](dont-block-the-event-loop/) - [مؤقتات في Node.js](timers-in-node/) - - ## الأدلة لوحدة المتعلقة - [التشريح لمعاملات HTTP](anatomy-of-an-http-transaction/) diff --git a/locale/ar/download/package-manager.md b/locale/ar/download/package-manager.md index 3d66a128b89a1..84b22002da490 100644 --- a/locale/ar/download/package-manager.md +++ b/locale/ar/download/package-manager.md @@ -210,7 +210,6 @@ pkgin -y install nodejs cd pkgsrc/lang/nodejs && bmake install ``` - ## Solus توفر Solus النود جي اس في مستودعها الرئيسي. @@ -219,7 +218,6 @@ cd pkgsrc/lang/nodejs && bmake install sudo eopkg install nodejs ``` - ## Void Linux يوفر Void Linux نسخة مستقرة من النود جي اس في المستودع الرئيسي. diff --git a/locale/ar/get-involved/node-meetups.md b/locale/ar/get-involved/node-meetups.md index 12f31757cbb60..c04f4f0522b11 100644 --- a/locale/ar/get-involved/node-meetups.md +++ b/locale/ar/get-involved/node-meetups.md @@ -60,7 +60,6 @@ layout: contribute.hbs - المنظم - جيمس ريتشاردسون. المشارك في تنظيم: جيسيكا كلير - معلومات الاتصال بالمنظم - - ### بلجيكا #### بروكسل @@ -118,7 +117,6 @@ layout: contribute.hbs - المنظم - ثياغو ادريانو - معلومات الاتصال بالمنظم - - ### فنلندا #### اوسيما @@ -143,7 +141,6 @@ layout: contribute.hbs - المنظم - كاميلو مونتويا - معلومات الاتصال بالمنظم - - ### فرنسا #### ايل-دو-فرانس @@ -314,7 +311,6 @@ layout: contribute.hbs - أسماء المنظمون - دان ت. وبول د. - معلومات الاتصال بالمنظم - _مجتمع سلاك_ - ### الولايات المتحدة #### أريزونا @@ -327,7 +323,6 @@ layout: contribute.hbs - المنظم - كريس ماتيو - معلومات الاتصال بالمنظم - - #### كاليفورنيا ##### إرفين @@ -352,7 +347,6 @@ layout: contribute.hbs - المنظم - مات باردي - معلومات الاتصال بالمنظم - - #### كولورادو ##### دنفر @@ -433,7 +427,6 @@ layout: contribute.hbs - المنظم - زيكي نيرينبرج وبن نيسواندر - معلومات الاتصال بالمنظم - #### شمال كارولينا ##### رالي @@ -492,7 +485,6 @@ layout: contribute.hbs - المنظم - آرون سيث مادسن - معلومات الاتصال بالمنظم - - #### واشنطن ##### سياتل @@ -541,7 +533,6 @@ layout: contribute.hbs - المنظم: جو باري - مساعد منظم: روب موران - معلومات الاتصال بالمنظم - - ### اوكرانيا #### كييف diff --git a/locale/ca/get-involved/index.md b/locale/ca/get-involved/index.md index 52ffb407d15b5..d99401b3ce63e 100644 --- a/locale/ca/get-involved/index.md +++ b/locale/ca/get-involved/index.md @@ -23,7 +23,6 @@ layout: contribute.hbs - L'[etiqueta de Node.js en la DEV Community](https://dev.to/t/node) és un lloc on compartir projectes de Node.js, articles i tutorials, així com iniciar debats i demanar realimentació sobre temes relacionats amb Node.js. Els desenvolupadors de tots els nivells d'experiència són benvinguts a participar. - [Nodeiflux](https://discordapp.com/invite/vUsrbjd) és una comunitat amigable de desenvolupadors de backend amb Node.js que es recolzen mútuament a Discord. - ## Llocs de la comunitat internacional i projectes - [Comunitat Xinesa de Node.js](https://cnodejs.org/) diff --git a/locale/ca/security.md b/locale/ca/security.md index ab7ac045fc02e..57bdc48d71b09 100644 --- a/locale/ca/security.md +++ b/locale/ca/security.md @@ -50,7 +50,6 @@ Les notificacions de seguretat seran distribuïdes usant els següents mitjans. - - - ## Comentaris sobre aquesta política Si vostè té suggeriments sobre com pot ser millorat aquest procés, si us plau enviï un [pull request](https://github.com/nodejs/nodejs.org) diff --git a/locale/en/blog/announcements/foundation-advances-growth.md b/locale/en/blog/announcements/foundation-advances-growth.md index f15305985404d..9d4847e3a846d 100644 --- a/locale/en/blog/announcements/foundation-advances-growth.md +++ b/locale/en/blog/announcements/foundation-advances-growth.md @@ -50,4 +50,3 @@ In addition, the Foundation announced three new Silver members to the team, Apig #### About Node.js Foundation Node.js Foundation is a collaborative open source project dedicated to building and supporting the Node.js platform and other related modules. Node.js is used by tens of thousands of organizations in more than 200 countries and amasses more than 2 million downloads per month. It is the runtime of choice for high-performance, low latency applications, powering everything from enterprise applications, robots, API engines, cloud stacks and mobile websites. The Foundation is made up of a diverse group of companies including Platinum members Famous, IBM, Intel, Joyent, Microsoft, PayPal and Red Hat. Gold members include GoDaddy, NodeSource and Modulus/Progress Software, and Silver members include Apigee, Codefresh, DigitalOcean, Fidelity, Groupon, nearForm, npm, RisingStack, Sauce Labs, SAP, StrongLoop (an IBM company), YLD!, and Yahoo!. Get involved here: [https://nodejs.org](https://nodejs.org). - diff --git a/locale/en/blog/announcements/interactive-2016-ams.md b/locale/en/blog/announcements/interactive-2016-ams.md index 0322325de07dd..d35d0d0f5429d 100644 --- a/locale/en/blog/announcements/interactive-2016-ams.md +++ b/locale/en/blog/announcements/interactive-2016-ams.md @@ -81,4 +81,3 @@ About the Node.js Foundation Node.js is used by tens of thousands of organizations in more than 200 countries and amasses more than 4 million active users per month. It is the runtime of choice for high-performance, low latency applications, powering everything from enterprise applications, robots, API engines, cloud stacks and mobile websites. The Foundation is made up of a diverse group of companies including Platinum members IBM, Intel, Joyent, Microsoft, PayPal and Red Hat. Gold members include GoDaddy and NodeSource, and Silver members include Apigee, AppDynamics, Codefresh, DigitalOcean, Fidelity, Google, Groupon, nearForm, New Relic, npm, Opbeat, RisingStack, Sauce Labs, SAP, StrongLoop (an IBM company), Sphinx, YLD, and Yahoo!. Get involved here: [https://nodejs.org](https://nodejs.org). - diff --git a/locale/en/blog/community/2017-election.md b/locale/en/blog/community/2017-election.md index f7a5998d6092a..3216e0f2a58a9 100644 --- a/locale/en/blog/community/2017-election.md +++ b/locale/en/blog/community/2017-election.md @@ -79,5 +79,4 @@ required to have a GitHub account to register. through the two above-mentioned elected Individual Membership Directors. - 20% off regular price registration to Node Interactive 2017 - See you at the (digital)poll? diff --git a/locale/en/blog/community/next-chapter.md b/locale/en/blog/community/next-chapter.md index d69957597278b..9717aac2c4b7d 100644 --- a/locale/en/blog/community/next-chapter.md +++ b/locale/en/blog/community/next-chapter.md @@ -99,5 +99,3 @@ much help and support to the rest of the core team as they need. However, I won't have the time to participate at the level needed to remain a core contributor. With the core team and the community working together, I know they won't miss a step. - - diff --git a/locale/en/blog/community/quality-with-speed.md b/locale/en/blog/community/quality-with-speed.md index eef1bc4dc427d..312beabfa23ec 100644 --- a/locale/en/blog/community/quality-with-speed.md +++ b/locale/en/blog/community/quality-with-speed.md @@ -183,7 +183,6 @@ on implementation. The result being that the merits of the concept can be discussed at the appropriate level of abstraction without having to review all of the technical details. - # Automation and Testing Automation and Testing are key strategies that go hand in hand in allowing @@ -215,7 +214,6 @@ These levels include: * Development Workflows * Use Case Testing - ## Functional Tests Functional tests are the first level of defense. Our collaborator guidelines @@ -302,8 +300,6 @@ Our current strategy is to get some of this coverage through the benchmarking that we put in place, but it is another area we can work on once we have the other levels of testing in place. - - # Performance Benchmarks While ensuring functional stability is good, its not enough. We also need diff --git a/locale/en/blog/feature/streams2.md b/locale/en/blog/feature/streams2.md index b5cc6daf198a0..38aac22b213fb 100644 --- a/locale/en/blog/feature/streams2.md +++ b/locale/en/blog/feature/streams2.md @@ -535,7 +535,6 @@ the `read()` method. Resumes the incoming `'data'` events after a `pause()`. - ## Class: stream.Writable @@ -592,7 +591,6 @@ the class that defines it, and should not be called directly by user programs. However, you **are** expected to override this method in your own extension classes. - ### writable.write(chunk, [encoding], [callback]) * `chunk` {Buffer | String} Data to be written @@ -842,7 +840,6 @@ source.pipe(parser) // with the parsed header data. ``` - ## Class: stream.PassThrough This is a trivial implementation of a `Transform` stream that simply @@ -850,5 +847,4 @@ passes the input bytes across to the output. Its purpose is mainly for examples and testing, but there are occasionally use cases where it can come in handy. - [EventEmitter]: https://nodejs.org/api/events.html#events_class_eventemitter diff --git a/locale/en/blog/release/v0.10.0.md b/locale/en/blog/release/v0.10.0.md index c2e38cc4a9728..b2977673d58ff 100644 --- a/locale/en/blog/release/v0.10.0.md +++ b/locale/en/blog/release/v0.10.0.md @@ -109,7 +109,6 @@ place.) As a result, latency is much more predictable and stable. You won't see a difference in the benchmarks as a result of this, but you'll probably find that your app's response times are more reliable. - ## Performance and Benchmarks When the Streams2 feature first landed in master, it disrupted a lot @@ -288,7 +287,6 @@ everything that sits on *top* of TCP (that is, TLS and HTTP). Keep an eye out for more work in this area. Fast is never fast enough! - ## Continuous Integration To support a higher degree of stability, and hopefully catch issues @@ -304,7 +302,6 @@ easy for things to slip by, and our ad-hoc methods are not cutting it any longer. This promises a much lower incidence of the sort of regressions that delayed the release of v0.10 for several months. - ## Growing Out A year ago, we said that the innovation in the Node universe would be @@ -441,7 +438,6 @@ And now, the traditional release notes: * win/tty: don't touch insert mode or quick edit mode (Bert Belder) - Source Code: https://nodejs.org/dist/v0.10.0/node-v0.10.0.tar.gz Macintosh Installer (Universal): https://nodejs.org/dist/v0.10.0/node-v0.10.0.pkg diff --git a/locale/en/blog/release/v0.10.1.md b/locale/en/blog/release/v0.10.1.md index 888f589e84b32..884df1a73e41a 100644 --- a/locale/en/blog/release/v0.10.1.md +++ b/locale/en/blog/release/v0.10.1.md @@ -37,7 +37,6 @@ layout: blog-post.hbs * node: Unwrap without aborting in handle fd getter (isaacs) - Source Code: https://nodejs.org/dist/v0.10.1/node-v0.10.1.tar.gz Macintosh Installer (Universal): https://nodejs.org/dist/v0.10.1/node-v0.10.1.pkg diff --git a/locale/en/blog/release/v0.10.10.md b/locale/en/blog/release/v0.10.10.md index c557ebce39653..d3b56b3f97577 100644 --- a/locale/en/blog/release/v0.10.10.md +++ b/locale/en/blog/release/v0.10.10.md @@ -17,7 +17,6 @@ layout: blog-post.hbs * stream: unshift('') is a noop (isaacs) - Source Code: https://nodejs.org/dist/v0.10.10/node-v0.10.10.tar.gz Macintosh Installer (Universal): https://nodejs.org/dist/v0.10.10/node-v0.10.10.pkg diff --git a/locale/en/blog/release/v0.10.11.md b/locale/en/blog/release/v0.10.11.md index 82eca86ec0d05..f43c3710914f1 100644 --- a/locale/en/blog/release/v0.10.11.md +++ b/locale/en/blog/release/v0.10.11.md @@ -23,8 +23,6 @@ layout: blog-post.hbs * net: Fix busy loop on POLLERR|POLLHUP on older linux kernels (Ben Noordhuis, isaacs) - - Source Code: https://nodejs.org/dist/v0.10.11/node-v0.10.11.tar.gz Macintosh Installer (Universal): https://nodejs.org/dist/v0.10.11/node-v0.10.11.pkg diff --git a/locale/en/blog/release/v0.10.12.md b/locale/en/blog/release/v0.10.12.md index 33a4b8276dd9b..d5bed385c3952 100644 --- a/locale/en/blog/release/v0.10.12.md +++ b/locale/en/blog/release/v0.10.12.md @@ -21,7 +21,6 @@ layout: blog-post.hbs * configure: fix cross-compilation host_arch_cc() (Andrei Sedoi) - Source Code: https://nodejs.org/dist/v0.10.12/node-v0.10.12.tar.gz Macintosh Installer (Universal): https://nodejs.org/dist/v0.10.12/node-v0.10.12.pkg diff --git a/locale/en/blog/release/v0.10.13.md b/locale/en/blog/release/v0.10.13.md index 2302f73bf0b12..191f3ecb2ffcb 100644 --- a/locale/en/blog/release/v0.10.13.md +++ b/locale/en/blog/release/v0.10.13.md @@ -31,7 +31,6 @@ layout: blog-post.hbs * src: fix memory leak in UsingDomains() (Ben Noordhuis) - Source Code: https://nodejs.org/dist/v0.10.13/node-v0.10.13.tar.gz Macintosh Installer (Universal): https://nodejs.org/dist/v0.10.13/node-v0.10.13.pkg diff --git a/locale/en/blog/release/v0.10.14.md b/locale/en/blog/release/v0.10.14.md index a87ffcb61f146..42d958fdae593 100644 --- a/locale/en/blog/release/v0.10.14.md +++ b/locale/en/blog/release/v0.10.14.md @@ -25,7 +25,6 @@ layout: blog-post.hbs * crypto: fix memory leak in LoadPKCS12 (Fedor Indutny) - Source Code: https://nodejs.org/dist/v0.10.14/node-v0.10.14.tar.gz Macintosh Installer (Universal): https://nodejs.org/dist/v0.10.14/node-v0.10.14.pkg diff --git a/locale/en/blog/release/v0.10.15.md b/locale/en/blog/release/v0.10.15.md index 2c1b175d49e65..4775a2f856851 100644 --- a/locale/en/blog/release/v0.10.15.md +++ b/locale/en/blog/release/v0.10.15.md @@ -11,7 +11,6 @@ layout: blog-post.hbs * src: fix process.getuid() return value (Ben Noordhuis) - Source Code: https://nodejs.org/dist/v0.10.15/node-v0.10.15.tar.gz Macintosh Installer (Universal): https://nodejs.org/dist/v0.10.15/node-v0.10.15.pkg diff --git a/locale/en/blog/release/v0.10.16.md b/locale/en/blog/release/v0.10.16.md index cf3633ee45bcf..119c56bb69e75 100644 --- a/locale/en/blog/release/v0.10.16.md +++ b/locale/en/blog/release/v0.10.16.md @@ -25,7 +25,6 @@ layout: blog-post.hbs * stream: Fix double pipe error emit (Eran Hammer) - Source Code: https://nodejs.org/dist/v0.10.16/node-v0.10.16.tar.gz Macintosh Installer (Universal): https://nodejs.org/dist/v0.10.16/node-v0.10.16.pkg diff --git a/locale/en/blog/release/v0.10.17.md b/locale/en/blog/release/v0.10.17.md index b77c3045c35eb..10d81a8efa9ec 100644 --- a/locale/en/blog/release/v0.10.17.md +++ b/locale/en/blog/release/v0.10.17.md @@ -21,7 +21,6 @@ layout: blog-post.hbs * readline: pause stdin before turning off terminal raw mode (Daniel Chatfield) - Source Code: https://nodejs.org/dist/v0.10.17/node-v0.10.17.tar.gz Macintosh Installer (Universal): https://nodejs.org/dist/v0.10.17/node-v0.10.17.pkg diff --git a/locale/en/blog/release/v0.10.18.md b/locale/en/blog/release/v0.10.18.md index bf79e6703ba26..bee7d5e88f542 100644 --- a/locale/en/blog/release/v0.10.18.md +++ b/locale/en/blog/release/v0.10.18.md @@ -15,7 +15,6 @@ layout: blog-post.hbs * stream: Pass 'buffer' encoding with decoded writable chunks (isaacs) - Source Code: https://nodejs.org/dist/v0.10.18/node-v0.10.18.tar.gz Macintosh Installer (Universal): https://nodejs.org/dist/v0.10.18/node-v0.10.18.pkg diff --git a/locale/en/blog/release/v0.10.19.md b/locale/en/blog/release/v0.10.19.md index 47bebb8f49c3b..8c88c801a3d38 100644 --- a/locale/en/blog/release/v0.10.19.md +++ b/locale/en/blog/release/v0.10.19.md @@ -23,7 +23,6 @@ layout: blog-post.hbs * tls: NPN protocols are now local to connections (Fedor Indutny) - Source Code: https://nodejs.org/dist/v0.10.19/node-v0.10.19.tar.gz Macintosh Installer (Universal): https://nodejs.org/dist/v0.10.19/node-v0.10.19.pkg diff --git a/locale/en/blog/release/v0.10.2.md b/locale/en/blog/release/v0.10.2.md index 7ab5f9a3c56d7..6923078564842 100644 --- a/locale/en/blog/release/v0.10.2.md +++ b/locale/en/blog/release/v0.10.2.md @@ -41,7 +41,6 @@ layout: blog-post.hbs * child_process: fix sending utf-8 to child process (Ben Noordhuis) - Source Code: https://nodejs.org/dist/v0.10.2/node-v0.10.2.tar.gz Macintosh Installer (Universal): https://nodejs.org/dist/v0.10.2/node-v0.10.2.pkg diff --git a/locale/en/blog/release/v0.10.20.md b/locale/en/blog/release/v0.10.20.md index 77c9f5e9e2dc6..0087e4df27810 100644 --- a/locale/en/blog/release/v0.10.20.md +++ b/locale/en/blog/release/v0.10.20.md @@ -12,7 +12,6 @@ layout: blog-post.hbs * tls: fix sporadic hang and partial reads (Fedor Indutny) - fixes "npm ERR! cb() never called!" - Source Code: https://nodejs.org/dist/v0.10.20/node-v0.10.20.tar.gz Macintosh Installer (Universal): https://nodejs.org/dist/v0.10.20/node-v0.10.20.pkg diff --git a/locale/en/blog/release/v0.10.21.md b/locale/en/blog/release/v0.10.21.md index dd5c705516119..fa5e21eb9cb15 100644 --- a/locale/en/blog/release/v0.10.21.md +++ b/locale/en/blog/release/v0.10.21.md @@ -24,7 +24,6 @@ upgrade as soon as possible. Details will be released soon. * tls: fix premature connection termination (Ben Noordhuis) - Source Code: https://nodejs.org/dist/v0.10.21/node-v0.10.21.tar.gz Macintosh Installer (Universal): https://nodejs.org/dist/v0.10.21/node-v0.10.21.pkg diff --git a/locale/en/blog/release/v0.10.22.md b/locale/en/blog/release/v0.10.22.md index 2c9c85a1384a7..acb1be570a49d 100644 --- a/locale/en/blog/release/v0.10.22.md +++ b/locale/en/blog/release/v0.10.22.md @@ -27,7 +27,6 @@ layout: blog-post.hbs * v8: use correct timezone information on Solaris (Maciej Małecki) - Source Code: https://nodejs.org/dist/v0.10.22/node-v0.10.22.tar.gz Macintosh Installer (Universal): https://nodejs.org/dist/v0.10.22/node-v0.10.22.pkg diff --git a/locale/en/blog/release/v0.10.23.md b/locale/en/blog/release/v0.10.23.md index c2a23a4a8ad25..47c85d6b6a5ff 100644 --- a/locale/en/blog/release/v0.10.23.md +++ b/locale/en/blog/release/v0.10.23.md @@ -39,7 +39,6 @@ layout: blog-post.hbs * tls: reset NPN callbacks after SNI (Fedor Indutny) - Source Code: https://nodejs.org/dist/v0.10.23/node-v0.10.23.tar.gz Macintosh Installer (Universal): https://nodejs.org/dist/v0.10.23/node-v0.10.23.pkg diff --git a/locale/en/blog/release/v0.10.24.md b/locale/en/blog/release/v0.10.24.md index eb102adaff225..4bd9a184aae97 100644 --- a/locale/en/blog/release/v0.10.24.md +++ b/locale/en/blog/release/v0.10.24.md @@ -21,7 +21,6 @@ layout: blog-post.hbs * module: only cache package main (Wyatt Preul) - Source Code: https://nodejs.org/dist/v0.10.24/node-v0.10.24.tar.gz Macintosh Installer (Universal): https://nodejs.org/dist/v0.10.24/node-v0.10.24.pkg diff --git a/locale/en/blog/release/v0.10.25.md b/locale/en/blog/release/v0.10.25.md index 084dd433dd78e..4e839a369a397 100644 --- a/locale/en/blog/release/v0.10.25.md +++ b/locale/en/blog/release/v0.10.25.md @@ -25,7 +25,6 @@ layout: blog-post.hbs * stream: writes may return false but forget to emit drain (Yang Tianyang) - Source Code: https://nodejs.org/dist/v0.10.25/node-v0.10.25.tar.gz Macintosh Installer (Universal): https://nodejs.org/dist/v0.10.25/node-v0.10.25.pkg diff --git a/locale/en/blog/release/v0.10.26.md b/locale/en/blog/release/v0.10.26.md index 577a6fa03235b..8ac661b9d36d0 100644 --- a/locale/en/blog/release/v0.10.26.md +++ b/locale/en/blog/release/v0.10.26.md @@ -35,7 +35,6 @@ layout: blog-post.hbs * zlib: avoid assertion in close (Fedor Indutny) - Source Code: https://nodejs.org/dist/v0.10.26/node-v0.10.26.tar.gz Macintosh Installer (Universal): https://nodejs.org/dist/v0.10.26/node-v0.10.26.pkg diff --git a/locale/en/blog/release/v0.10.27.md b/locale/en/blog/release/v0.10.27.md index b4ea1ce87d409..717b5de0365ba 100644 --- a/locale/en/blog/release/v0.10.27.md +++ b/locale/en/blog/release/v0.10.27.md @@ -39,7 +39,6 @@ layout: blog-post.hbs * util: format as Error if instanceof Error (Rod Vagg) - Source Code: https://nodejs.org/dist/v0.10.27/node-v0.10.27.tar.gz Macintosh Installer (Universal): https://nodejs.org/dist/v0.10.27/node-v0.10.27.pkg diff --git a/locale/en/blog/release/v0.10.28.md b/locale/en/blog/release/v0.10.28.md index 153393f769b1b..4078e0ae78c75 100644 --- a/locale/en/blog/release/v0.10.28.md +++ b/locale/en/blog/release/v0.10.28.md @@ -11,7 +11,6 @@ layout: blog-post.hbs * npm: upgrade to v1.4.9 - Source Code: https://nodejs.org/dist/v0.10.28/node-v0.10.28.tar.gz Macintosh Installer (Universal): https://nodejs.org/dist/v0.10.28/node-v0.10.28.pkg diff --git a/locale/en/blog/release/v0.10.29.md b/locale/en/blog/release/v0.10.29.md index 54649eec8cf7d..b652469f80c41 100644 --- a/locale/en/blog/release/v0.10.29.md +++ b/locale/en/blog/release/v0.10.29.md @@ -34,7 +34,6 @@ environment variable set. * tls: fix performance issue (Alexis Campailla) - Source Code: https://nodejs.org/dist/v0.10.29/node-v0.10.29.tar.gz Macintosh Installer (Universal): https://nodejs.org/dist/v0.10.29/node-v0.10.29.pkg diff --git a/locale/en/blog/release/v0.10.3.md b/locale/en/blog/release/v0.10.3.md index 61d45c4dc99fb..db86d60e59224 100644 --- a/locale/en/blog/release/v0.10.3.md +++ b/locale/en/blog/release/v0.10.3.md @@ -31,7 +31,6 @@ layout: blog-post.hbs * src: tie process.versions.uv to uv_version_string() (Ben Noordhuis) - Source Code: https://nodejs.org/dist/v0.10.3/node-v0.10.3.tar.gz Macintosh Installer (Universal): https://nodejs.org/dist/v0.10.3/node-v0.10.3.pkg diff --git a/locale/en/blog/release/v0.10.30.md b/locale/en/blog/release/v0.10.30.md index fced0a43f2392..e21befdf87d00 100644 --- a/locale/en/blog/release/v0.10.30.md +++ b/locale/en/blog/release/v0.10.30.md @@ -41,7 +41,6 @@ layout: blog-post.hbs * zlib: do not crash on write after close (Fedor Indutny) - Source Code: https://nodejs.org/dist/v0.10.30/node-v0.10.30.tar.gz Macintosh Installer (Universal): https://nodejs.org/dist/v0.10.30/node-v0.10.30.pkg diff --git a/locale/en/blog/release/v0.10.31.md b/locale/en/blog/release/v0.10.31.md index 020e5ac14e82b..ba7eaa114d74a 100644 --- a/locale/en/blog/release/v0.10.31.md +++ b/locale/en/blog/release/v0.10.31.md @@ -23,7 +23,6 @@ layout: blog-post.hbs * timers: fix timers with non-integer delay hanging. (Julien Gilli) - Source Code: https://nodejs.org/dist/v0.10.31/node-v0.10.31.tar.gz Macintosh Installer (Universal): https://nodejs.org/dist/v0.10.31/node-v0.10.31.pkg diff --git a/locale/en/blog/release/v0.10.32.md b/locale/en/blog/release/v0.10.32.md index 72aa587e89bad..713e8f0ad5d2d 100644 --- a/locale/en/blog/release/v0.10.32.md +++ b/locale/en/blog/release/v0.10.32.md @@ -23,7 +23,6 @@ layout: blog-post.hbs * url: Add support for RFC 3490 separators (Mathias Bynens) - Source Code: https://nodejs.org/dist/v0.10.32/node-v0.10.32.tar.gz Macintosh Installer (Universal): https://nodejs.org/dist/v0.10.32/node-v0.10.32.pkg diff --git a/locale/en/blog/release/v0.10.33.md b/locale/en/blog/release/v0.10.33.md index 5b3760d1da95e..1bf8be41dd6f5 100644 --- a/locale/en/blog/release/v0.10.33.md +++ b/locale/en/blog/release/v0.10.33.md @@ -81,7 +81,6 @@ This does not change the behavior for users specifically requesting assumed you know what you're doing since you're specifically asking to use these methods. - Source Code: https://nodejs.org/dist/v0.10.33/node-v0.10.33.tar.gz Macintosh Installer (Universal): https://nodejs.org/dist/v0.10.33/node-v0.10.33.pkg diff --git a/locale/en/blog/release/v0.10.34.md b/locale/en/blog/release/v0.10.34.md index 05815675997c9..4dd308b1d3dfc 100644 --- a/locale/en/blog/release/v0.10.34.md +++ b/locale/en/blog/release/v0.10.34.md @@ -29,7 +29,6 @@ layout: blog-post.hbs * debugger: fix when using "use strict" (Julien Gilli) - Source Code: https://nodejs.org/dist/v0.10.34/node-v0.10.34.tar.gz Macintosh Installer (Universal): https://nodejs.org/dist/v0.10.34/node-v0.10.34.pkg diff --git a/locale/en/blog/release/v0.10.35.md b/locale/en/blog/release/v0.10.35.md index 27d7566362de3..a97f3a655d191 100644 --- a/locale/en/blog/release/v0.10.35.md +++ b/locale/en/blog/release/v0.10.35.md @@ -15,7 +15,6 @@ layout: blog-post.hbs * timers: don't mutate unref list while iterating it (Julien Gilli) - Source Code: https://nodejs.org/dist/v0.10.35/node-v0.10.35.tar.gz Macintosh Installer (Universal): https://nodejs.org/dist/v0.10.35/node-v0.10.35.pkg diff --git a/locale/en/blog/release/v0.10.36.md b/locale/en/blog/release/v0.10.36.md index 0d8bf1d69be5a..eb84870d071f0 100644 --- a/locale/en/blog/release/v0.10.36.md +++ b/locale/en/blog/release/v0.10.36.md @@ -15,7 +15,6 @@ layout: blog-post.hbs * v8: don't busy loop in cpu profiler thread (Ben Noordhuis) - Source Code: https://nodejs.org/dist/v0.10.36/node-v0.10.36.tar.gz Macintosh Installer (Universal): https://nodejs.org/dist/v0.10.36/node-v0.10.36.pkg diff --git a/locale/en/blog/release/v0.10.37.md b/locale/en/blog/release/v0.10.37.md index 82807e01c1c5e..797429b015bb4 100644 --- a/locale/en/blog/release/v0.10.37.md +++ b/locale/en/blog/release/v0.10.37.md @@ -27,7 +27,6 @@ coding guide](https://www.securecoding.cert.org/confluence/display/c/POS36-C.+Ob * http: fix performance regression for GET requests (Florin-Cristian Gavrila) - Source Code: https://nodejs.org/dist/v0.10.37/node-v0.10.37.tar.gz Macintosh Installer (Universal): https://nodejs.org/dist/v0.10.37/node-v0.10.37.pkg diff --git a/locale/en/blog/release/v0.10.38.md b/locale/en/blog/release/v0.10.38.md index 448dcc0238ccb..e6e1ce2363862 100644 --- a/locale/en/blog/release/v0.10.38.md +++ b/locale/en/blog/release/v0.10.38.md @@ -15,7 +15,6 @@ recently](https://www.openssl.org/news/secadv_20150319.txt). * openssl: upgrade to 1.0.1m (Addressing multiple CVEs) - Source Code: https://nodejs.org/dist/v0.10.38/node-v0.10.38.tar.gz Macintosh Installer (Universal): https://nodejs.org/dist/v0.10.38/node-v0.10.38.pkg diff --git a/locale/en/blog/release/v0.10.39.md b/locale/en/blog/release/v0.10.39.md index a0e64309cae9c..9bee51cf67194 100644 --- a/locale/en/blog/release/v0.10.39.md +++ b/locale/en/blog/release/v0.10.39.md @@ -38,7 +38,6 @@ written with Node.js are vulnerable to Denial Of Service attacks. * windows: broadcast WM_SETTINGCHANGE after install (Mathias Küsel) - Source Code: https://nodejs.org/dist/v0.10.39/node-v0.10.39.tar.gz Macintosh Installer (Universal): https://nodejs.org/dist/v0.10.39/node-v0.10.39.pkg diff --git a/locale/en/blog/release/v0.10.4.md b/locale/en/blog/release/v0.10.4.md index 23eb9b25426db..53182a06b4ae6 100644 --- a/locale/en/blog/release/v0.10.4.md +++ b/locale/en/blog/release/v0.10.4.md @@ -39,7 +39,6 @@ layout: blog-post.hbs * tls: Re-enable check of CN-ID in cert verification (Tobias Müllerleile) - Source Code: https://nodejs.org/dist/v0.10.4/node-v0.10.4.tar.gz Macintosh Installer (Universal): https://nodejs.org/dist/v0.10.4/node-v0.10.4.pkg diff --git a/locale/en/blog/release/v0.10.40.md b/locale/en/blog/release/v0.10.40.md index 25b6601cf3877..054d1022d235e 100644 --- a/locale/en/blog/release/v0.10.40.md +++ b/locale/en/blog/release/v0.10.40.md @@ -19,7 +19,6 @@ found [on OpenSSL's website](http://openssl.org/news/secadv_20150709.txt). * win,msi: create npm folder in AppData directory (Steven Rockarts) - Source Code: https://nodejs.org/dist/v0.10.40/node-v0.10.40.tar.gz Macintosh Installer (Universal): https://nodejs.org/dist/v0.10.40/node-v0.10.40.pkg diff --git a/locale/en/blog/release/v0.10.42.md b/locale/en/blog/release/v0.10.42.md index 1c942b886ba72..c3858dff38220 100644 --- a/locale/en/blog/release/v0.10.42.md +++ b/locale/en/blog/release/v0.10.42.md @@ -33,8 +33,6 @@ This is an important security release. For full details see https://nodejs.org/e * [df80e856c6] - src: add --security-revert command line flag (James M Snell) * [ff58dcdd74] - tools: backport tools/install.py for headers (Richard Lau) https://github.com/nodejs/node/pull/4149 - - Windows 32-bit Installer: https://nodejs.org/dist/v0.10.42/node-v0.10.42-x86.msi
Windows 64-bit Installer: https://nodejs.org/dist/v0.10.42/x64/node-v0.10.42-x64.msi
Windows 32-bit Binary: https://nodejs.org/dist/v0.10.42/node.exe
diff --git a/locale/en/blog/release/v0.10.46.md b/locale/en/blog/release/v0.10.46.md index 9fc974ceef799..e75e4fad750dd 100644 --- a/locale/en/blog/release/v0.10.46.md +++ b/locale/en/blog/release/v0.10.46.md @@ -20,7 +20,6 @@ This is a security release. All Node.js users should consult the security releas * [3374f57973] - deps: update libuv to 0.10.37 (Saúl Ibarra Corretgé) https://github.com/nodejs/node/pull/7293 * [fcb9145e29] - deps: backport 3a9bfec from v8 upstream (Myles Borins) https://github.com/nodejs/node-private/pull/43 - Windows 32-bit Installer: https://nodejs.org/dist/v0.10.46/node-v0.10.46-x86.msi
Windows 64-bit Installer: https://nodejs.org/dist/v0.10.46/x64/node-v0.10.46-x64.msi
Windows 32-bit Binary: https://nodejs.org/dist/v0.10.46/node.exe
diff --git a/locale/en/blog/release/v0.10.5.md b/locale/en/blog/release/v0.10.5.md index af713f38d8c24..8fbcb28e3909c 100644 --- a/locale/en/blog/release/v0.10.5.md +++ b/locale/en/blog/release/v0.10.5.md @@ -27,7 +27,6 @@ layout: blog-post.hbs * stream: Fix unshift() race conditions (isaacs) - Source Code: https://nodejs.org/dist/v0.10.5/node-v0.10.5.tar.gz Macintosh Installer (Universal): https://nodejs.org/dist/v0.10.5/node-v0.10.5.pkg diff --git a/locale/en/blog/release/v0.10.6.md b/locale/en/blog/release/v0.10.6.md index 61c6f918fd1ff..fc49f3e19b3fc 100644 --- a/locale/en/blog/release/v0.10.6.md +++ b/locale/en/blog/release/v0.10.6.md @@ -19,7 +19,6 @@ layout: blog-post.hbs * src: DRY string encoding/decoding (isaacs) - Source Code: https://nodejs.org/dist/v0.10.6/node-v0.10.6.tar.gz Macintosh Installer (Universal): https://nodejs.org/dist/v0.10.6/node-v0.10.6.pkg diff --git a/locale/en/blog/release/v0.10.7.md b/locale/en/blog/release/v0.10.7.md index 04a7edeea12bb..b899aa7a2c361 100644 --- a/locale/en/blog/release/v0.10.7.md +++ b/locale/en/blog/release/v0.10.7.md @@ -19,7 +19,6 @@ layout: blog-post.hbs * timers: fix setInterval() assert (Ben Noordhuis) - Source Code: https://nodejs.org/dist/v0.10.7/node-v0.10.7.tar.gz Macintosh Installer (Universal): https://nodejs.org/dist/v0.10.7/node-v0.10.7.pkg diff --git a/locale/en/blog/release/v0.10.8.md b/locale/en/blog/release/v0.10.8.md index f983b504737d0..6903ac9ba870f 100644 --- a/locale/en/blog/release/v0.10.8.md +++ b/locale/en/blog/release/v0.10.8.md @@ -29,7 +29,6 @@ layout: blog-post.hbs * string_bytes: strip padding from base64 strings (Trevor Norris) - Source Code: https://nodejs.org/dist/v0.10.8/node-v0.10.8.tar.gz Macintosh Installer (Universal): https://nodejs.org/dist/v0.10.8/node-v0.10.8.pkg diff --git a/locale/en/blog/release/v0.10.9.md b/locale/en/blog/release/v0.10.9.md index f6071acd6ee34..efd87816f40c7 100644 --- a/locale/en/blog/release/v0.10.9.md +++ b/locale/en/blog/release/v0.10.9.md @@ -21,7 +21,6 @@ layout: blog-post.hbs * tls: ignore .shutdown() syscall error (Fedor Indutny) - Source Code: https://nodejs.org/dist/v0.10.9/node-v0.10.9.tar.gz Macintosh Installer (Universal): https://nodejs.org/dist/v0.10.9/node-v0.10.9.pkg diff --git a/locale/en/blog/release/v0.11.0.md b/locale/en/blog/release/v0.11.0.md index b06752871fb28..39a8005dcf221 100644 --- a/locale/en/blog/release/v0.11.0.md +++ b/locale/en/blog/release/v0.11.0.md @@ -41,7 +41,6 @@ layout: blog-post.hbs * console: `console.dir()` bypasses inspect() methods (Nathan Rajlich) - Source Code: https://nodejs.org/dist/v0.11.0/node-v0.11.0.tar.gz Macintosh Installer (Universal): https://nodejs.org/dist/v0.11.0/node-v0.11.0.pkg diff --git a/locale/en/blog/release/v0.11.1.md b/locale/en/blog/release/v0.11.1.md index 083bc60071513..e666cefa07db8 100644 --- a/locale/en/blog/release/v0.11.1.md +++ b/locale/en/blog/release/v0.11.1.md @@ -38,7 +38,6 @@ than delay. * zlib: allow passing options to convenience methods (Kyle Robinson Young) - Source Code: https://nodejs.org/dist/v0.11.1/node-v0.11.1.tar.gz Macintosh Installer (Universal): https://nodejs.org/dist/v0.11.1/node-v0.11.1.pkg diff --git a/locale/en/blog/release/v0.11.10.md b/locale/en/blog/release/v0.11.10.md index 8134140415cce..ed83b9e0dfd98 100644 --- a/locale/en/blog/release/v0.11.10.md +++ b/locale/en/blog/release/v0.11.10.md @@ -59,7 +59,6 @@ layout: blog-post.hbs * windows: fix dns lookup of localhost with ipv6 (Alexis Campailla) - Source Code: https://nodejs.org/dist/v0.11.10/node-v0.11.10.tar.gz Macintosh Installer (Universal): https://nodejs.org/dist/v0.11.10/node-v0.11.10.pkg diff --git a/locale/en/blog/release/v0.11.11.md b/locale/en/blog/release/v0.11.11.md index dd26c1990083c..faf34aafb4732 100644 --- a/locale/en/blog/release/v0.11.11.md +++ b/locale/en/blog/release/v0.11.11.md @@ -59,7 +59,6 @@ layout: blog-post.hbs * util: handle escaped forward slashes correctly (Tom Gallacher) - Source Code: https://nodejs.org/dist/v0.11.11/node-v0.11.11.tar.gz Macintosh Installer (Universal): https://nodejs.org/dist/v0.11.11/node-v0.11.11.pkg diff --git a/locale/en/blog/release/v0.11.12.md b/locale/en/blog/release/v0.11.12.md index 1cfc5396d9f1f..b21daea1048e0 100644 --- a/locale/en/blog/release/v0.11.12.md +++ b/locale/en/blog/release/v0.11.12.md @@ -69,7 +69,6 @@ layout: blog-post.hbs * zlib: add sync versions for convenience methods (Nikolai Vavilov) - Source Code: https://nodejs.org/dist/v0.11.12/node-v0.11.12.tar.gz Macintosh Installer (Universal): https://nodejs.org/dist/v0.11.12/node-v0.11.12.pkg diff --git a/locale/en/blog/release/v0.11.14.md b/locale/en/blog/release/v0.11.14.md index 0a6ac0029d6be..e2e15dc8a31a6 100644 --- a/locale/en/blog/release/v0.11.14.md +++ b/locale/en/blog/release/v0.11.14.md @@ -175,7 +175,6 @@ layout: blog-post.hbs * url: treat the same as / (isaacs) - Source Code: https://nodejs.org/dist/v0.11.14/node-v0.11.14.tar.gz Macintosh Installer (Universal): https://nodejs.org/dist/v0.11.14/node-v0.11.14.pkg diff --git a/locale/en/blog/release/v0.11.15.md b/locale/en/blog/release/v0.11.15.md index 6d6644647bcf5..e491b8967ab49 100644 --- a/locale/en/blog/release/v0.11.15.md +++ b/locale/en/blog/release/v0.11.15.md @@ -145,7 +145,6 @@ layout: blog-post.hbs * util: add es6 Symbol support for `util.inspect` (gyson) - Source Code: https://nodejs.org/dist/v0.11.15/node-v0.11.15.tar.gz Macintosh Installer (Universal): https://nodejs.org/dist/v0.11.15/node-v0.11.15.pkg diff --git a/locale/en/blog/release/v0.11.16.md b/locale/en/blog/release/v0.11.16.md index a8b4c2fe17357..211727a9f7f35 100644 --- a/locale/en/blog/release/v0.11.16.md +++ b/locale/en/blog/release/v0.11.16.md @@ -21,7 +21,6 @@ layout: blog-post.hbs * url: fix parsing of ssh urls (Evan Lucas) - Source Code: https://nodejs.org/dist/v0.11.16/node-v0.11.16.tar.gz Macintosh Installer (Universal): https://nodejs.org/dist/v0.11.16/node-v0.11.16.pkg diff --git a/locale/en/blog/release/v0.11.2.md b/locale/en/blog/release/v0.11.2.md index 4f0ed5da0daf0..00dd698eb7d52 100644 --- a/locale/en/blog/release/v0.11.2.md +++ b/locale/en/blog/release/v0.11.2.md @@ -41,7 +41,6 @@ layout: blog-post.hbs * vm: add support for timeout argument (Andrew Paprocki) - Source Code: https://nodejs.org/dist/v0.11.2/node-v0.11.2.tar.gz Macintosh Installer (Universal): https://nodejs.org/dist/v0.11.2/node-v0.11.2.pkg diff --git a/locale/en/blog/release/v0.11.3.md b/locale/en/blog/release/v0.11.3.md index 620b60ed893d5..07c251838839f 100644 --- a/locale/en/blog/release/v0.11.3.md +++ b/locale/en/blog/release/v0.11.3.md @@ -55,7 +55,6 @@ layout: blog-post.hbs * dns: add getServers and setServers (Timothy J Fontaine) - Source Code: https://nodejs.org/dist/v0.11.3/node-v0.11.3.tar.gz Macintosh Installer (Universal): https://nodejs.org/dist/v0.11.3/node-v0.11.3.pkg diff --git a/locale/en/blog/release/v0.11.4.md b/locale/en/blog/release/v0.11.4.md index 52a9e4cf16e8d..493408c58c866 100644 --- a/locale/en/blog/release/v0.11.4.md +++ b/locale/en/blog/release/v0.11.4.md @@ -41,7 +41,6 @@ layout: blog-post.hbs * zlib: allow custom flush type for flush() (Brian White) - Source Code: https://nodejs.org/dist/v0.11.4/node-v0.11.4.tar.gz Macintosh Installer (Universal): https://nodejs.org/dist/v0.11.4/node-v0.11.4.pkg diff --git a/locale/en/blog/release/v0.11.5.md b/locale/en/blog/release/v0.11.5.md index f6332bdfc794e..5fc54d20030ae 100644 --- a/locale/en/blog/release/v0.11.5.md +++ b/locale/en/blog/release/v0.11.5.md @@ -41,7 +41,6 @@ layout: blog-post.hbs * util: don't throw on circular %j input to format() (Ben Noordhuis) - Source Code: https://nodejs.org/dist/v0.11.5/node-v0.11.5.tar.gz Macintosh Installer (Universal): https://nodejs.org/dist/v0.11.5/node-v0.11.5.pkg diff --git a/locale/en/blog/release/v0.11.6.md b/locale/en/blog/release/v0.11.6.md index 014e4141252e4..d746b7d02d80a 100644 --- a/locale/en/blog/release/v0.11.6.md +++ b/locale/en/blog/release/v0.11.6.md @@ -63,7 +63,6 @@ layout: blog-post.hbs * util: isObject should always return boolean (Trevor Norris) - Source Code: https://nodejs.org/dist/v0.11.6/node-v0.11.6.tar.gz Macintosh Installer (Universal): https://nodejs.org/dist/v0.11.6/node-v0.11.6.pkg diff --git a/locale/en/blog/release/v0.11.7.md b/locale/en/blog/release/v0.11.7.md index d28f2920215ce..c1d514220b314 100644 --- a/locale/en/blog/release/v0.11.7.md +++ b/locale/en/blog/release/v0.11.7.md @@ -45,7 +45,6 @@ layout: blog-post.hbs * vm: rewritten to behave like Contextify (Domenic Denicola) - Source Code: https://nodejs.org/dist/v0.11.7/node-v0.11.7.tar.gz Macintosh Installer (Universal): https://nodejs.org/dist/v0.11.7/node-v0.11.7.pkg diff --git a/locale/en/blog/release/v0.11.8.md b/locale/en/blog/release/v0.11.8.md index ddcd0ad210801..777bf53c6d92f 100644 --- a/locale/en/blog/release/v0.11.8.md +++ b/locale/en/blog/release/v0.11.8.md @@ -49,7 +49,6 @@ layout: blog-post.hbs * util: format as Error if instanceof Error (Rod Vagg) - Source Code: https://nodejs.org/dist/v0.11.8/node-v0.11.8.tar.gz Macintosh Installer (Universal): https://nodejs.org/dist/v0.11.8/node-v0.11.8.pkg diff --git a/locale/en/blog/release/v0.11.9.md b/locale/en/blog/release/v0.11.9.md index 99b880c1dae3a..2d5257dcf847c 100644 --- a/locale/en/blog/release/v0.11.9.md +++ b/locale/en/blog/release/v0.11.9.md @@ -45,7 +45,6 @@ layout: blog-post.hbs * tls: more accurate wrapping of connecting socket (Fedor Indutny) - Source Code: https://nodejs.org/dist/v0.11.9/node-v0.11.9.tar.gz Macintosh Installer (Universal): https://nodejs.org/dist/v0.11.9/node-v0.11.9.pkg diff --git a/locale/en/blog/release/v0.12.1.md b/locale/en/blog/release/v0.12.1.md index 55e0514fbd209..4ce504e5725f9 100644 --- a/locale/en/blog/release/v0.12.1.md +++ b/locale/en/blog/release/v0.12.1.md @@ -15,7 +15,6 @@ recently](https://www.openssl.org/news/secadv_20150319.txt). * openssl: upgrade to 1.0.1m (Addressing multiple CVES) - Source Code: https://nodejs.org/dist/v0.12.1/node-v0.12.1.tar.gz Macintosh Installer (Universal): https://nodejs.org/dist/v0.12.1/node-v0.12.1.pkg diff --git a/locale/en/blog/release/v0.12.10.md b/locale/en/blog/release/v0.12.10.md index 9cdfc66b0cd76..fa0487f516bb8 100644 --- a/locale/en/blog/release/v0.12.10.md +++ b/locale/en/blog/release/v0.12.10.md @@ -33,8 +33,6 @@ Commits: * [23bced1fb3] - src: add --security-revert command line flag (James M Snell) * [f41a3c73e7] - tools: backport tools/install.py for headers (Richard Lau) https://github.com/nodejs/node/pull/4149 - - Windows 32-bit Installer: https://nodejs.org/dist/v0.12.10/node-v0.12.10-x86.msi
Windows 64-bit Installer: https://nodejs.org/dist/v0.12.10/x64/node-v0.12.10-x64.msi
Windows 32-bit Binary: https://nodejs.org/dist/v0.12.10/node.exe
diff --git a/locale/en/blog/release/v0.12.11.md b/locale/en/blog/release/v0.12.11.md index 6893366939d8a..3df522063245a 100644 --- a/locale/en/blog/release/v0.12.11.md +++ b/locale/en/blog/release/v0.12.11.md @@ -21,7 +21,6 @@ This release contains security updates. OpenSSL 1.0.1s fixes some low-severity d - Fix a defect that can cause memory corruption in certain very rare cases relating to the internal `BN_hex2bn()` and `BN_dec2bn()` functions. It is believed that Node.js is not invoking the code paths that use these functions so practical attacks via Node.js using this defect are _unlikely_ to be possible. More info is available at https://www.openssl.org/news/vulnerabilities.html#2016-0797 - Fix a defect that makes the CacheBleed Attack (https://ssrg.nicta.com.au/projects/TS/cachebleed/) possible. This defect enables attackers to execute side-channel attacks leading to the potential recovery of entire RSA private keys. It only affects the Intel Sandy Bridge (and possibly older) microarchitecture when using hyper-threading. Newer microarchitectures, including Haswell, are unaffected. More info is available at https://www.openssl.org/news/vulnerabilities.html#2016-0702 - Commits: * [[`1ab6653db9`](https://github.com/nodejs/node/commit/1ab6653db9)] - **build**: update Node.js logo on OSX installer (Rod Vagg) [#5401](https://github.com/nodejs/node/pull/5401) diff --git a/locale/en/blog/release/v0.12.13.md b/locale/en/blog/release/v0.12.13.md index 2f5f9303585ba..ecdd63a726f74 100644 --- a/locale/en/blog/release/v0.12.13.md +++ b/locale/en/blog/release/v0.12.13.md @@ -28,8 +28,6 @@ Commits: * [154098a3dc] - test: bp fix for test-http-get-pipeline-problem.js (Michael Dawson) https://github.com/nodejs/node/pull/3013 * [ff2bed6e86] - win,build: support Visual C++ Build Tools 2015 (João Reis) https://github.com/nodejs/node/pull/5627 - - Windows 32-bit Installer: https://nodejs.org/dist/v0.12.13/node-v0.12.13-x86.msi
Windows 64-bit Installer: https://nodejs.org/dist/v0.12.13/x64/node-v0.12.13-x64.msi
Windows 32-bit Binary: https://nodejs.org/dist/v0.12.13/node.exe
diff --git a/locale/en/blog/release/v0.12.15.md b/locale/en/blog/release/v0.12.15.md index 3d5796667963b..bc67634d48cd8 100644 --- a/locale/en/blog/release/v0.12.15.md +++ b/locale/en/blog/release/v0.12.15.md @@ -25,8 +25,6 @@ This is a security release. All Node.js users should consult the security releas * [a113e02f16] - deps: backport 3a9bfec from v8 upstream (Ben Noordhuis) * [8138055c88] - test: fix test failure due to expired certificates (Ben Noordhuis) https://github.com/nodejs/node/pull/7195 - - Windows 32-bit Installer: https://nodejs.org/dist/v0.12.15/node-v0.12.15-x86.msi
Windows 64-bit Installer: https://nodejs.org/dist/v0.12.15/x64/node-v0.12.15-x64.msi
Windows 32-bit Binary: https://nodejs.org/dist/v0.12.15/node.exe
diff --git a/locale/en/blog/release/v0.12.2.md b/locale/en/blog/release/v0.12.2.md index c91fc68c8de68..3482c799a89c3 100644 --- a/locale/en/blog/release/v0.12.2.md +++ b/locale/en/blog/release/v0.12.2.md @@ -49,7 +49,6 @@ layout: blog-post.hbs * watchdog: fix timeout for early polling return (Saúl Ibarra Corretgé) - Source Code: https://nodejs.org/dist/v0.12.2/node-v0.12.2.tar.gz Macintosh Installer (Universal): https://nodejs.org/dist/v0.12.2/node-v0.12.2.pkg diff --git a/locale/en/blog/release/v0.12.3.md b/locale/en/blog/release/v0.12.3.md index 277b2092d4aa4..5e2414b4a8f2a 100644 --- a/locale/en/blog/release/v0.12.3.md +++ b/locale/en/blog/release/v0.12.3.md @@ -29,7 +29,6 @@ layout: blog-post.hbs * src: fix backport of SIGINT crash fix on FreeBSD (Julien Gilli) - Source Code: https://nodejs.org/dist/v0.12.3/node-v0.12.3.tar.gz Macintosh Installer (Universal): https://nodejs.org/dist/v0.12.3/node-v0.12.3.pkg diff --git a/locale/en/blog/release/v0.12.4.md b/locale/en/blog/release/v0.12.4.md index db06f7b058f5f..512d04e8da5e2 100644 --- a/locale/en/blog/release/v0.12.4.md +++ b/locale/en/blog/release/v0.12.4.md @@ -15,7 +15,6 @@ layout: blog-post.hbs * win: bring back xp/2k3 support (Bert Belder) - Source Code: https://nodejs.org/dist/v0.12.4/node-v0.12.4.tar.gz Macintosh Installer (Universal): https://nodejs.org/dist/v0.12.4/node-v0.12.4.pkg diff --git a/locale/en/blog/release/v0.12.5.md b/locale/en/blog/release/v0.12.5.md index 3037ca8d208b4..6ed1c71d39dfa 100644 --- a/locale/en/blog/release/v0.12.5.md +++ b/locale/en/blog/release/v0.12.5.md @@ -44,7 +44,6 @@ written with Node.js are vulnerable to Denial Of Service attacks. * windows: broadcast WM_SETTINGCHANGE after install (Mathias Küsel) - Source Code: https://nodejs.org/dist/v0.12.5/node-v0.12.5.tar.gz Macintosh Installer (Universal): https://nodejs.org/dist/v0.12.5/node-v0.12.5.pkg diff --git a/locale/en/blog/release/v0.12.6.md b/locale/en/blog/release/v0.12.6.md index 9a69bb061491d..07cbd2077c96b 100644 --- a/locale/en/blog/release/v0.12.6.md +++ b/locale/en/blog/release/v0.12.6.md @@ -16,7 +16,6 @@ attack. * V8: fix out-of-band write in utf8 decoder - Source Code: https://nodejs.org/dist/v0.12.6/node-v0.12.6.tar.gz Macintosh Installer (Universal): https://nodejs.org/dist/v0.12.6/node-v0.12.6.pkg diff --git a/locale/en/blog/release/v0.12.7.md b/locale/en/blog/release/v0.12.7.md index a2b3acb4a6999..e69a8a791c836 100644 --- a/locale/en/blog/release/v0.12.7.md +++ b/locale/en/blog/release/v0.12.7.md @@ -22,7 +22,6 @@ OpenSSL's website](http://openssl.org/news/secadv_20150709.txt). * win,msi: create npm folder in AppData directory (Steven Rockarts) - Source Code: https://nodejs.org/dist/v0.12.7/node-v0.12.7.tar.gz Macintosh Installer (Universal): https://nodejs.org/dist/v0.12.7/node-v0.12.7.pkg diff --git a/locale/en/blog/release/v0.12.9.md b/locale/en/blog/release/v0.12.9.md index b0dda36661bd3..03958f4a83706 100644 --- a/locale/en/blog/release/v0.12.9.md +++ b/locale/en/blog/release/v0.12.9.md @@ -20,7 +20,6 @@ author: Rod Vagg * [[`8d24a14f2c`](https://github.com/nodejs/node/commit/8d24a14f2c)] - **deps**: upgrade to openssl 1.0.1q (Ben Noordhuis) [#4133](https://github.com/nodejs/node/pull/4133) * [[`dfc6f4a9af`](https://github.com/nodejs/node/commit/dfc6f4a9af)] - **http**: fix pipeline regression (Fedor Indutny) - Windows 32-bit Installer: https://nodejs.org/dist/v0.12.9/node-v0.12.9-x86.msi
Windows 64-bit Installer: https://nodejs.org/dist/v0.12.9/x64/node-v0.12.9-x64.msi
Windows 32-bit Binary: https://nodejs.org/dist/v0.12.9/node.exe
diff --git a/locale/en/blog/release/v0.4.12.md b/locale/en/blog/release/v0.4.12.md index f2356bd3ae3b5..451fa9b15e56b 100644 --- a/locale/en/blog/release/v0.4.12.md +++ b/locale/en/blog/release/v0.4.12.md @@ -23,7 +23,6 @@ layout: blog-post.hbs
  • #1719 Drain OpenSSL error queue
  • Fix error reporting in net.Server.listen
    • - Download: https://nodejs.org/dist/node-v0.4.12.tar.gz Website: https://nodejs.org/docs/v0.4.12/ diff --git a/locale/en/blog/release/v0.4.3.md b/locale/en/blog/release/v0.4.3.md index d9400e289eaa6..e0ef96609fb44 100644 --- a/locale/en/blog/release/v0.4.3.md +++ b/locale/en/blog/release/v0.4.3.md @@ -23,8 +23,6 @@ layout: blog-post.hbs
  • Upgrade V8 to 3.1.8.3
    • - - Download: https://nodejs.org/dist/node-v0.4.3.tar.gz Website: https://nodejs.org/docs/v0.4.3/ diff --git a/locale/en/blog/release/v0.4.4.md b/locale/en/blog/release/v0.4.4.md index bcaf32627aa16..07c5ada0cf788 100644 --- a/locale/en/blog/release/v0.4.4.md +++ b/locale/en/blog/release/v0.4.4.md @@ -19,8 +19,6 @@ layout: blog-post.hbs
  • Added support for removing .once listeners (GH-806)
  • Upgrade V8 to 3.1.8.5
    • - - Download: https://nodejs.org/dist/node-v0.4.4.tar.gz Website: https://nodejs.org/docs/v0.4.4 diff --git a/locale/en/blog/release/v0.4.5.md b/locale/en/blog/release/v0.4.5.md index 13c0e77652df5..07d2e9468fc6b 100644 --- a/locale/en/blog/release/v0.4.5.md +++ b/locale/en/blog/release/v0.4.5.md @@ -20,13 +20,10 @@ layout: blog-post.hbs
  • Set default host header properly GH-721 (isaacs)
  • Upgrade V8 to 3.1.8.8
    • - - Download: https://nodejs.org/dist/node-v0.4.5.tar.gz Website: https://nodejs.org/docs/v0.4.5 Documentation: https://nodejs.org/docs/v0.4.5/api/ - announcement diff --git a/locale/en/blog/release/v0.4.7.md b/locale/en/blog/release/v0.4.7.md index ee590019d6d68..d59bd45c0091b 100644 --- a/locale/en/blog/release/v0.4.7.md +++ b/locale/en/blog/release/v0.4.7.md @@ -18,7 +18,6 @@ layout: blog-post.hbs
  • Fix timeouts with floating point numbers #897 (Jorge Chamorro Bieling)
  • Improve docs.
    • - Download: https://nodejs.org/dist/node-v0.4.7.tar.gz Website: https://nodejs.org/docs/v0.4.7/ diff --git a/locale/en/blog/release/v0.4.8.md b/locale/en/blog/release/v0.4.8.md index 70f62609851d9..7f9ff8edf13d2 100644 --- a/locale/en/blog/release/v0.4.8.md +++ b/locale/en/blog/release/v0.4.8.md @@ -48,9 +48,6 @@ layout: blog-post.hbs * Upgrade V8 to 3.1.8.16. - - - Website: https://nodejs.org/docs/v0.4.8/ Download: https://nodejs.org/dist/node-v0.4.8.tar.gz diff --git a/locale/en/blog/release/v0.4.9.md b/locale/en/blog/release/v0.4.9.md index 173a0f6606699..8ee3264c85484 100644 --- a/locale/en/blog/release/v0.4.9.md +++ b/locale/en/blog/release/v0.4.9.md @@ -28,7 +28,6 @@ layout: blog-post.hbs
  • Upgrade V8 to 3.1.8.25, upgrade http-parser.
    • - Download: https://nodejs.org/dist/node-v0.4.9.tar.gz Website: https://nodejs.org/docs/v0.4.9 diff --git a/locale/en/blog/release/v0.5.1.md b/locale/en/blog/release/v0.5.1.md index 82aa94965abdf..494cb5b0ad503 100644 --- a/locale/en/blog/release/v0.5.1.md +++ b/locale/en/blog/release/v0.5.1.md @@ -21,9 +21,6 @@ layout: blog-post.hbs
  • libuv backend improvements
  • Upgrade V8 to 3.4.10
    • - - - Download: https://nodejs.org/dist/v0.5.1/node-v0.5.1.tar.gz Windows Build: https://nodejs.org/dist/v0.5.1/node.exe diff --git a/locale/en/blog/release/v0.5.10.md b/locale/en/blog/release/v0.5.10.md index 108b83e6429d2..78f3933a5a05c 100644 --- a/locale/en/blog/release/v0.5.10.md +++ b/locale/en/blog/release/v0.5.10.md @@ -33,8 +33,6 @@ layout: blog-post.hbs
  • Upgrade V8 to 3.7.0
  • Upgrade GYP to r1081
    • - - Download: https://nodejs.org/dist/v0.5.10/node-v0.5.10.tar.gz Windows Executable: https://nodejs.org/dist/v0.5.10/node.exe diff --git a/locale/en/blog/release/v0.5.3.md b/locale/en/blog/release/v0.5.3.md index 2d424e913d64e..776a4ec11c857 100644 --- a/locale/en/blog/release/v0.5.3.md +++ b/locale/en/blog/release/v0.5.3.md @@ -29,8 +29,6 @@ layout: blog-post.hbs
  • Fix startup time regressions.
  • doc improvements
    • - - Download: https://nodejs.org/dist/v0.5.3/node-v0.5.3.tar.gz Windows Executable: https://nodejs.org/dist/v0.5.3/node.exe diff --git a/locale/en/blog/release/v0.5.4.md b/locale/en/blog/release/v0.5.4.md index 176fe88a90a8f..94b6ae17d77ac 100644 --- a/locale/en/blog/release/v0.5.4.md +++ b/locale/en/blog/release/v0.5.4.md @@ -21,7 +21,6 @@ layout: blog-post.hbs
  • CMake improvements (Tom Huges)
  • Upgrade V8 to 3.5.4.
    • - Download: https://nodejs.org/dist/v0.5.4/node-v0.5.4.tar.gz Windows Executable: https://nodejs.org/dist/v0.5.4/node.exe diff --git a/locale/en/blog/release/v0.5.7.md b/locale/en/blog/release/v0.5.7.md index 8a8111f8e50ab..2f07edb83fc78 100644 --- a/locale/en/blog/release/v0.5.7.md +++ b/locale/en/blog/release/v0.5.7.md @@ -27,8 +27,6 @@ layout: blog-post.hbs
  • #1707 Fix hasOwnProperty security problem in querystring (isaacs)
  • #1719 Drain OpenSSL error queue
    • - - Download: https://nodejs.org/dist/v0.5.7/node-v0.5.7.tar.gz Windows Executable: https://nodejs.org/dist/v0.5.7/node.exe diff --git a/locale/en/blog/release/v0.5.9.md b/locale/en/blog/release/v0.5.9.md index 60a9877d2e078..7de4a463311ac 100644 --- a/locale/en/blog/release/v0.5.9.md +++ b/locale/en/blog/release/v0.5.9.md @@ -20,7 +20,6 @@ layout: blog-post.hbs
  • process.stderr now goes through libuv. Both process.stdout and process.stderr are blocking when referencing a TTY.
  • net_uv performance improvements (Ben Noordhuis, Bert Belder)
    • - Download: https://nodejs.org/dist/v0.5.9/node-v0.5.9.tar.gz Windows Executable: https://nodejs.org/dist/v0.5.9/node.exe diff --git a/locale/en/blog/release/v0.6.1.md b/locale/en/blog/release/v0.6.1.md index 3a3d5b6d1e43a..f8005a430b565 100644 --- a/locale/en/blog/release/v0.6.1.md +++ b/locale/en/blog/release/v0.6.1.md @@ -24,7 +24,6 @@ layout: blog-post.hbs
  • #2052 readline get window columns correctly
  • Upgrade V8 to 3.6.6.7
    • - Source Code: https://nodejs.org/dist/v0.6.1/node-v0.6.1.tar.gz Windows Installer: https://nodejs.org/dist/v0.6.1/node-v0.6.1.msi diff --git a/locale/en/blog/release/v0.6.20.md b/locale/en/blog/release/v0.6.20.md index ea392a623a114..29127f399dede 100644 --- a/locale/en/blog/release/v0.6.20.md +++ b/locale/en/blog/release/v0.6.20.md @@ -21,7 +21,6 @@ layout: blog-post.hbs * windows: don't print error when GetConsoleTitleW returns an empty string (Bert Belder) - Source Code: https://nodejs.org/dist/v0.6.20/node-v0.6.20.tar.gz Windows Installer: https://nodejs.org/dist/v0.6.20/node-v0.6.20.msi diff --git a/locale/en/blog/release/v0.6.21.md b/locale/en/blog/release/v0.6.21.md index e2a0c8add310d..42f6072101570 100644 --- a/locale/en/blog/release/v0.6.21.md +++ b/locale/en/blog/release/v0.6.21.md @@ -13,7 +13,6 @@ layout: blog-post.hbs * net: make pause/resume work with connecting sockets (Bert Belder) - Source Code: https://nodejs.org/dist/v0.6.21/node-v0.6.21.tar.gz Windows Installer: https://nodejs.org/dist/v0.6.21/node-v0.6.21.msi diff --git a/locale/en/blog/release/v0.7.0.md b/locale/en/blog/release/v0.7.0.md index fa28af5e10890..653fe6de8b10d 100644 --- a/locale/en/blog/release/v0.7.0.md +++ b/locale/en/blog/release/v0.7.0.md @@ -20,7 +20,6 @@ layout: blog-post.hbs
  • Use isolates for internal debugger (Fedor Indutny)
  • Bug fixes
    • - Source Code: https://nodejs.org/dist/v0.7.0/node-v0.7.0.tar.gz Windows Installer: https://nodejs.org/dist/v0.7.0/node-v0.7.0.msi diff --git a/locale/en/blog/release/v0.7.6.md b/locale/en/blog/release/v0.7.6.md index 1cbd6addc7858..e854daaf0b75c 100644 --- a/locale/en/blog/release/v0.7.6.md +++ b/locale/en/blog/release/v0.7.6.md @@ -38,7 +38,6 @@ layout: blog-post.hbs
  • expose the zlib and http_parser version in process.versions (Nathan Rajlich)
    • -

    Source Code: https://nodejs.org/dist/v0.7.6/node-v0.7.6.tar.gz

    Windows Installer: https://nodejs.org/dist/v0.7.6/node-v0.7.6.msi

    Windows x64 Files: https://nodejs.org/dist/v0.7.6/x64/

    diff --git a/locale/en/blog/release/v0.8.0.md b/locale/en/blog/release/v0.8.0.md index 312f1760fde07..9fdaf2739874a 100644 --- a/locale/en/blog/release/v0.8.0.md +++ b/locale/en/blog/release/v0.8.0.md @@ -96,14 +96,12 @@ Requests per second: 3317.24 [#/sec] (mean) # 0.8.0 Requests per second: 3795.34 [#/sec] (mean) +14.41% - $ TYPE=bytes LENGTH=1024 bash benchmark/http.sh 2>&1 | grep Req # v0.6.19 Requests per second: 3258.42 [#/sec] (mean) # 0.8.0 Requests per second: 3585.62 [#/sec] (mean) +10.04% - $ TYPE=bytes LENGTH=123456 bash benchmark/http.sh 2>&1 | grep Req # v0.6.19 Requests per second: 218.51 [#/sec] (mean) @@ -146,7 +144,6 @@ The vast majority of the performance boost is due to improvements in V8. They've been very responsive to the needs of the Node.js project. A lot of Node's success is due to being built on such a stellar VM. - ## Build System Since its inception Node has used the WAF build system which is a Python @@ -167,7 +164,6 @@ npm. In future releases, node-waf will be officially deprecated. If you are currently using a wscript in your addon, please migrate to gyp as soon as possible. - ## Stabler The transition from libev and libeio to libuv in 0.6 was somewhat @@ -345,7 +341,6 @@ v0.7.12, your regularly scheduled release announcement: * Rename GYP variable node_use_system_openssl to be consistent (Ryan Dahl) - Source Code: https://nodejs.org/dist/v0.8.0/node-v0.8.0.tar.gz Macintosh Installer (Universal): https://nodejs.org/dist/v0.8.0/node-v0.8.0.pkg diff --git a/locale/en/blog/release/v0.8.1.md b/locale/en/blog/release/v0.8.1.md index cdb337a1c10e4..d1ee4bb3a5e63 100644 --- a/locale/en/blog/release/v0.8.1.md +++ b/locale/en/blog/release/v0.8.1.md @@ -45,7 +45,6 @@ layout: blog-post.hbs * windows: better (f)utimes and (f)stat (Bert Belder) - Source Code: https://nodejs.org/dist/v0.8.1/node-v0.8.1.tar.gz Macintosh Installer (Universal): https://nodejs.org/dist/v0.8.1/node-v0.8.1.pkg diff --git a/locale/en/blog/release/v0.8.10.md b/locale/en/blog/release/v0.8.10.md index bc4af62d5d03c..5815699b7487a 100644 --- a/locale/en/blog/release/v0.8.10.md +++ b/locale/en/blog/release/v0.8.10.md @@ -47,7 +47,6 @@ layout: blog-post.hbs * openssl: Use optimized assembly code for x86 and x64 (Bert Belder) - Source Code: https://nodejs.org/dist/v0.8.10/node-v0.8.10.tar.gz Macintosh Installer (Universal): https://nodejs.org/dist/v0.8.10/node-v0.8.10.pkg diff --git a/locale/en/blog/release/v0.8.11.md b/locale/en/blog/release/v0.8.11.md index 039f4667610fc..5f8c210104efd 100644 --- a/locale/en/blog/release/v0.8.11.md +++ b/locale/en/blog/release/v0.8.11.md @@ -17,7 +17,6 @@ instead. * fs: Fix stat() size reporting for large files (Ben Noordhuis) - Source Code: https://nodejs.org/dist/v0.8.11/node-v0.8.11.tar.gz Macintosh Installer (Universal): https://nodejs.org/dist/v0.8.11/node-v0.8.11.pkg diff --git a/locale/en/blog/release/v0.8.12.md b/locale/en/blog/release/v0.8.12.md index 2347bcce7c81d..1c663acf82e3a 100644 --- a/locale/en/blog/release/v0.8.12.md +++ b/locale/en/blog/release/v0.8.12.md @@ -27,7 +27,6 @@ layout: blog-post.hbs * http: handle multiple Proxy-Authenticate values (Willi Eggeling) - Source Code: https://nodejs.org/dist/v0.8.12/node-v0.8.12.tar.gz Macintosh Installer (Universal): https://nodejs.org/dist/v0.8.12/node-v0.8.12.pkg diff --git a/locale/en/blog/release/v0.8.13.md b/locale/en/blog/release/v0.8.13.md index 0d68613808bc6..e414022d0e117 100644 --- a/locale/en/blog/release/v0.8.13.md +++ b/locale/en/blog/release/v0.8.13.md @@ -30,7 +30,6 @@ Please use 0.8.14 instead. * repl: ensure each REPL instance gets its own "context" (Nathan Rajlich) - Source Code: https://nodejs.org/dist/v0.8.13/node-v0.8.13.tar.gz Macintosh Installer (Universal): https://nodejs.org/dist/v0.8.13/node-v0.8.13.pkg diff --git a/locale/en/blog/release/v0.8.14.md b/locale/en/blog/release/v0.8.14.md index 7611f36d4641d..36a64472e2b1a 100644 --- a/locale/en/blog/release/v0.8.14.md +++ b/locale/en/blog/release/v0.8.14.md @@ -11,7 +11,6 @@ Note: v0.8.13 contains a regression in the EventEmitter class. This is a bugfix release, but contains no new features. Most of the release notes are copied from v0.8.13, since it didn't live long. - 2012.10.25, Version 0.8.14 (Stable) * events: Don't clobber pre-existing _events obj in EE ctor (isaacs) @@ -34,7 +33,6 @@ release notes are copied from v0.8.13, since it didn't live long. * repl: ensure each REPL instance gets its own "context" (Nathan Rajlich) - Source Code: https://nodejs.org/dist/v0.8.14/node-v0.8.14.tar.gz Macintosh Installer (Universal): https://nodejs.org/dist/v0.8.14/node-v0.8.14.pkg diff --git a/locale/en/blog/release/v0.8.15.md b/locale/en/blog/release/v0.8.15.md index 1030e33acf647..ce9a182dd231e 100644 --- a/locale/en/blog/release/v0.8.15.md +++ b/locale/en/blog/release/v0.8.15.md @@ -25,7 +25,6 @@ layout: blog-post.hbs * net, tls: fix connect() resource leak (Ben Noordhuis) - Source Code: https://nodejs.org/dist/v0.8.15/node-v0.8.15.tar.gz Macintosh Installer (Universal): https://nodejs.org/dist/v0.8.15/node-v0.8.15.pkg diff --git a/locale/en/blog/release/v0.8.16.md b/locale/en/blog/release/v0.8.16.md index d50568d6f6ede..c11c748370f87 100644 --- a/locale/en/blog/release/v0.8.16.md +++ b/locale/en/blog/release/v0.8.16.md @@ -19,7 +19,6 @@ layout: blog-post.hbs * net: More accurate IP address validation and IPv6 dotted notation. (Joshua Erickson) - Source Code: https://nodejs.org/dist/v0.8.16/node-v0.8.16.tar.gz Macintosh Installer (Universal): https://nodejs.org/dist/v0.8.16/node-v0.8.16.pkg diff --git a/locale/en/blog/release/v0.8.17.md b/locale/en/blog/release/v0.8.17.md index 43cdda4a7f78c..f42a147afccb6 100644 --- a/locale/en/blog/release/v0.8.17.md +++ b/locale/en/blog/release/v0.8.17.md @@ -34,7 +34,6 @@ upgrade ASAP. * http: bubble up parser errors to ClientRequest (Brian White) - Source Code: https://nodejs.org/dist/v0.8.17/node-v0.8.17.tar.gz Macintosh Installer (Universal): https://nodejs.org/dist/v0.8.17/node-v0.8.17.pkg diff --git a/locale/en/blog/release/v0.8.18.md b/locale/en/blog/release/v0.8.18.md index 33c8b4ef03210..da28adae9e7b5 100644 --- a/locale/en/blog/release/v0.8.18.md +++ b/locale/en/blog/release/v0.8.18.md @@ -21,7 +21,6 @@ layout: blog-post.hbs * http: fix "Cannot call method 'emit' of null" (Ben Noordhuis) - Source Code: https://nodejs.org/dist/v0.8.18/node-v0.8.18.tar.gz Macintosh Installer (Universal): https://nodejs.org/dist/v0.8.18/node-v0.8.18.pkg diff --git a/locale/en/blog/release/v0.8.19.md b/locale/en/blog/release/v0.8.19.md index 531854c9d5dad..9683a099d2795 100644 --- a/locale/en/blog/release/v0.8.19.md +++ b/locale/en/blog/release/v0.8.19.md @@ -27,7 +27,6 @@ layout: blog-post.hbs * windows: map ERROR_DIRECTORY to UV_ENOENT (Bert Belder) - Source Code: https://nodejs.org/dist/v0.8.19/node-v0.8.19.tar.gz Macintosh Installer (Universal): https://nodejs.org/dist/v0.8.19/node-v0.8.19.pkg diff --git a/locale/en/blog/release/v0.8.2.md b/locale/en/blog/release/v0.8.2.md index d85e896668ab6..b33a026a8b622 100644 --- a/locale/en/blog/release/v0.8.2.md +++ b/locale/en/blog/release/v0.8.2.md @@ -41,7 +41,6 @@ layout: blog-post.hbs * unix: fix EINPROGRESS busy loop (Ben Noordhuis) - Source Code: https://nodejs.org/dist/v0.8.2/node-v0.8.2.tar.gz Macintosh Installer (Universal): https://nodejs.org/dist/v0.8.2/node-v0.8.2.pkg diff --git a/locale/en/blog/release/v0.8.20.md b/locale/en/blog/release/v0.8.20.md index 323ca5c5f496c..1499ffb29208a 100644 --- a/locale/en/blog/release/v0.8.20.md +++ b/locale/en/blog/release/v0.8.20.md @@ -17,7 +17,6 @@ layout: blog-post.hbs * http: protect against response splitting attacks (Bert Belder) - Source Code: https://nodejs.org/dist/v0.8.20/node-v0.8.20.tar.gz Macintosh Installer (Universal): https://nodejs.org/dist/v0.8.20/node-v0.8.20.pkg diff --git a/locale/en/blog/release/v0.8.21.md b/locale/en/blog/release/v0.8.21.md index 59d2d4752e924..4641dd4c106e1 100644 --- a/locale/en/blog/release/v0.8.21.md +++ b/locale/en/blog/release/v0.8.21.md @@ -19,7 +19,6 @@ layout: blog-post.hbs * unix: Handle EINPROGRESS from domain sockets (Ben Noordhuis) - Source Code: https://nodejs.org/dist/v0.8.21/node-v0.8.21.tar.gz Macintosh Installer (Universal): https://nodejs.org/dist/v0.8.21/node-v0.8.21.pkg diff --git a/locale/en/blog/release/v0.8.22.md b/locale/en/blog/release/v0.8.22.md index e2548bd260da4..49fcff3816b11 100644 --- a/locale/en/blog/release/v0.8.22.md +++ b/locale/en/blog/release/v0.8.22.md @@ -17,7 +17,6 @@ layout: blog-post.hbs * build, windows: disable SEH (Ben Noordhuis) - Source Code: https://nodejs.org/dist/v0.8.22/node-v0.8.22.tar.gz Macintosh Installer (Universal): https://nodejs.org/dist/v0.8.22/node-v0.8.22.pkg diff --git a/locale/en/blog/release/v0.8.23.md b/locale/en/blog/release/v0.8.23.md index 90518b6bdc6fb..d2db6025f6225 100644 --- a/locale/en/blog/release/v0.8.23.md +++ b/locale/en/blog/release/v0.8.23.md @@ -23,7 +23,6 @@ layout: blog-post.hbs * windows/msi: fix msi build issue with WiX 3.7/3.8 (Raymond Feng) - Source Code: https://nodejs.org/dist/v0.8.23/node-v0.8.23.tar.gz Macintosh Installer (Universal): https://nodejs.org/dist/v0.8.23/node-v0.8.23.pkg diff --git a/locale/en/blog/release/v0.8.24.md b/locale/en/blog/release/v0.8.24.md index 2eedda034a63e..215fd8321fe24 100644 --- a/locale/en/blog/release/v0.8.24.md +++ b/locale/en/blog/release/v0.8.24.md @@ -17,7 +17,6 @@ layout: blog-post.hbs * handle_wrap: fix NULL pointer dereference (Ben Noordhuis) - Source Code: https://nodejs.org/dist/v0.8.24/node-v0.8.24.tar.gz Macintosh Installer (Universal): https://nodejs.org/dist/v0.8.24/node-v0.8.24.pkg diff --git a/locale/en/blog/release/v0.8.25.md b/locale/en/blog/release/v0.8.25.md index 43e0c0e2f1baf..3945246a1aedf 100644 --- a/locale/en/blog/release/v0.8.25.md +++ b/locale/en/blog/release/v0.8.25.md @@ -13,7 +13,6 @@ layout: blog-post.hbs * child_process: fix handle delivery (Ben Noordhuis) - Source Code: https://nodejs.org/dist/v0.8.25/node-v0.8.25.tar.gz Macintosh Installer (Universal): https://nodejs.org/dist/v0.8.25/node-v0.8.25.pkg diff --git a/locale/en/blog/release/v0.8.26.md b/locale/en/blog/release/v0.8.26.md index f4c19166b2b1b..1896565b2aebd 100644 --- a/locale/en/blog/release/v0.8.26.md +++ b/locale/en/blog/release/v0.8.26.md @@ -26,7 +26,6 @@ upgrade as soon as possible. Details will be released soon. * readline: pause stdin before turning off terminal raw mode (Daniel Chatfield) - Source Code: https://nodejs.org/dist/v0.8.26/node-v0.8.26.tar.gz Macintosh Installer (Universal): https://nodejs.org/dist/v0.8.26/node-v0.8.26.pkg diff --git a/locale/en/blog/release/v0.8.27.md b/locale/en/blog/release/v0.8.27.md index bb19846a5b808..9064b99ef7b45 100644 --- a/locale/en/blog/release/v0.8.27.md +++ b/locale/en/blog/release/v0.8.27.md @@ -22,7 +22,6 @@ environment variable set. * fs: close file if fstat() fails in readFile() (cjihrig) - Source Code: https://nodejs.org/dist/v0.8.27/node-v0.8.27.tar.gz Macintosh Installer (Universal): https://nodejs.org/dist/v0.8.27/node-v0.8.27.pkg diff --git a/locale/en/blog/release/v0.8.28.md b/locale/en/blog/release/v0.8.28.md index d76ab3fd58331..4b8113cba1431 100644 --- a/locale/en/blog/release/v0.8.28.md +++ b/locale/en/blog/release/v0.8.28.md @@ -11,7 +11,6 @@ layout: blog-post.hbs * v8: Interrupts must not mask stack overflow. (Fedor Indutny) - Source Code: https://nodejs.org/dist/v0.8.28/node-v0.8.28.tar.gz Macintosh Installer (Universal): https://nodejs.org/dist/v0.8.28/node-v0.8.28.pkg diff --git a/locale/en/blog/release/v0.8.3.md b/locale/en/blog/release/v0.8.3.md index 11cc5cc6c2ad4..e363bc9f72328 100644 --- a/locale/en/blog/release/v0.8.3.md +++ b/locale/en/blog/release/v0.8.3.md @@ -39,7 +39,6 @@ layout: blog-post.hbs * crypto: Fix memory leak in DecipherUpdate() (Ben Noordhuis) - Source Code: https://nodejs.org/dist/v0.8.3/node-v0.8.3.tar.gz Macintosh Installer (Universal): https://nodejs.org/dist/v0.8.3/node-v0.8.3.pkg diff --git a/locale/en/blog/release/v0.8.4.md b/locale/en/blog/release/v0.8.4.md index 43ca512b6c83a..bab3227fc0cfb 100644 --- a/locale/en/blog/release/v0.8.4.md +++ b/locale/en/blog/release/v0.8.4.md @@ -25,7 +25,6 @@ layout: blog-post.hbs * net: ignore socket.setTimeout(Infinity or NaN) (Fedor Indutny) - Source Code: https://nodejs.org/dist/v0.8.4/node-v0.8.4.tar.gz Macintosh Installer (Universal): https://nodejs.org/dist/v0.8.4/node-v0.8.4.pkg diff --git a/locale/en/blog/release/v0.8.5.md b/locale/en/blog/release/v0.8.5.md index f7273038768be..c1dfae12a19a9 100644 --- a/locale/en/blog/release/v0.8.5.md +++ b/locale/en/blog/release/v0.8.5.md @@ -43,7 +43,6 @@ layout: blog-post.hbs * build: Sign pkg installer for OS X (isaacs) - Source Code: https://nodejs.org/dist/v0.8.5/node-v0.8.5.tar.gz Macintosh Installer (Universal): https://nodejs.org/dist/v0.8.5/node-v0.8.5.pkg diff --git a/locale/en/blog/release/v0.8.6.md b/locale/en/blog/release/v0.8.6.md index 480b98c440308..441f872e4ea5c 100644 --- a/locale/en/blog/release/v0.8.6.md +++ b/locale/en/blog/release/v0.8.6.md @@ -39,7 +39,6 @@ This is an experimental feature. Please use it and provide feedback. * windows: map WSANO_DATA to UV_ENOENT (Bert Belder) - Source Code: https://nodejs.org/dist/v0.8.6/node-v0.8.6.tar.gz Macintosh Installer (Universal): https://nodejs.org/dist/v0.8.6/node-v0.8.6.pkg diff --git a/locale/en/blog/release/v0.8.7.md b/locale/en/blog/release/v0.8.7.md index fe7f8bc13047f..a1d4c441f21a2 100644 --- a/locale/en/blog/release/v0.8.7.md +++ b/locale/en/blog/release/v0.8.7.md @@ -29,7 +29,6 @@ layout: blog-post.hbs * windows: fix typos in process-stdio.c (Bert Belder) - Source Code: https://nodejs.org/dist/v0.8.7/node-v0.8.7.tar.gz Macintosh Installer (Universal): https://nodejs.org/dist/v0.8.7/node-v0.8.7.pkg diff --git a/locale/en/blog/release/v0.8.8.md b/locale/en/blog/release/v0.8.8.md index 18af78c9cfee5..e6c9f659bf088 100644 --- a/locale/en/blog/release/v0.8.8.md +++ b/locale/en/blog/release/v0.8.8.md @@ -31,7 +31,6 @@ layout: blog-post.hbs * windows: make junctions work again (Bert Belder) - Source Code: https://nodejs.org/dist/v0.8.8/node-v0.8.8.tar.gz Macintosh Installer (Universal): https://nodejs.org/dist/v0.8.8/node-v0.8.8.pkg diff --git a/locale/en/blog/release/v0.8.9.md b/locale/en/blog/release/v0.8.9.md index 5e990230b5d99..b7ec86305c299 100644 --- a/locale/en/blog/release/v0.8.9.md +++ b/locale/en/blog/release/v0.8.9.md @@ -51,7 +51,6 @@ layout: blog-post.hbs * stream.pipe: Don't call destroy() unless it's a function (isaacs) - Source Code: https://nodejs.org/dist/v0.8.9/node-v0.8.9.tar.gz Macintosh Installer (Universal): https://nodejs.org/dist/v0.8.9/node-v0.8.9.pkg diff --git a/locale/en/blog/release/v0.9.0.md b/locale/en/blog/release/v0.9.0.md index 22f2422607028..957092e550202 100644 --- a/locale/en/blog/release/v0.9.0.md +++ b/locale/en/blog/release/v0.9.0.md @@ -29,7 +29,6 @@ layout: blog-post.hbs * Fix #3521 Make process.env more like a regular Object (isaacs) - Source Code: https://nodejs.org/dist/v0.9.0/node-v0.9.0.tar.gz Macintosh Installer (Universal): https://nodejs.org/dist/v0.9.0/node-v0.9.0.pkg diff --git a/locale/en/blog/release/v0.9.1.md b/locale/en/blog/release/v0.9.1.md index 928d63729df0d..3dc79291a854b 100644 --- a/locale/en/blog/release/v0.9.1.md +++ b/locale/en/blog/release/v0.9.1.md @@ -71,7 +71,6 @@ layout: blog-post.hbs * windows: signal handling support with uv_signal_t (Bert Belder) - Source Code: https://nodejs.org/dist/v0.9.1/node-v0.9.1.tar.gz Macintosh Installer (Universal): https://nodejs.org/dist/v0.9.1/node-v0.9.1.pkg diff --git a/locale/en/blog/release/v0.9.10.md b/locale/en/blog/release/v0.9.10.md index faf6f6d7349ac..cec2303993335 100644 --- a/locale/en/blog/release/v0.9.10.md +++ b/locale/en/blog/release/v0.9.10.md @@ -39,7 +39,6 @@ layout: blog-post.hbs * windows: MSI installer enhancements (Scott Blomquist, Jim Schubert) - Source Code: https://nodejs.org/dist/v0.9.10/node-v0.9.10.tar.gz Macintosh Installer (Universal): https://nodejs.org/dist/v0.9.10/node-v0.9.10.pkg diff --git a/locale/en/blog/release/v0.9.11.md b/locale/en/blog/release/v0.9.11.md index 43e12fa538e5f..fb1117519fb3b 100644 --- a/locale/en/blog/release/v0.9.11.md +++ b/locale/en/blog/release/v0.9.11.md @@ -43,7 +43,6 @@ layout: blog-post.hbs * crypto: fix uninitialized memory access in openssl (Ben Noordhuis) - Source Code: https://nodejs.org/dist/v0.9.11/node-v0.9.11.tar.gz Macintosh Installer (Universal): https://nodejs.org/dist/v0.9.11/node-v0.9.11.pkg diff --git a/locale/en/blog/release/v0.9.12.md b/locale/en/blog/release/v0.9.12.md index 30453b98313fb..ed7a6d64e26a1 100644 --- a/locale/en/blog/release/v0.9.12.md +++ b/locale/en/blog/release/v0.9.12.md @@ -61,7 +61,6 @@ programs. It is as stable as 0.9 is going to get. * events: Code cleanup and performance improvements (Trevor Norris) - Source Code: https://nodejs.org/dist/v0.9.12/node-v0.9.12.tar.gz Macintosh Installer (Universal): https://nodejs.org/dist/v0.9.12/node-v0.9.12.pkg diff --git a/locale/en/blog/release/v0.9.2.md b/locale/en/blog/release/v0.9.2.md index 32d9d7f35e8a0..7d020ab452b8c 100644 --- a/locale/en/blog/release/v0.9.2.md +++ b/locale/en/blog/release/v0.9.2.md @@ -49,7 +49,6 @@ layout: blog-post.hbs * url: Go much faster by using Url class (isaacs) - Source Code: https://nodejs.org/dist/v0.9.2/node-v0.9.2.tar.gz Macintosh Installer (Universal): https://nodejs.org/dist/v0.9.2/node-v0.9.2.pkg diff --git a/locale/en/blog/release/v0.9.3.md b/locale/en/blog/release/v0.9.3.md index a4774f785842a..80da2e2d5a4ec 100644 --- a/locale/en/blog/release/v0.9.3.md +++ b/locale/en/blog/release/v0.9.3.md @@ -41,7 +41,6 @@ layout: blog-post.hbs * streams: fix pipe is destructed by 'end' from destination (koichik) - Source Code: https://nodejs.org/dist/v0.9.3/node-v0.9.3.tar.gz Macintosh Installer (Universal): https://nodejs.org/dist/v0.9.3/node-v0.9.3.pkg diff --git a/locale/en/blog/release/v0.9.4.md b/locale/en/blog/release/v0.9.4.md index 2b8f961f3acf4..81d42de2d26cf 100644 --- a/locale/en/blog/release/v0.9.4.md +++ b/locale/en/blog/release/v0.9.4.md @@ -51,7 +51,6 @@ layout: blog-post.hbs * url: url.format escapes delimiters in path and query (J. Lee Coltrane) - Source Code: https://nodejs.org/dist/v0.9.4/node-v0.9.4.tar.gz Macintosh Installer (Universal): https://nodejs.org/dist/v0.9.4/node-v0.9.4.pkg diff --git a/locale/en/blog/release/v0.9.5.md b/locale/en/blog/release/v0.9.5.md index 861bdd8bed6bf..3ebdbeedfcc7a 100644 --- a/locale/en/blog/release/v0.9.5.md +++ b/locale/en/blog/release/v0.9.5.md @@ -37,7 +37,6 @@ layout: blog-post.hbs * node: Emit 'exit' event when exiting for an uncaught exception (isaacs) - Source Code: https://nodejs.org/dist/v0.9.5/node-v0.9.5.tar.gz Macintosh Installer (Universal): https://nodejs.org/dist/v0.9.5/node-v0.9.5.pkg diff --git a/locale/en/blog/release/v0.9.6.md b/locale/en/blog/release/v0.9.6.md index 5cff3a8750e97..c9ccf140a16bb 100644 --- a/locale/en/blog/release/v0.9.6.md +++ b/locale/en/blog/release/v0.9.6.md @@ -41,7 +41,6 @@ layout: blog-post.hbs * dgram: fix double implicit bind error (Ben Noordhuis) - Source Code: https://nodejs.org/dist/v0.9.6/node-v0.9.6.tar.gz Macintosh Installer (Universal): https://nodejs.org/dist/v0.9.6/node-v0.9.6.pkg diff --git a/locale/en/blog/release/v0.9.7.md b/locale/en/blog/release/v0.9.7.md index 6b6e6c05d3d58..d2ed1125cf66b 100644 --- a/locale/en/blog/release/v0.9.7.md +++ b/locale/en/blog/release/v0.9.7.md @@ -35,7 +35,6 @@ layout: blog-post.hbs * stream: Properly handle large reads from push-streams (isaacs) - Source Code: https://nodejs.org/dist/v0.9.7/node-v0.9.7.tar.gz Macintosh Installer (Universal): https://nodejs.org/dist/v0.9.7/node-v0.9.7.pkg diff --git a/locale/en/blog/release/v0.9.8.md b/locale/en/blog/release/v0.9.8.md index bd96bac2a9cdf..f9a816c6b31d8 100644 --- a/locale/en/blog/release/v0.9.8.md +++ b/locale/en/blog/release/v0.9.8.md @@ -29,7 +29,6 @@ layout: blog-post.hbs * linux: add futimes() fallback (Ben Noordhuis) - Source Code: https://nodejs.org/dist/v0.9.8/node-v0.9.8.tar.gz Macintosh Installer (Universal): https://nodejs.org/dist/v0.9.8/node-v0.9.8.pkg diff --git a/locale/en/blog/release/v11.0.0.md b/locale/en/blog/release/v11.0.0.md index e8f3a510bd611..83b7493a2fffd 100755 --- a/locale/en/blog/release/v11.0.0.md +++ b/locale/en/blog/release/v11.0.0.md @@ -204,7 +204,6 @@ focus primarily on improving internals, performance, and an update to V8 7.0. * [[`48a2568f41`](https://github.com/nodejs/node/commit/48a2568f41)] - **(SEMVER-MINOR)** **timers**: add hasRef method to Timeout & Immediate (Anatoli Papirovski) [#20898](https://github.com/nodejs/node/pull/20898) * [[`bed4a8c6e0`](https://github.com/nodejs/node/commit/bed4a8c6e0)] - **(SEMVER-MINOR)** **tls**: support changing credentials dynamically (cjihrig) [#23644](https://github.com/nodejs/node/pull/23644) - ### Semver-Patch Commits * [[`eccc65919a`](https://github.com/nodejs/node/commit/eccc65919a)] - **assert**: add comments for diff algorithm (Ruben Bridgewater) [#23048](https://github.com/nodejs/node/pull/23048) diff --git a/locale/en/blog/release/v4.0.0.md b/locale/en/blog/release/v4.0.0.md index 3d600858cb981..7b61321b1c16b 100644 --- a/locale/en/blog/release/v4.0.0.md +++ b/locale/en/blog/release/v4.0.0.md @@ -115,7 +115,6 @@ See https://github.com/nodejs/node/labels/confirmed-bug for complete and current * [[`7a8c3e08c3`](https://github.com/nodejs/node/commit/7a8c3e08c3)] - **timers**: Avoid linear scan in `_unrefActive`. (Julien Gilli) [#2540](https://github.com/nodejs/node/pull/2540) * [[`b630ebaf43`](https://github.com/nodejs/node/commit/b630ebaf43)] - **win,msi**: Upgrade from old upgrade code (João Reis) [#2439](https://github.com/nodejs/node/pull/2439) - Windows 32-bit Installer: https://nodejs.org/dist/v4.0.0/node-v4.0.0-x86.msi
    Windows 64-bit Installer: https://nodejs.org/dist/v4.0.0/node-v4.0.0-x64.msi
    Mac OS X 64-bit Installer: https://nodejs.org/dist/v4.0.0/node-v4.0.0.pkg
    diff --git a/locale/en/blog/release/v4.1.0.md b/locale/en/blog/release/v4.1.0.md index ddc07041b398a..916a6f378f1e2 100644 --- a/locale/en/blog/release/v4.1.0.md +++ b/locale/en/blog/release/v4.1.0.md @@ -91,8 +91,6 @@ See https://github.com/nodejs/node/labels/confirmed-bug for complete and current * [[`ba47511976`](https://github.com/nodejs/node/commit/ba47511976)] - **tsc**: adjust TSC membership for IBM+StrongLoop (James M Snell) [#2858](https://github.com/nodejs/node/pull/2858) * [[`e035266805`](https://github.com/nodejs/node/commit/e035266805)] - **win,msi**: fix documentation shortcut url (Brian White) [#2781](https://github.com/nodejs/node/pull/2781) - - Windows 32-bit Installer: https://nodejs.org/dist/v4.1.0/node-v4.1.0-x86.msi
    Windows 64-bit Installer: https://nodejs.org/dist/v4.1.0/node-v4.1.0-x64.msi
    Windows 32-bit Binary: https://nodejs.org/dist/v4.1.0/win-x86/node.exe
    diff --git a/locale/en/blog/release/v4.1.1.md b/locale/en/blog/release/v4.1.1.md index 358d54beef58e..1801c9dd34596 100644 --- a/locale/en/blog/release/v4.1.1.md +++ b/locale/en/blog/release/v4.1.1.md @@ -60,8 +60,6 @@ See https://github.com/nodejs/node/labels/confirmed-bug for complete and current * [[`3e09dcfc32`](https://github.com/nodejs/node/commit/3e09dcfc32)] - **test**: update cwd-enoent tests for AIX (Imran Iqbal) [#2909](https://github.com/nodejs/node/pull/2909) * [[`6ea8ec1c59`](https://github.com/nodejs/node/commit/6ea8ec1c59)] - **tools**: single, cross-platform tick processor (Matt Loring) [#2868](https://github.com/nodejs/node/pull/2868) - - Windows 32-bit Installer: https://nodejs.org/dist/v4.1.1/node-v4.1.1-x86.msi
    Windows 64-bit Installer: https://nodejs.org/dist/v4.1.1/node-v4.1.1-x64.msi
    Windows 32-bit Binary: https://nodejs.org/dist/v4.1.1/win-x86/node.exe
    diff --git a/locale/en/blog/release/v4.1.2.md b/locale/en/blog/release/v4.1.2.md index 9932528851e13..d7ddf80817a21 100644 --- a/locale/en/blog/release/v4.1.2.md +++ b/locale/en/blog/release/v4.1.2.md @@ -78,8 +78,6 @@ See https://github.com/nodejs/node/labels/confirmed-bug for complete and current * [[`5ada45bf28`](https://github.com/nodejs/node/commit/5ada45bf28)] - **test**: replace deprecated util.debug() calls (Rich Trott) [#3082](https://github.com/nodejs/node/pull/3082) * [[`d8ab4e185d`](https://github.com/nodejs/node/commit/d8ab4e185d)] - **util**: optimize promise introspection (Ben Noordhuis) [#3130](https://github.com/nodejs/node/pull/3130) - - Windows 32-bit Installer: https://nodejs.org/dist/v4.1.2/node-v4.1.2-x86.msi
    Windows 64-bit Installer: https://nodejs.org/dist/v4.1.2/node-v4.1.2-x64.msi
    Windows 32-bit Binary: https://nodejs.org/dist/v4.1.2/win-x86/node.exe
    diff --git a/locale/en/blog/release/v4.2.0.md b/locale/en/blog/release/v4.2.0.md index f7dc254c0388c..80708917793ee 100644 --- a/locale/en/blog/release/v4.2.0.md +++ b/locale/en/blog/release/v4.2.0.md @@ -46,7 +46,6 @@ See https://github.com/nodejs/node/labels/confirmed-bug for complete and current ### Commits - * [[`8383c4fe00`](https://github.com/nodejs/node/commit/8383c4fe00)] - **assert**: support arrow functions in .throws() (Ben Noordhuis) [#3276](https://github.com/nodejs/node/pull/3276) * [[`3eaa593a32`](https://github.com/nodejs/node/commit/3eaa593a32)] - **async_wrap**: correctly pass parent to init callback (Trevor Norris) [#3216](https://github.com/nodejs/node/pull/3216) * [[`54795620f6`](https://github.com/nodejs/node/commit/54795620f6)] - **buffer**: don't abort on prototype getters (Trevor Norris) [#3302](https://github.com/nodejs/node/pull/3302) @@ -107,8 +106,6 @@ See https://github.com/nodejs/node/labels/confirmed-bug for complete and current * [[`8dfdee3733`](https://github.com/nodejs/node/commit/8dfdee3733)] - **util**: correctly inspect Map/Set Iterators (Evan Lucas) [#3119](https://github.com/nodejs/node/pull/3119) * [[`b5c51fdba0`](https://github.com/nodejs/node/commit/b5c51fdba0)] - **util**: fix check for Array constructor (Evan Lucas) [#3119](https://github.com/nodejs/node/pull/3119) - - Windows 32-bit Installer: https://nodejs.org/dist/v4.2.0/node-v4.2.0-x86.msi
    Windows 64-bit Installer: https://nodejs.org/dist/v4.2.0/node-v4.2.0-x64.msi
    Windows 32-bit Binary: https://nodejs.org/dist/v4.2.0/win-x86/node.exe
    diff --git a/locale/en/blog/release/v4.2.1.md b/locale/en/blog/release/v4.2.1.md index 545f6b8ccbafe..bed011c3f47a7 100644 --- a/locale/en/blog/release/v4.2.1.md +++ b/locale/en/blog/release/v4.2.1.md @@ -27,8 +27,6 @@ layout: blog-post.hbs * [[`102cb7288c`](https://github.com/nodejs/node/commit/102cb7288c)] - **doc**: label v4.2.0 as LTS in changelog heading (Rod Vagg) [#3343](https://github.com/nodejs/node/pull/3343) * [[`c245a199a7`](https://github.com/nodejs/node/commit/c245a199a7)] - **lib**: fix undefined timeout regression (Ryan Graham) [#3331](https://github.com/nodejs/node/pull/3331 - - Windows 32-bit Installer: https://nodejs.org/dist/v4.2.1/node-v4.2.1-x86.msi
    Windows 64-bit Installer: https://nodejs.org/dist/v4.2.1/node-v4.2.1-x64.msi
    Windows 32-bit Binary: https://nodejs.org/dist/v4.2.1/win-x86/node.exe
    diff --git a/locale/en/blog/release/v4.2.2.md b/locale/en/blog/release/v4.2.2.md index 4c4cb0f800c7c..1615d34616bd4 100644 --- a/locale/en/blog/release/v4.2.2.md +++ b/locale/en/blog/release/v4.2.2.md @@ -99,9 +99,6 @@ This is an LTS maintenance release that addresses a number of issues: * [[`e69c869399`](https://github.com/nodejs/node/commit/e69c869399)] - **tls**: TLSSocket options default isServer false (Yuval Brik) [#2614](https://github.com/nodejs/node/pull/2614) * [[`0b32bbbf69`](https://github.com/nodejs/node/commit/0b32bbbf69)] - **v8**: pull fix for builtin code size on PPC (Michael Dawson) [#3474](https://github.com/nodejs/node/pull/3474) - - - Windows 32-bit Installer: https://nodejs.org/dist/v4.2.2/node-v4.2.2-x86.msi
    Windows 64-bit Installer: https://nodejs.org/dist/v4.2.2/node-v4.2.2-x64.msi
    Windows 32-bit Binary: https://nodejs.org/dist/v4.2.2/win-x86/node.exe
    diff --git a/locale/en/blog/release/v4.2.3.md b/locale/en/blog/release/v4.2.3.md index 59724064a3dcc..3204801433e03 100644 --- a/locale/en/blog/release/v4.2.3.md +++ b/locale/en/blog/release/v4.2.3.md @@ -33,8 +33,6 @@ author: Rod Vagg * [[`07233206e9`](https://github.com/nodejs/node/commit/07233206e9)] - **deps**: backport 6df9a1d from upstream v8 (Ben Noordhuis) * [[`1c8e6de78e`](https://github.com/nodejs/node/commit/1c8e6de78e)] - **http**: fix pipeline regression (Fedor Indutny) - - Windows 32-bit Installer: https://nodejs.org/dist/v4.2.3/node-v4.2.3-x86.msi
    Windows 64-bit Installer: https://nodejs.org/dist/v4.2.3/node-v4.2.3-x64.msi
    Windows 32-bit Binary: https://nodejs.org/dist/v4.2.3/win-x86/node.exe
    diff --git a/locale/en/blog/release/v4.2.4.md b/locale/en/blog/release/v4.2.4.md index 69e47654be528..c1b6f8965b099 100644 --- a/locale/en/blog/release/v4.2.4.md +++ b/locale/en/blog/release/v4.2.4.md @@ -183,8 +183,6 @@ of fixes and documentation updates. * [[`47bb94a0c3`](https://github.com/nodejs/node/commit/47bb94a0c3)] - **zlib**: only apply drain listener if given callback (Craig Cavalier) [#3534](https://github.com/nodejs/node/pull/3534) * [[`4733a60158`](https://github.com/nodejs/node/commit/4733a60158)] - **zlib**: pass kind to recursive calls to flush (Myles Borins) [#3534](https://github.com/nodejs/node/pull/3534) - - Windows 32-bit Installer: https://nodejs.org/dist/v4.2.4/node-v4.2.4-x86.msi
    Windows 64-bit Installer: https://nodejs.org/dist/v4.2.4/node-v4.2.4-x64.msi
    Windows 32-bit Binary: https://nodejs.org/dist/v4.2.4/win-x86/node.exe
    diff --git a/locale/en/blog/release/v4.2.5.md b/locale/en/blog/release/v4.2.5.md index 509593da52943..ce10bc711c3c2 100644 --- a/locale/en/blog/release/v4.2.5.md +++ b/locale/en/blog/release/v4.2.5.md @@ -39,7 +39,6 @@ author: Myles Borins ### Commits - * [[`87181cd74c`](https://github.com/nodejs/node/commit/87181cd74c)] - **assert**: accommodate ES6 classes that extend Error (Rich Trott) [#4166](https://github.com/nodejs/node/pull/4166) * [[`901172a783`](https://github.com/nodejs/node/commit/901172a783)] - **assert**: typed array deepequal performance fix (Claudio Rodriguez) [#4330](https://github.com/nodejs/node/pull/4330) * [[`55336810ee`](https://github.com/nodejs/node/commit/55336810ee)] - **async_wrap**: call callback in destructor (Trevor Norris) [#3461](https://github.com/nodejs/node/pull/3461) @@ -230,8 +229,6 @@ author: Myles Borins * [[`2d5380ea25`](https://github.com/nodejs/node/commit/2d5380ea25)] - **util**: fix constructor/instanceof checks (Brian White) [#3385](https://github.com/nodejs/node/pull/3385) * [[`1bf84b9d41`](https://github.com/nodejs/node/commit/1bf84b9d41)] - **util,src**: allow lookup of hidden values (cjihrig) [#3988](https://github.com/nodejs/node/pull/3988) - - Windows 32-bit Installer: https://nodejs.org/dist/v4.2.5/node-v4.2.5-x86.msi
    Windows 64-bit Installer: https://nodejs.org/dist/v4.2.5/node-v4.2.5-x64.msi
    Windows 32-bit Binary: https://nodejs.org/dist/v4.2.5/win-x86/node.exe
    diff --git a/locale/en/blog/release/v4.2.6.md b/locale/en/blog/release/v4.2.6.md index 9bbdcb7759bb9..d27b34171af5b 100644 --- a/locale/en/blog/release/v4.2.6.md +++ b/locale/en/blog/release/v4.2.6.md @@ -24,9 +24,6 @@ author: Myles Borins * [[`1408f7abb1`](https://github.com/nodejs/node/commit/1408f7abb1)] - **module,src**: do not wrap modules with -1 lineOffset (cjihrig) [#4298](https://github.com/nodejs/node/pull/4298) * [[`1f8e1472cc`](https://github.com/nodejs/node/commit/1f8e1472cc)] - **test**: add test for debugging one line files (cjihrig) [#4298](https://github.com/nodejs/node/pull/4298) - - - Windows 32-bit Installer: https://nodejs.org/dist/v4.2.6/node-v4.2.6-x86.msi
    Windows 64-bit Installer: https://nodejs.org/dist/v4.2.6/node-v4.2.6-x64.msi
    Windows 32-bit Binary: https://nodejs.org/dist/v4.2.6/win-x86/node.exe
    diff --git a/locale/en/blog/release/v4.3.0.md b/locale/en/blog/release/v4.3.0.md index 680839444f185..76e704a0846ab 100644 --- a/locale/en/blog/release/v4.3.0.md +++ b/locale/en/blog/release/v4.3.0.md @@ -28,8 +28,6 @@ This is an important security release. For full details see https://nodejs.org/e * [[`49ae2e0334`](https://github.com/nodejs/node/commit/49ae2e0334)] - **src**: avoid compiler warning in node_revert.cc (James M Snell) * [[`da3750f981`](https://github.com/nodejs/node/commit/da3750f981)] - **(SEMVER-MAJOR)** **src**: add --security-revert command line flag (James M Snell) - - Windows 32-bit Installer: https://nodejs.org/dist/v4.3.0/node-v4.3.0-x86.msi
    Windows 64-bit Installer: https://nodejs.org/dist/v4.3.0/node-v4.3.0-x64.msi
    Windows 32-bit Binary: https://nodejs.org/dist/v4.3.0/win-x86/node.exe
    diff --git a/locale/en/blog/release/v4.3.1.md b/locale/en/blog/release/v4.3.1.md index 39d63c2c5f57e..49e67ae13d52a 100644 --- a/locale/en/blog/release/v4.3.1.md +++ b/locale/en/blog/release/v4.3.1.md @@ -91,8 +91,6 @@ author: Myles Borins * [[`c96800a432`](https://github.com/nodejs/node/commit/c96800a432)] - **tools**: fix license-builder.sh for ICU (Richard Lau) [#4762](https://github.com/nodejs/node/pull/4762) * [[`720b03dca7`](https://github.com/nodejs/node/commit/720b03dca7)] - **tools**: add license-builder.sh to construct LICENSE (Rod Vagg) [#4194](https://github.com/nodejs/node/pull/4194) - - Windows 32-bit Installer: https://nodejs.org/dist/v4.3.1/node-v4.3.1-x86.msi
    Windows 64-bit Installer: https://nodejs.org/dist/v4.3.1/node-v4.3.1-x64.msi
    Windows 32-bit Binary: https://nodejs.org/dist/v4.3.1/win-x86/node.exe
    diff --git a/locale/en/blog/release/v4.3.2.md b/locale/en/blog/release/v4.3.2.md index c365a3fb0864d..20078bcf8f8c6 100644 --- a/locale/en/blog/release/v4.3.2.md +++ b/locale/en/blog/release/v4.3.2.md @@ -19,9 +19,6 @@ author: Myles Borins * [[`c133797d09`](https://github.com/nodejs/node/commit/c133797d09)] - **deps**: upgrade openssl to 1.0.2g (Ben Noordhuis) [#5507](https://github.com/nodejs/node/pull/5507) - - - Windows 32-bit Installer: https://nodejs.org/dist/v4.3.2/node-v4.3.2-x86.msi
    Windows 64-bit Installer: https://nodejs.org/dist/v4.3.2/node-v4.3.2-x64.msi
    Windows 32-bit Binary: https://nodejs.org/dist/v4.3.2/win-x86/node.exe
    diff --git a/locale/en/blog/release/v4.4.0.md b/locale/en/blog/release/v4.4.0.md index a60f8fc47b90b..109e285d5f136 100644 --- a/locale/en/blog/release/v4.4.0.md +++ b/locale/en/blog/release/v4.4.0.md @@ -261,8 +261,6 @@ Notable semver patch changes include: * [[`01006392cf`](https://github.com/nodejs/node/commit/01006392cf)] - **tools,doc**: fix linting errors (Rich Trott) [#5161](https://github.com/nodejs/node/pull/5161) * [[`57a5f8731a`](https://github.com/nodejs/node/commit/57a5f8731a)] - **url**: change scoping of variables with let (Kári Tristan Helgason) [#4867](https://github.com/nodejs/node/pull/4867) - - Windows 32-bit Installer: https://nodejs.org/dist/v4.4.0/node-v4.4.0-x86.msi
    Windows 64-bit Installer: https://nodejs.org/dist/v4.4.0/node-v4.4.0-x64.msi
    Windows 32-bit Binary: https://nodejs.org/dist/v4.4.0/win-x86/node.exe
    diff --git a/locale/en/blog/release/v4.4.1.md b/locale/en/blog/release/v4.4.1.md index 6dd0929719b40..a2e2afd94f91e 100644 --- a/locale/en/blog/release/v4.4.1.md +++ b/locale/en/blog/release/v4.4.1.md @@ -137,8 +137,6 @@ author: Myles Borins * [[`dff7091fce`](https://github.com/nodejs/node/commit/dff7091fce)] - **url**: group slashed protocols by protocol name (nettofarah) [#5380](https://github.com/nodejs/node/pull/5380) * [[`0e97a3ea51`](https://github.com/nodejs/node/commit/0e97a3ea51)] - **win,build**: support Visual C++ Build Tools 2015 (João Reis) [#5627](https://github.com/nodejs/node/pull/5627) - - Windows 32-bit Installer: https://nodejs.org/dist/v4.4.1/node-v4.4.1-x86.msi
    Windows 64-bit Installer: https://nodejs.org/dist/v4.4.1/node-v4.4.1-x64.msi
    Windows 32-bit Binary: https://nodejs.org/dist/v4.4.1/win-x86/node.exe
    diff --git a/locale/en/blog/release/v4.4.2.md b/locale/en/blog/release/v4.4.2.md index 9c4dafb649095..00bd92b78a1b8 100644 --- a/locale/en/blog/release/v4.4.2.md +++ b/locale/en/blog/release/v4.4.2.md @@ -66,8 +66,6 @@ This release includes a security update for npm. For more details you can read [ * [[`f209effe8b`](https://github.com/nodejs/node/commit/f209effe8b)] - **test**: remove timer from test-http-1.0 (Santiago Gimeno) [#5129](https://github.com/nodejs/node/pull/5129) * [[`3a901b0e3e`](https://github.com/nodejs/node/commit/3a901b0e3e)] - **tools**: remove unused imports (Sakthipriyan Vairamani) [#5765](https://github.com/nodejs/node/pull/5765) - - Windows 32-bit Installer: https://nodejs.org/dist/v4.4.2/node-v4.4.2-x86.msi
    Windows 64-bit Installer: https://nodejs.org/dist/v4.4.2/node-v4.4.2-x64.msi
    Windows 32-bit Binary: https://nodejs.org/dist/v4.4.2/win-x86/node.exe
    diff --git a/locale/en/blog/release/v4.4.3.md b/locale/en/blog/release/v4.4.3.md index be1304ec020a7..2479db50a0d22 100644 --- a/locale/en/blog/release/v4.4.3.md +++ b/locale/en/blog/release/v4.4.3.md @@ -72,8 +72,6 @@ author: Myles Borins * [[`6f0bd64122`](https://github.com/nodejs/node/commit/6f0bd64122)] - **tools,doc**: fix incomplete json produced by doctool (firedfox) [#5966](https://github.com/nodejs/node/pull/5966) * [[`f7eb48302c`](https://github.com/nodejs/node/commit/f7eb48302c)] - **win,build**: build and test add-ons on test-ci (Bogdan Lobor) [#5886](https://github.com/nodejs/node/pull/5886) - - Windows 32-bit Installer: https://nodejs.org/dist/v4.4.3/node-v4.4.3-x86.msi
    Windows 64-bit Installer: https://nodejs.org/dist/v4.4.3/node-v4.4.3-x64.msi
    Windows 32-bit Binary: https://nodejs.org/dist/v4.4.3/win-x86/node.exe
    diff --git a/locale/en/blog/release/v4.4.4.md b/locale/en/blog/release/v4.4.4.md index 0039109ff048f..d4649d2a942e7 100644 --- a/locale/en/blog/release/v4.4.4.md +++ b/locale/en/blog/release/v4.4.4.md @@ -26,8 +26,6 @@ author: Myles Borins * [[`2dfeb01213`](https://github.com/nodejs/node/commit/2dfeb01213)] - **deps**: copy all openssl header files to include dir (Shigeki Ohtsu) [#6551](https://github.com/nodejs/node/pull/6551) * [[`72f9952516`](https://github.com/nodejs/node/commit/72f9952516)] - **deps**: upgrade openssl sources to 1.0.2h (Shigeki Ohtsu) [#6551](https://github.com/nodejs/node/pull/6551) - - Windows 32-bit Installer: https://nodejs.org/dist/v4.4.4/node-v4.4.4-x86.msi
    Windows 64-bit Installer: https://nodejs.org/dist/v4.4.4/node-v4.4.4-x64.msi
    Windows 32-bit Binary: https://nodejs.org/dist/v4.4.4/win-x86/node.exe
    diff --git a/locale/en/blog/release/v4.4.5.md b/locale/en/blog/release/v4.4.5.md index 0d736bec3288a..585e6aac196b6 100644 --- a/locale/en/blog/release/v4.4.5.md +++ b/locale/en/blog/release/v4.4.5.md @@ -97,8 +97,6 @@ author: Myles Borins * [[`c893cd33d1`](https://github.com/nodejs/node/commit/c893cd33d1)] - **tools,doc**: parse types in braces everywhere (Alexander Makarenko) [#5329](https://github.com/nodejs/node/pull/5329) * [[`48684af55f`](https://github.com/nodejs/node/commit/48684af55f)] - **zlib**: fix use after null when calling .close (James Lal) [#5982](https://github.com/nodejs/node/pull/5982) - - Windows 32-bit Installer: https://nodejs.org/dist/v4.4.5/node-v4.4.5-x86.msi
    Windows 64-bit Installer: https://nodejs.org/dist/v4.4.5/node-v4.4.5-x64.msi
    Windows 32-bit Binary: https://nodejs.org/dist/v4.4.5/win-x86/node.exe
    diff --git a/locale/en/blog/release/v4.4.6.md b/locale/en/blog/release/v4.4.6.md index 495d46e2def2f..b19c3958d05c9 100644 --- a/locale/en/blog/release/v4.4.6.md +++ b/locale/en/blog/release/v4.4.6.md @@ -18,7 +18,6 @@ This release is specifically related to a Buffer overflow vulnerability discover * [[`134c3b3977`](https://github.com/nodejs/node/commit/134c3b3977)] - **deps**: backport 3a9bfec from v8 upstream (Ben Noordhuis) [nodejs/node-private#38](https://github.com/nodejs/node-private/pull/38) - Windows 32-bit Installer: https://nodejs.org/dist/v4.4.6/node-v4.4.6-x86.msi
    Windows 64-bit Installer: https://nodejs.org/dist/v4.4.6/node-v4.4.6-x64.msi
    Windows 32-bit Binary: https://nodejs.org/dist/v4.4.6/win-x86/node.exe
    diff --git a/locale/en/blog/release/v4.4.7.md b/locale/en/blog/release/v4.4.7.md index a51f1ce2a3b07..a532e543038f9 100644 --- a/locale/en/blog/release/v4.4.7.md +++ b/locale/en/blog/release/v4.4.7.md @@ -114,7 +114,6 @@ author: Myles Borins * [[`0f6146c6c0`](https://github.com/nodejs/node/commit/0f6146c6c0)] - **tools**: add tests for the doctool (Ian Kronquist) [#6031](https://github.com/nodejs/node/pull/6031) * [[`cc3645cff3`](https://github.com/nodejs/node/commit/cc3645cff3)] - **tools**: lint for alignment of variable assignments (Rich Trott) [#6869](https://github.com/nodejs/node/pull/6869) - Windows 32-bit Installer: https://nodejs.org/dist/v4.4.7/node-v4.4.7-x86.msi
    Windows 64-bit Installer: https://nodejs.org/dist/v4.4.7/node-v4.4.7-x64.msi
    Windows 32-bit Binary: https://nodejs.org/dist/v4.4.7/win-x86/node.exe
    diff --git a/locale/en/blog/release/v5.0.0.md b/locale/en/blog/release/v5.0.0.md index 7646f8650addf..96b0e2cd4ed43 100644 --- a/locale/en/blog/release/v5.0.0.md +++ b/locale/en/blog/release/v5.0.0.md @@ -57,7 +57,6 @@ The release notes below are annotated with the main breaking changes that warran * `url.resolve` may transfer the auth portion of the url when resolving between two full hosts, see [#1435](https://github.com/nodejs/node/issues/1435). * Unicode characters in filesystem paths are not handled consistently across platforms or Node.js APIs. See [#2088](https://github.com/nodejs/node/issues/2088), [#3401](https://github.com/nodejs/node/issues/3401) and [#3519](https://github.com/nodejs/node/issues/3519). - ### Commits * [[`6a04cc0a43`](https://github.com/nodejs/node/commit/6a04cc0a43)] - **buffer**: fix value check for writeUInt{B,L}E (Trevor Norris) [#3500](https://github.com/nodejs/node/pull/3500) diff --git a/locale/en/blog/release/v5.1.0.md b/locale/en/blog/release/v5.1.0.md index e32e32e6f2427..4606f41d9a7be 100644 --- a/locale/en/blog/release/v5.1.0.md +++ b/locale/en/blog/release/v5.1.0.md @@ -169,8 +169,6 @@ author: Jeremiah Senkpiel * [[`33ffc62670`](https://github.com/nodejs/node/commit/33ffc62670)] - **zlib**: only apply drain listener if given callback (Craig Cavalier) [#3534](https://github.com/nodejs/node/pull/3534) * [[`d70deabf90`](https://github.com/nodejs/node/commit/d70deabf90)] - **zlib**: pass kind to recursive calls to flush (Myles Borins) [#3534](https://github.com/nodejs/node/pull/3534) - - Windows 32-bit Installer: https://nodejs.org/dist/v5.1.0/node-v5.1.0-x86.msi
    Windows 64-bit Installer: https://nodejs.org/dist/v5.1.0/node-v5.1.0-x64.msi
    Windows 32-bit Binary: https://nodejs.org/dist/v5.1.0/win-x86/node.exe
    diff --git a/locale/en/blog/release/v5.1.1.md b/locale/en/blog/release/v5.1.1.md index 62ed8fa5bc72f..0f1a6d2b57b26 100644 --- a/locale/en/blog/release/v5.1.1.md +++ b/locale/en/blog/release/v5.1.1.md @@ -33,8 +33,6 @@ author: Rod Vagg * [[`533881f889`](https://github.com/nodejs/node/commit/533881f889)] - **deps**: upgrade openssl sources to 1.0.2e (Shigeki Ohtsu) [#4134](https://github.com/nodejs/node/pull/4134) * [[`12e70fafd3`](https://github.com/nodejs/node/commit/12e70fafd3)] - **http**: fix pipeline regression (Fedor Indutny) - - Windows 32-bit Installer: https://nodejs.org/dist/v5.1.1/node-v5.1.1-x86.msi
    Windows 64-bit Installer: https://nodejs.org/dist/v5.1.1/node-v5.1.1-x64.msi
    Windows 32-bit Binary: https://nodejs.org/dist/v5.1.1/win-x86/node.exe
    diff --git a/locale/en/blog/release/v5.10.0.md b/locale/en/blog/release/v5.10.0.md index 6b91230c699a4..56bde56b7ff33 100644 --- a/locale/en/blog/release/v5.10.0.md +++ b/locale/en/blog/release/v5.10.0.md @@ -89,8 +89,6 @@ written by [Forrest L Norvell](https://github.com/othiym23) from npm. * [[`77bed269ad`](https://github.com/nodejs/node/commit/77bed269ad)] - **win,build**: build and test add-ons on test-ci (Bogdan Lobor) [#5886](https://github.com/nodejs/node/pull/5886) * [[`afcd276ecc`](https://github.com/nodejs/node/commit/afcd276ecc)] - **zlib**: Fix handling of gzip magic bytes mid-file (Anna Henningsen) [#5863](https://github.com/nodejs/node/pull/5863) - - Windows 32-bit Installer: https://nodejs.org/dist/v5.10.0/node-v5.10.0-x86.msi
    Windows 64-bit Installer: https://nodejs.org/dist/v5.10.0/node-v5.10.0-x64.msi
    Windows 32-bit Binary: https://nodejs.org/dist/v5.10.0/win-x86/node.exe
    diff --git a/locale/en/blog/release/v5.10.1.md b/locale/en/blog/release/v5.10.1.md index d3e6a25464bbe..346a4b1b679c5 100644 --- a/locale/en/blog/release/v5.10.1.md +++ b/locale/en/blog/release/v5.10.1.md @@ -49,8 +49,6 @@ author: Myles Borins * [[`50a062e691`](https://github.com/nodejs/node/commit/50a062e691)] - **tools**: remove obsolete lint config file (Rich Trott) [#5959](https://github.com/nodejs/node/pull/5959) * [[`7491fdcfe9`](https://github.com/nodejs/node/commit/7491fdcfe9)] - **tools**: remove disabling of already-disabled rule (Rich Trott) [#6013](https://github.com/nodejs/node/pull/6013) - - Windows 32-bit Installer: https://nodejs.org/dist/v5.10.1/node-v5.10.1-x86.msi
    Windows 64-bit Installer: https://nodejs.org/dist/v5.10.1/node-v5.10.1-x64.msi
    Windows 32-bit Binary: https://nodejs.org/dist/v5.10.1/win-x86/node.exe
    diff --git a/locale/en/blog/release/v5.11.0.md b/locale/en/blog/release/v5.11.0.md index db01b465e52f7..dcc487d8b0c4d 100644 --- a/locale/en/blog/release/v5.11.0.md +++ b/locale/en/blog/release/v5.11.0.md @@ -130,8 +130,6 @@ author: Myles Borins * [[`2c23e14d5d`](https://github.com/nodejs/node/commit/2c23e14d5d)] - **(SEMVER-MINOR)** **zlib**: detect gzip files when using unzip* (Anna Henningsen) [#5884](https://github.com/nodejs/node/pull/5884) * [[`61167c3e23`](https://github.com/nodejs/node/commit/61167c3e23)] - **zlib**: fix gzip member head/buffer boundary issue (Anna Henningsen) [#5973](https://github.com/nodejs/node/pull/5973) - - Windows 32-bit Installer: https://nodejs.org/dist/v5.11.0/node-v5.11.0-x86.msi
    Windows 64-bit Installer: https://nodejs.org/dist/v5.11.0/node-v5.11.0-x64.msi
    Windows 32-bit Binary: https://nodejs.org/dist/v5.11.0/win-x86/node.exe
    diff --git a/locale/en/blog/release/v5.11.1.md b/locale/en/blog/release/v5.11.1.md index b517d5c75c897..cf714a5f851f8 100644 --- a/locale/en/blog/release/v5.11.1.md +++ b/locale/en/blog/release/v5.11.1.md @@ -28,8 +28,6 @@ Please see our [blog post](https://nodejs.org/en/blog/vulnerability/openssl-may- * [[`c1ddefdd79`](https://github.com/nodejs/node/commit/c1ddefdd79)] - **openssl**: fix keypress requirement in apps on win32 (Shigeki Ohtsu) [#1389](https://github.com/nodejs/node/pull/1389) * [[`bec5d50f1e`](https://github.com/nodejs/node/commit/bec5d50f1e)] - **test**: fix alpn tests for openssl1.0.2h (Shigeki Ohtsu) [#6552](https://github.com/nodejs/node/pull/6552) - - Windows 32-bit Installer: https://nodejs.org/dist/v5.11.1/node-v5.11.1-x86.msi
    Windows 64-bit Installer: https://nodejs.org/dist/v5.11.1/node-v5.11.1-x64.msi
    Windows 32-bit Binary: https://nodejs.org/dist/v5.11.1/win-x86/node.exe
    diff --git a/locale/en/blog/release/v5.12.0.md b/locale/en/blog/release/v5.12.0.md index 713e6955443ef..32b4d1c5933c9 100644 --- a/locale/en/blog/release/v5.12.0.md +++ b/locale/en/blog/release/v5.12.0.md @@ -26,7 +26,6 @@ This is a security release. All Node.js users should consult the security releas * [[`2ebeb82852`](https://github.com/nodejs/node/commit/2ebeb82852)] - **test**: fix test-net-* error code check for getaddrinfo(3) (Natanael Copa) [#5099](https://github.com/nodejs/node/pull/5099) * [[`03d36aea4f`](https://github.com/nodejs/node/commit/03d36aea4f)] - **(SEMVER-MINOR)** **test**: add buffer testcase for resetting kZeroFill (Сковорода Никита Андреевич) [#7169](https://github.com/nodejs/node/pull/7169) - Windows 32-bit Installer: https://nodejs.org/dist/v5.12.0/node-v5.12.0-x86.msi
    Windows 64-bit Installer: https://nodejs.org/dist/v5.12.0/node-v5.12.0-x64.msi
    Windows 32-bit Binary: https://nodejs.org/dist/v5.12.0/win-x86/node.exe
    diff --git a/locale/en/blog/release/v5.2.0.md b/locale/en/blog/release/v5.2.0.md index 0e8bf53db10ed..33566d52ff23b 100644 --- a/locale/en/blog/release/v5.2.0.md +++ b/locale/en/blog/release/v5.2.0.md @@ -134,8 +134,6 @@ author: Rod Vagg * [[`e68ea16c32`](https://github.com/nodejs/node/commit/e68ea16c32)] - **util**: add decorateErrorStack() (cjihrig) [#4013](https://github.com/nodejs/node/pull/4013) * [[`c584c3e08f`](https://github.com/nodejs/node/commit/c584c3e08f)] - **util,src**: allow lookup of hidden values (cjihrig) [#3988](https://github.com/nodejs/node/pull/3988) - - Windows 32-bit Installer: https://nodejs.org/dist/v5.2.0/node-v5.2.0-x86.msi
    Windows 64-bit Installer: https://nodejs.org/dist/v5.2.0/node-v5.2.0-x64.msi
    Windows 32-bit Binary: https://nodejs.org/dist/v5.2.0/win-x86/node.exe
    diff --git a/locale/en/blog/release/v5.3.0.md b/locale/en/blog/release/v5.3.0.md index 4745d8407a88a..f48aca9a8ff77 100644 --- a/locale/en/blog/release/v5.3.0.md +++ b/locale/en/blog/release/v5.3.0.md @@ -21,7 +21,6 @@ author: Colin Ihrig * **deps**: - Upgrade libuv to 1.8.0. (Saúl Ibarra Corretgé) [#4276](https://github.com/nodejs/node/pull/4276). - ### Known issues * Surrogate pair in REPL can freeze terminal. [#690](https://github.com/nodejs/node/issues/690) @@ -83,8 +82,6 @@ author: Colin Ihrig * [[`d63cceeb10`](https://github.com/nodejs/node/commit/d63cceeb10)] - **tools**: add .editorconfig (ronkorving) [#2993](https://github.com/nodejs/node/pull/2993) * [[`4b267df93e`](https://github.com/nodejs/node/commit/4b267df93e)] - **udp**: remove a needless instanceof Buffer check (ronkorving) [#4301](https://github.com/nodejs/node/pull/4301) - - Windows 32-bit Installer: https://nodejs.org/dist/v5.3.0/node-v5.3.0-x86.msi
    Windows 64-bit Installer: https://nodejs.org/dist/v5.3.0/node-v5.3.0-x64.msi
    Windows 32-bit Binary: https://nodejs.org/dist/v5.3.0/win-x86/node.exe
    diff --git a/locale/en/blog/release/v5.4.0.md b/locale/en/blog/release/v5.4.0.md index 330ed6d8e1767..4f80cf91a8c08 100644 --- a/locale/en/blog/release/v5.4.0.md +++ b/locale/en/blog/release/v5.4.0.md @@ -129,8 +129,6 @@ author: Jeremiah Senkpiel * [[`14a947fc70`](https://github.com/nodejs/node/commit/14a947fc70)] - **tools**: run tick processor without forking (Matt Loring) [#4224](https://github.com/nodejs/node/pull/4224) * [[`8039ca06eb`](https://github.com/nodejs/node/commit/8039ca06eb)] - **util**: faster arrayToHash (Jackson Tian) [#3964](https://github.com/nodejs/node/pull/3964) - - Windows 32-bit Installer: https://nodejs.org/dist/v5.4.0/node-v5.4.0-x86.msi
    Windows 64-bit Installer: https://nodejs.org/dist/v5.4.0/node-v5.4.0-x64.msi
    Windows 32-bit Binary: https://nodejs.org/dist/v5.4.0/win-x86/node.exe
    diff --git a/locale/en/blog/release/v5.4.1.md b/locale/en/blog/release/v5.4.1.md index 89b710979ea13..3f380dc6d1481 100644 --- a/locale/en/blog/release/v5.4.1.md +++ b/locale/en/blog/release/v5.4.1.md @@ -52,8 +52,6 @@ author: Myles Borins * [[`6f9a96f497`](https://github.com/nodejs/node/commit/6f9a96f497)] - **test**: fix flaky unrefed timers test (Rich Trott) [#4599](https://github.com/nodejs/node/pull/4599) * [[`b70eec8f7b`](https://github.com/nodejs/node/commit/b70eec8f7b)] - **tls_legacy**: do not read on OpenSSL's stack (Fedor Indutny) [#4624](https://github.com/nodejs/node/pull/4624) - - Windows 32-bit Installer: https://nodejs.org/dist/v5.4.1/node-v5.4.1-x86.msi
    Windows 64-bit Installer: https://nodejs.org/dist/v5.4.1/node-v5.4.1-x64.msi
    Windows 32-bit Binary: https://nodejs.org/dist/v5.4.1/win-x86/node.exe
    diff --git a/locale/en/blog/release/v5.5.0.md b/locale/en/blog/release/v5.5.0.md index df91a58ae6050..f15045cf91635 100644 --- a/locale/en/blog/release/v5.5.0.md +++ b/locale/en/blog/release/v5.5.0.md @@ -90,8 +90,6 @@ author: Evan Lucas * [[`aba3cc834e`](https://github.com/nodejs/node/commit/aba3cc834e)] - **tools**: fix license-builder.sh for ICU (Richard Lau) [#4762](https://github.com/nodejs/node/pull/4762) * [[`5f57005ec9`](https://github.com/nodejs/node/commit/5f57005ec9)] - **(SEMVER-MINOR)** **v8,src**: expose statistics about heap spaces (Ben Ripkens) [#4463](https://github.com/nodejs/node/pull/4463) - - Windows 32-bit Installer: https://nodejs.org/dist/v5.5.0/node-v5.5.0-x86.msi
    Windows 64-bit Installer: https://nodejs.org/dist/v5.5.0/node-v5.5.0-x64.msi
    Windows 32-bit Binary: https://nodejs.org/dist/v5.5.0/win-x86/node.exe
    diff --git a/locale/en/blog/release/v5.6.0.md b/locale/en/blog/release/v5.6.0.md index 861e41a048ab8..18104f7241857 100644 --- a/locale/en/blog/release/v5.6.0.md +++ b/locale/en/blog/release/v5.6.0.md @@ -163,8 +163,6 @@ This is an important security release. For full details see https://nodejs.org/e * [[`386ad7e0b5`](https://github.com/nodejs/node/commit/386ad7e0b5)] - **tools**: fix setting path containing an ampersand (Brian White) [#4804](https://github.com/nodejs/node/pull/4804) * [[`e415eb27e5`](https://github.com/nodejs/node/commit/e415eb27e5)] - **url**: change scoping of variables with let (Kári Tristan Helgason) [#4867](https://github.com/nodejs/node/pull/4867) - - Windows 32-bit Installer: https://nodejs.org/dist/v5.6.0/node-v5.6.0-x86.msi
    Windows 64-bit Installer: https://nodejs.org/dist/v5.6.0/node-v5.6.0-x64.msi
    Windows 32-bit Binary: https://nodejs.org/dist/v5.6.0/win-x86/node.exe
    diff --git a/locale/en/blog/release/v5.7.0.md b/locale/en/blog/release/v5.7.0.md index 446f5462b95ec..86e38945a7914 100644 --- a/locale/en/blog/release/v5.7.0.md +++ b/locale/en/blog/release/v5.7.0.md @@ -141,8 +141,6 @@ author: Rod Vagg * [[`6c8378b15b`](https://github.com/nodejs/node/commit/6c8378b15b)] - **vm**: fix `produceCachedData` (Jiho Choi) [#5343](https://github.com/nodejs/node/pull/5343) * [[`d1cacb814f`](https://github.com/nodejs/node/commit/d1cacb814f)] - **(SEMVER-MINOR)** **vm**: introduce `cachedData`/`produceCachedData` (Fedor Indutny) [#4777](https://github.com/nodejs/node/pull/4777) - - Windows 32-bit Installer: https://nodejs.org/dist/v5.7.0/node-v5.7.0-x86.msi
    Windows 64-bit Installer: https://nodejs.org/dist/v5.7.0/node-v5.7.0-x64.msi
    Windows 32-bit Binary: https://nodejs.org/dist/v5.7.0/win-x86/node.exe
    diff --git a/locale/en/blog/release/v5.7.1.md b/locale/en/blog/release/v5.7.1.md index e99c909298d94..347bbdce809e5 100644 --- a/locale/en/blog/release/v5.7.1.md +++ b/locale/en/blog/release/v5.7.1.md @@ -100,8 +100,6 @@ author: Jeremiah Senkpiel * [[`9424fa5732`](https://github.com/nodejs/node/commit/9424fa5732)] - **url**: group slashed protocols by protocol name (nettofarah) [#5380](https://github.com/nodejs/node/pull/5380) * [[`dfe45f13e7`](https://github.com/nodejs/node/commit/dfe45f13e7)] - **url**: fix off-by-one error with parse() (Brian White) [#5394](https://github.com/nodejs/node/pull/5394) - - Windows 32-bit Installer: https://nodejs.org/dist/v5.7.1/node-v5.7.1-x86.msi
    Windows 64-bit Installer: https://nodejs.org/dist/v5.7.1/node-v5.7.1-x64.msi
    Windows 32-bit Binary: https://nodejs.org/dist/v5.7.1/win-x86/node.exe
    diff --git a/locale/en/blog/release/v5.8.0.md b/locale/en/blog/release/v5.8.0.md index f33e16391c31e..bddaffcc058c6 100644 --- a/locale/en/blog/release/v5.8.0.md +++ b/locale/en/blog/release/v5.8.0.md @@ -53,8 +53,6 @@ author: Jeremiah Senkpiel * [[`971edde0cb`](https://github.com/nodejs/node/commit/971edde0cb)] - **util**: improve format() performance further (Brian White) [#5360](https://github.com/nodejs/node/pull/5360) * [[`c32d460747`](https://github.com/nodejs/node/commit/c32d460747)] - **util**: improve util.format performance (Evan Lucas) [#5360](https://github.com/nodejs/node/pull/5360) - - Windows 32-bit Installer: https://nodejs.org/dist/v5.8.0/node-v5.8.0-x86.msi
    Windows 64-bit Installer: https://nodejs.org/dist/v5.8.0/node-v5.8.0-x64.msi
    Windows 32-bit Binary: https://nodejs.org/dist/v5.8.0/win-x86/node.exe
    diff --git a/locale/en/blog/release/v5.9.0.md b/locale/en/blog/release/v5.9.0.md index 9406909f0cbf0..474bbf74041d6 100644 --- a/locale/en/blog/release/v5.9.0.md +++ b/locale/en/blog/release/v5.9.0.md @@ -83,8 +83,6 @@ https://github.com/nodejs/node/pull/5120 * [[`0b545fb3f8`](https://github.com/nodejs/node/commit/0b545fb3f8)] - **win,build**: support Visual C++ Build Tools 2015 (João Reis) [#5627](https://github.com/nodejs/node/pull/5627) * [[`ef774ff9a8`](https://github.com/nodejs/node/commit/ef774ff9a8)] - **(SEMVER-MINOR)** **zlib**: add support for concatenated members (Kári Tristan Helgason) [#5120](https://github.com/nodejs/node/pull/5120) - - Windows 32-bit Installer: https://nodejs.org/dist/v5.9.0/node-v5.9.0-x86.msi
    Windows 64-bit Installer: https://nodejs.org/dist/v5.9.0/node-v5.9.0-x64.msi
    Windows 32-bit Binary: https://nodejs.org/dist/v5.9.0/win-x86/node.exe
    diff --git a/locale/en/blog/release/v5.9.1.md b/locale/en/blog/release/v5.9.1.md index 3ffc268619697..4ec8cbbcd3e4f 100644 --- a/locale/en/blog/release/v5.9.1.md +++ b/locale/en/blog/release/v5.9.1.md @@ -62,8 +62,6 @@ author: Jeremiah Senkpiel * [[`d3654d80f3`](https://github.com/nodejs/node/commit/d3654d80f3)] - **timers**: improve setImmediate() performance (Brian White) [#4169](https://github.com/nodejs/node/pull/4169) * [[`b1a4870200`](https://github.com/nodejs/node/commit/b1a4870200)] - **tools**: remove unused imports (Sakthipriyan Vairamani) [#5765](https://github.com/nodejs/node/pull/5765) - - Windows 32-bit Installer: https://nodejs.org/dist/v5.9.1/node-v5.9.1-x86.msi
    Windows 64-bit Installer: https://nodejs.org/dist/v5.9.1/node-v5.9.1-x64.msi
    Windows 32-bit Binary: https://nodejs.org/dist/v5.9.1/win-x86/node.exe
    diff --git a/locale/en/blog/release/v6.0.0.md b/locale/en/blog/release/v6.0.0.md index e45bd6f7ce249..184ad3ce761b9 100644 --- a/locale/en/blog/release/v6.0.0.md +++ b/locale/en/blog/release/v6.0.0.md @@ -172,7 +172,6 @@ v5.0.0 release. [#5883](https://github.com/nodejs/node/pull/5883) and [#5707](https://github.com/nodejs/node/pull/5707). - ### Commits Semver-major Changes since v5.0.0 @@ -267,7 +266,6 @@ Semver-major Changes since v5.0.0 **(SEMVER-MAJOR)** **zlib**: fix gzip member head/buffer boundary issue (Anna Henningsen) [#5883](https://github.com/nodejs/node/pull/5883) * [[`8b43d3f52d`](https://github.com/nodejs/node/commit/8b43d3f52d)] - **(SEMVER-MAJOR)** **zlib**: do not emit event on *Sync() methods (Rich Trott) [#5707](https://github.com/nodejs/node/pull/5707) - Semver-minor and patch commits since v5.11.0 * [[`6c1e5ad3ab`](https://github.com/nodejs/node/commit/6c1e5ad3ab)] - **(SEMVER-MINOR)** **buffer**: add Buffer.prototype.lastIndexOf() (dcposch@dcpos.ch) [#4846](https://github.com/nodejs/node/pull/4846) @@ -308,8 +306,6 @@ Semver-minor and patch commits since v5.11.0 * [[`e84c69310f`](https://github.com/nodejs/node/commit/e84c69310f)] - **tools**: enforce deepStrictEqual over deepEqual (Rich Trott) [#6213](https://github.com/nodejs/node/pull/6213) * [[`7940ecfa00`](https://github.com/nodejs/node/commit/7940ecfa00)] - **v8**: warn in Template::Set() on improper use (Ben Noordhuis) [#6277](https://github.com/nodejs/node/pull/6277) - - Windows 32-bit Installer: https://nodejs.org/dist/v6.0.0/node-v6.0.0-x86.msi
    Windows 64-bit Installer: https://nodejs.org/dist/v6.0.0/node-v6.0.0-x64.msi
    Windows 32-bit Binary: https://nodejs.org/dist/v6.0.0/win-x86/node.exe
    diff --git a/locale/en/blog/release/v6.1.0.md b/locale/en/blog/release/v6.1.0.md index 85a1aff614788..1c3aa66750221 100644 --- a/locale/en/blog/release/v6.1.0.md +++ b/locale/en/blog/release/v6.1.0.md @@ -89,8 +89,6 @@ Please see our [blog post](https://nodejs.org/en/blog/vulnerability/openssl-may- * [[`91ab769940`](https://github.com/nodejs/node/commit/91ab769940)] - **(SEMVER-MINOR)** **util**: truncate inspect array and typed array (James M Snell) [#6334](https://github.com/nodejs/node/pull/6334) * [[`0bca959617`](https://github.com/nodejs/node/commit/0bca959617)] - **(SEMVER-MINOR)** **util**: fix inspecting of proxy objects (James M Snell) [#6465](https://github.com/nodejs/node/pull/6465) - - Windows 32-bit Installer: https://nodejs.org/dist/v6.1.0/node-v6.1.0-x86.msi
    Windows 64-bit Installer: https://nodejs.org/dist/v6.1.0/node-v6.1.0-x64.msi
    Windows 32-bit Binary: https://nodejs.org/dist/v6.1.0/win-x86/node.exe
    diff --git a/locale/en/blog/release/v6.10.0.md b/locale/en/blog/release/v6.10.0.md index 8db2c76752468..50549c8bf7b0c 100644 --- a/locale/en/blog/release/v6.10.0.md +++ b/locale/en/blog/release/v6.10.0.md @@ -17,7 +17,6 @@ The SEMVER-MINOR changes include: * **process**: add `process.memoryUsage.external` (Fedor Indutny) [#9587](https://github.com/nodejs/node/pull/9587) * **src**: add wrapper for process.emitWarning() (Sam Roberts) [#9139](https://github.com/nodejs/node/pull/9139) - Notable SEMVER-PATCH changes include: * **fs**: cache non-symlinks in realpathSync. (Jeremy Yallop) [#10253](https://github.com/nodejs/node/pull/10253) diff --git a/locale/en/blog/release/v6.2.0.md b/locale/en/blog/release/v6.2.0.md index cec5a0b027e9f..db4a7f2a06066 100644 --- a/locale/en/blog/release/v6.2.0.md +++ b/locale/en/blog/release/v6.2.0.md @@ -151,7 +151,6 @@ running in big endian mode in addition to the existing 64-bit binaries for runni * [[`6d1527bb37`](https://github.com/nodejs/node/commit/6d1527bb37)] - **util**: fix invalid date output with util.inspect (Rumkin) [#6504](https://github.com/nodejs/node/pull/6504) * [[`1d6c17efd7`](https://github.com/nodejs/node/commit/1d6c17efd7)] - **util**: adhere to `noDeprecation` set at runtime (Anna Henningsen) [#6683](https://github.com/nodejs/node/pull/6683) - Windows 32-bit Installer: https://nodejs.org/dist/v6.2.0/node-v6.2.0-x86.msi
    Windows 64-bit Installer: https://nodejs.org/dist/v6.2.0/node-v6.2.0-x64.msi
    Windows 32-bit Binary: https://nodejs.org/dist/v6.2.0/win-x86/node.exe
    diff --git a/locale/en/blog/release/v6.2.1.md b/locale/en/blog/release/v6.2.1.md index 352486632ee55..ea481d70c02ad 100644 --- a/locale/en/blog/release/v6.2.1.md +++ b/locale/en/blog/release/v6.2.1.md @@ -157,7 +157,6 @@ author: Rod Vagg * [[`1e26b82ce4`](https://github.com/nodejs/node/commit/1e26b82ce4)] - **zlib**: release callback and buffer after processing (Matt Lavin) [#6955](https://github.com/nodejs/node/pull/6955) * [[`64415564de`](https://github.com/nodejs/node/commit/64415564de)] - **zlib**: remove `_closed` in source (Anna Henningsen) [#6574](https://github.com/nodejs/node/pull/6574) - Windows 32-bit Installer: https://nodejs.org/dist/v6.2.1/node-v6.2.1-x86.msi
    Windows 64-bit Installer: https://nodejs.org/dist/v6.2.1/node-v6.2.1-x64.msi
    Windows 32-bit Binary: https://nodejs.org/dist/v6.2.1/win-x86/node.exe
    diff --git a/locale/en/blog/release/v6.2.2.md b/locale/en/blog/release/v6.2.2.md index 894b304ee2dd5..e39d1150b114a 100644 --- a/locale/en/blog/release/v6.2.2.md +++ b/locale/en/blog/release/v6.2.2.md @@ -81,7 +81,6 @@ author: Evan Lucas * [[`9545c41cba`](https://github.com/nodejs/node/commit/9545c41cba)] - **tools**: fix license builder to work with icu-small (Myles Borins) [#7119](https://github.com/nodejs/node/pull/7119) * [[`6562c9fc75`](https://github.com/nodejs/node/commit/6562c9fc75)] - **tools,doc**: add example usage for REPLACEME tag (Anna Henningsen) [#6864](https://github.com/nodejs/node/pull/6864) - Windows 32-bit Installer: https://nodejs.org/dist/v6.2.2/node-v6.2.2-x86.msi
    Windows 64-bit Installer: https://nodejs.org/dist/v6.2.2/node-v6.2.2-x64.msi
    Windows 32-bit Binary: https://nodejs.org/dist/v6.2.2/win-x86/node.exe
    diff --git a/locale/en/blog/release/v6.3.0.md b/locale/en/blog/release/v6.3.0.md index 48afbb7697cd4..ad256fe26686b 100644 --- a/locale/en/blog/release/v6.3.0.md +++ b/locale/en/blog/release/v6.3.0.md @@ -186,7 +186,6 @@ author: Jeremiah Senkpiel * [[`55b87c0238`](https://github.com/nodejs/node/commit/55b87c0238)] - **vm**: test for abort condition of current invocation (Anna Henningsen) [#7373](https://github.com/nodejs/node/pull/7373) * [[`d049919e7d`](https://github.com/nodejs/node/commit/d049919e7d)] - **(SEMVER-MINOR)** **vm**: add ability to break on sigint/ctrl+c (Anna Henningsen) [#6635](https://github.com/nodejs/node/pull/6635) - Windows 32-bit Installer: https://nodejs.org/dist/v6.3.0/node-v6.3.0-x86.msi
    Windows 64-bit Installer: https://nodejs.org/dist/v6.3.0/node-v6.3.0-x64.msi
    Windows 32-bit Binary: https://nodejs.org/dist/v6.3.0/win-x86/node.exe
    diff --git a/locale/en/blog/release/v6.3.1.md b/locale/en/blog/release/v6.3.1.md index b81642f013511..7ed25d851c43d 100644 --- a/locale/en/blog/release/v6.3.1.md +++ b/locale/en/blog/release/v6.3.1.md @@ -106,7 +106,6 @@ author: Evan Lucas * [[`fa99dadda4`](https://github.com/nodejs/node/commit/fa99dadda4)] - **tools**: remove unnecessary imports and assignments (Sakthipriyan Vairamani) [#7483](https://github.com/nodejs/node/pull/7483) * [[`0858e620e9`](https://github.com/nodejs/node/commit/0858e620e9)] - **util**: inspect boxed symbols like other primitives (Anna Henningsen) [#7641](https://github.com/nodejs/node/pull/7641) - Windows 32-bit Installer: https://nodejs.org/dist/v6.3.1/node-v6.3.1-x86.msi
    Windows 64-bit Installer: https://nodejs.org/dist/v6.3.1/node-v6.3.1-x64.msi
    Windows 32-bit Binary: https://nodejs.org/dist/v6.3.1/win-x86/node.exe
    diff --git a/locale/en/blog/vulnerability/august-2018-security-releases.md b/locale/en/blog/vulnerability/august-2018-security-releases.md index dd48ff94a09f1..e0cc9c1a493cc 100644 --- a/locale/en/blog/vulnerability/august-2018-security-releases.md +++ b/locale/en/blog/vulnerability/august-2018-security-releases.md @@ -125,4 +125,3 @@ The current Node.js security policy can be found at https://nodejs.org/en/securi Please contact security@nodejs.org if you wish to report a vulnerability in Node.js. Subscribe to the low-volume announcement-only nodejs-sec mailing list at https://groups.google.com/forum/#!forum/nodejs-sec to stay up to date on security vulnerabilities and security-related releases of Node.js and the projects maintained in the [nodejs GitHub organization](https://github.com/nodejs/). - diff --git a/locale/en/blog/vulnerability/december-2015-security-releases.md b/locale/en/blog/vulnerability/december-2015-security-releases.md index 7a8521f6adf1c..8e528fb1de9dd 100644 --- a/locale/en/blog/vulnerability/december-2015-security-releases.md +++ b/locale/en/blog/vulnerability/december-2015-security-releases.md @@ -56,5 +56,3 @@ OpenSSL v1.0.0 is used in Node.js v0.10.x and v0.12.x. OpenSSL v1.0.2 is used in * Versions 5.x of Node.js are **vulnerable**, please upgrade to [v5.1.1 (Stable)](/en/blog/release/v5.1.1/). **Note:** Node.js users are not considered vulnerable to the two additional announced OpenSSL vulnerabilities: CVE-2015-3195 "X509_ATTRIBUTE memory leak" and CVE-2015-3196 "Race condition handling PSK identify hint". However, fixes for these bugs are included with the new versions of OpenSSL bundled with the newly patched versions of Node.js. - - diff --git a/locale/en/blog/vulnerability/december-2017-security-releases.md b/locale/en/blog/vulnerability/december-2017-security-releases.md index d862e4b82993c..5a66312a114ca 100644 --- a/locale/en/blog/vulnerability/december-2017-security-releases.md +++ b/locale/en/blog/vulnerability/december-2017-security-releases.md @@ -51,7 +51,6 @@ The severity of this information disclosure vulnerability was low (due to the co Note that CVE 2017-3738 of OpenSSL-1.0.2 affected Node but it was low severity as described in [secadv-20171207.txt](https://www.openssl.org/news/secadv/20171207.txt). - ***Original post is included below*** ------------------------------------ diff --git a/locale/en/blog/vulnerability/july-2017-security-releases.md b/locale/en/blog/vulnerability/july-2017-security-releases.md index 9f234e70ac454..83d0884c577c6 100644 --- a/locale/en/blog/vulnerability/july-2017-security-releases.md +++ b/locale/en/blog/vulnerability/july-2017-security-releases.md @@ -67,8 +67,6 @@ A security vulnerability has been discovered in the c-ares library that is bundl This is a low severity defect and affects all active release lines (4.x, 6.x and 8.x) as well as the 7.x line. - - ***Original post is included below*** -------------------------------------- diff --git a/locale/en/blog/vulnerability/june-2018-security-releases.md b/locale/en/blog/vulnerability/june-2018-security-releases.md index 5951308418dd9..786ffc63e04f8 100644 --- a/locale/en/blog/vulnerability/june-2018-security-releases.md +++ b/locale/en/blog/vulnerability/june-2018-security-releases.md @@ -105,4 +105,3 @@ The current Node.js security policy can be found at https://nodejs.org/en/securi Please contact security@nodejs.org if you wish to report a vulnerability in Node.js. Subscribe to the low-volume announcement-only nodejs-sec mailing list at https://groups.google.com/forum/#!forum/nodejs-sec to stay up to date on security vulnerabilities and security-related releases of Node.js and the projects maintained in the [nodejs GitHub organization](https://github.com/nodejs/). - diff --git a/locale/en/blog/vulnerability/march-2018-security-releases.md b/locale/en/blog/vulnerability/march-2018-security-releases.md index 90454415b483d..20e30c9b8dc6c 100644 --- a/locale/en/blog/vulnerability/march-2018-security-releases.md +++ b/locale/en/blog/vulnerability/march-2018-security-releases.md @@ -146,4 +146,3 @@ The current Node.js security policy can be found at https://nodejs.org/en/securi Please contact security@nodejs.org if you wish to report a vulnerability in Node.js. Subscribe to the low-volume announcement-only nodejs-sec mailing list at https://groups.google.com/forum/#!forum/nodejs-sec to stay up to date on security vulnerabilities and security-related releases of Node.js and the projects maintained in the [nodejs GitHub organization](https://github.com/nodejs/). - diff --git a/locale/en/blog/vulnerability/oct-2017-dos.md b/locale/en/blog/vulnerability/oct-2017-dos.md index c9b512d16de8b..190e81a97a25c 100644 --- a/locale/en/blog/vulnerability/oct-2017-dos.md +++ b/locale/en/blog/vulnerability/oct-2017-dos.md @@ -40,7 +40,6 @@ This problem was resolved within Node.js by changing any request for a `windowBi This vulnerability has been assigned CVE-2017-14919. - ***Original post is included below*** -------------------------------------- diff --git a/locale/en/blog/vulnerability/openssl-and-low-severity-fixes-jan-2016.md b/locale/en/blog/vulnerability/openssl-and-low-severity-fixes-jan-2016.md index 035eaa21b7d92..30d26114f1347 100644 --- a/locale/en/blog/vulnerability/openssl-and-low-severity-fixes-jan-2016.md +++ b/locale/en/blog/vulnerability/openssl-and-low-severity-fixes-jan-2016.md @@ -109,4 +109,3 @@ The planned fixes include a backward-incompatible change that, under normal circ We apologise for any inconvenience this schedule change may cause. Please tune in to **nodejs-sec** (https://groups.google.com/forum/#!forum/nodejs-sec) to be notified of any further updates. - diff --git a/locale/en/blog/vulnerability/openssl-may-2016.md b/locale/en/blog/vulnerability/openssl-may-2016.md index 58b319254ad0e..a1ef8b0f07528 100644 --- a/locale/en/blog/vulnerability/openssl-may-2016.md +++ b/locale/en/blog/vulnerability/openssl-may-2016.md @@ -23,7 +23,6 @@ The OpenSSL project has [announced](https://mta.openssl.org/pipermail/openssl-an > ... issues that are of a lower risk than critical, perhaps due to affecting less common configurations, or which are less likely to be exploitable. - Node.js v0.10 and v0.12 both use OpenSSL v1.0.1 and Node.js v4, v5 and v6 use OpenSSL v1.0.2 and releases from [nodejs.org](https://nodejs.org/) and some other popular distribution sources are statically compiled. Therefore, all active release lines are impacted by this update. At this stage, due to embargo, it is uncertain the exact nature of these defects, nor what impact they will have on Node.js users, if any. We will proceed as follows: diff --git a/locale/en/blog/vulnerability/openssl-november-2017.md b/locale/en/blog/vulnerability/openssl-november-2017.md index 8d7eebe243395..80ee1d8e47d27 100644 --- a/locale/en/blog/vulnerability/openssl-november-2017.md +++ b/locale/en/blog/vulnerability/openssl-november-2017.md @@ -57,7 +57,6 @@ Our active release lines are: We will include an update here once all releases are made available. - ***Original post is included below*** diff --git a/locale/en/blog/weekly-updates/weekly-update.2015-03-06.md b/locale/en/blog/weekly-updates/weekly-update.2015-03-06.md index 3eaca103f451b..64f45ae86c21e 100644 --- a/locale/en/blog/weekly-updates/weekly-update.2015-03-06.md +++ b/locale/en/blog/weekly-updates/weekly-update.2015-03-06.md @@ -53,8 +53,6 @@ On Friday, March 6th, [@rvagg](https://github.com/rvagg) released io.js [**v1.5. * [@eranhammer](https://twitter.com/eranhammer) wrote a blog post called [The Node Version Dilemma](http://hueniverse.com/2015/03/02/the-node-version-dilemma/) which discusses the various node.js / io.js versions and proposes which ones to use and when to use them. - - ## io.js Support Added * **[scrypt](https://npmjs-com.sihan.fun/scrypt)** now supports io.js. Learn more from this [GitHub issue](https://github.com/barrysteyn/node-scrypt/issues/39) diff --git a/locale/en/blog/weekly-updates/weekly-update.2015-04-17.md b/locale/en/blog/weekly-updates/weekly-update.2015-04-17.md index ee6a95f7539d9..291913d12db75 100644 --- a/locale/en/blog/weekly-updates/weekly-update.2015-04-17.md +++ b/locale/en/blog/weekly-updates/weekly-update.2015-04-17.md @@ -8,7 +8,6 @@ slug: weekly-update-2015-04-17 layout: blog-post.hbs --- - # io.js 1.7 releases This week we had two io.js releases [v1.7.0](https://iojs.org/dist/v1.7.0/) and [v1.7.1](https://iojs.org/dist/v1.7.1/), complete changelog can be found [on GitHub](https://github.com/nodejs/node/blob/v1.x/CHANGELOG.md). diff --git a/locale/en/blog/weekly-updates/weekly-update.2015-04-24.md b/locale/en/blog/weekly-updates/weekly-update.2015-04-24.md index dd8b022a4be10..e3ae0bd50db4a 100644 --- a/locale/en/blog/weekly-updates/weekly-update.2015-04-24.md +++ b/locale/en/blog/weekly-updates/weekly-update.2015-04-24.md @@ -8,7 +8,6 @@ slug: weekly-update-2015-04-24 layout: blog-post.hbs --- - # io.js 1.8.1 release This week we had one io.js release [v1.8.1](https://iojs.org/dist/v1.8.1/), complete changelog can be found [on GitHub](https://github.com/nodejs/node/blob/v1.x/CHANGELOG.md). diff --git a/locale/en/blog/weekly-updates/weekly-update.2015-07-10.md b/locale/en/blog/weekly-updates/weekly-update.2015-07-10.md index d9bd2e3e026d2..b721fe14866dd 100644 --- a/locale/en/blog/weekly-updates/weekly-update.2015-07-10.md +++ b/locale/en/blog/weekly-updates/weekly-update.2015-07-10.md @@ -23,7 +23,6 @@ This week we have two io.js releases: [v2.3.4](https://iojs.org/dist/v2.3.4/) an * **openssl**: Upgrade to 1.0.2d, fixes CVE-2015-1793 (Alternate Chains Certificate Forgery) [#2141](https://github.com/nodejs/node/pull/2141). - #### 2.3.4 * **openssl**: Upgrade to 1.0.2d, fixes CVE-2015-1793 (Alternate Chains Certificate Forgery) (Shigeki Ohtsu) [#2141](https://github.com/nodejs/node/pull/2141). diff --git a/locale/en/blog/weekly-updates/weekly-update.2015-08-21.md b/locale/en/blog/weekly-updates/weekly-update.2015-08-21.md index 6fdc01f43858d..4055650831251 100644 --- a/locale/en/blog/weekly-updates/weekly-update.2015-08-21.md +++ b/locale/en/blog/weekly-updates/weekly-update.2015-08-21.md @@ -38,7 +38,6 @@ See https://github.com/nodejs/node/labels/confirmed-bug for complete and current * 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/node/issues/894) * `url.resolve` may transfer the auth portion of the url when resolving between two full hosts, see [#1435](https://github.com/nodejs/node/issues/1435). - ### Node.js v0.12 LTS plan has been shortened * Node.js v0.12 LTS plan has been shortened to end at the end of 2016, because OpenSSL 1.0.1 LTS is scheduled until the end of 2016. The detail is [here](https://github.com/nodejs/LTS/pull/36). @@ -60,5 +59,4 @@ If you have spotted or written something about Node.js and io.js, do come over t * [JSConf CO](http://www.jsconf.co/), October 16th - 17th at Ruta N, Medellin * [Nodevember](http://nodevember.org/?utm_source=io.js+and+Node.js+News&utm_medium=article), November 14th - 15th at Nashville, Tennessee, US. - Have an event about Node.js and io.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. diff --git a/locale/en/blog/weekly-updates/weekly-update.2015-08-28.md b/locale/en/blog/weekly-updates/weekly-update.2015-08-28.md index 8c50928b6d353..f40c6e9458cc7 100644 --- a/locale/en/blog/weekly-updates/weekly-update.2015-08-28.md +++ b/locale/en/blog/weekly-updates/weekly-update.2015-08-28.md @@ -15,7 +15,6 @@ io.js v3.2.0/v3.3.0 and Node v4 evangelism, nodejs.org, nodefest/empirenode even This week we have two io.js releases: [v3.2.0](https://iojs.org/dist/v3.2.0/) and [v3.3.0](https://iojs.org/dist/v3.3.0/), complete changelog from previous releases can be found [on GitHub](https://github.com/nodejs/node/blob/master/CHANGELOG.md). - ### io.js v3.3.0 Notable changes * **build**: Add a `--link-module` option to `configure` that can be used to bundle additional JavaScript modules into a built binary (Bradley Meck) [#2497](https://github.com/nodejs/node/pull/2497) @@ -44,7 +43,6 @@ See https://github.com/nodejs/node/labels/confirmed-bug for complete and current * 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/node/issues/894) * `url.resolve` may transfer the auth portion of the url when resolving between two full hosts, see [#1435](https://github.com/nodejs/node/issues/1435). - ### We need Node.js v4 evangelists * Node.js v4 is released soon. We need evangelists for Node.js v4. If you have an interest to evangelize, provide your information in [this issue](https://github.com/nodejs/node/issues/2633). @@ -89,5 +87,4 @@ If you have spotted or written something about Node.js and io.js, do come over t * [NodeFest](http://nodefest.jp/2015/), November 7th at Tokyo, Japan * [Nodevember](http://nodevember.org/?utm_source=io.js+and+Node.js+News&utm_medium=article), November 14th - 15th at Nashville, Tennessee, US. - Have an event about Node.js and io.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. diff --git a/locale/en/blog/weekly-updates/weekly-update.2015-09-04.md b/locale/en/blog/weekly-updates/weekly-update.2015-09-04.md index 56dd8336fe6f5..cbcb7291ab3c7 100644 --- a/locale/en/blog/weekly-updates/weekly-update.2015-09-04.md +++ b/locale/en/blog/weekly-updates/weekly-update.2015-09-04.md @@ -68,7 +68,4 @@ If you have spotted or written something about Node.js and io.js, do come over t * [Nodevember](http://nodevember.org/?utm_source=io.js+and+Node.js+News&utm_medium=article), November 14th - 15th at Nashville, Tennessee, US. * [NodeConf Barcelona](https://ti.to/barcelonajs/nodeconf-barcelona-2015), November 21st at Barcelona, Spain - Have an event about Node.js and io.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. - - diff --git a/locale/en/blog/weekly-updates/weekly-update.2015-11-06.md b/locale/en/blog/weekly-updates/weekly-update.2015-11-06.md index 4a76d56a3fe06..d713906dd7455 100644 --- a/locale/en/blog/weekly-updates/weekly-update.2015-11-06.md +++ b/locale/en/blog/weekly-updates/weekly-update.2015-11-06.md @@ -27,7 +27,6 @@ This is an LTS maintenance release that addresses a number of issues: * NodeUp podcast episode 93, 94 were published this week: , . * The subjects of the podcast are "An LTS Show with Kat Marchán, James Snell, and Rich Trott", "A Node.js Interactive Show with Dan Shaw, Mikeal Rogers, and Kassandra Perch.". - ### Community Updates * [Understanding Garbage Collection and hunting Memory Leaks in Node.js](http://apmblog.dynatrace.com/2015/11/04/understanding-garbage-collection-and-hunting-memory-leaks-in-node-js/), "Covers how Node.js manages memory and how to trace down memory-related problems" diff --git a/locale/en/blog/weekly-updates/weekly-update.2016-12-25.md b/locale/en/blog/weekly-updates/weekly-update.2016-12-25.md index 6abe74e018a00..dd82700e851b3 100644 --- a/locale/en/blog/weekly-updates/weekly-update.2016-12-25.md +++ b/locale/en/blog/weekly-updates/weekly-update.2016-12-25.md @@ -16,7 +16,6 @@ layout: blog-post.hbs * [Node v7.3.0 (Current)](https://nodejs.org/en/blog/release/v7.3.0/). The complete changelog can be found [on GitHub](https://github.com/nodejs/node/blob/master/CHANGELOG.md). - ### Help in Promoting our Node.js Foundation survey * The Node.js Foundation launched a second user survey to learn more about how developers are using Node.js. diff --git a/locale/en/docs/guides/anatomy-of-an-http-transaction.md b/locale/en/docs/guides/anatomy-of-an-http-transaction.md index 289514b9c5537..e7cdb03e47bf4 100644 --- a/locale/en/docs/guides/anatomy-of-an-http-transaction.md +++ b/locale/en/docs/guides/anatomy-of-an-http-transaction.md @@ -401,8 +401,6 @@ From these basics, Node.js HTTP servers for many typical use cases can be constructed. There are plenty of other things these APIs provide, so be sure to read through the API docs for [`EventEmitters`][], [`Streams`][], and [`HTTP`][]. - - [`EventEmitters`]: https://nodejs.org/api/events.html [`Streams`]: https://nodejs.org/api/stream.html [`createServer`]: https://nodejs.org/api/http.html#http_http_createserver_requestlistener diff --git a/locale/en/docs/guides/backpressuring-in-streams.md b/locale/en/docs/guides/backpressuring-in-streams.md index a03622f9a6f12..1444a2e871243 100644 --- a/locale/en/docs/guides/backpressuring-in-streams.md +++ b/locale/en/docs/guides/backpressuring-in-streams.md @@ -592,7 +592,6 @@ Be sure to read up more on [`Stream`][] for other API functions to help improve and unleash your streaming capabilities when building an application with Node.js. - [`Stream`]: https://nodejs.org/api/stream.html [`Buffer`]: https://nodejs.org/api/buffer.html [`EventEmitters`]: https://nodejs.org/api/events.html diff --git a/locale/en/docs/guides/blocking-vs-non-blocking.md b/locale/en/docs/guides/blocking-vs-non-blocking.md index 0d22c123367fc..e50e675444406 100644 --- a/locale/en/docs/guides/blocking-vs-non-blocking.md +++ b/locale/en/docs/guides/blocking-vs-non-blocking.md @@ -13,7 +13,6 @@ basic understanding of the JavaScript language and Node.js [callback pattern](ht > "I/O" refers primarily to interaction with the system's disk and > network supported by [libuv](https://libuv.org/). - ## Blocking **Blocking** is when the execution of additional JavaScript in the Node.js @@ -32,7 +31,6 @@ versions, which are **non-blocking**, and accept callback functions. Some methods also have **blocking** counterparts, which have names that end with `Sync`. - ## Comparing Code **Blocking** methods execute **synchronously** and **non-blocking** methods @@ -87,7 +85,6 @@ can continue and `moreWork()` will be called first. The ability to run `moreWork()` without waiting for the file read to complete is a key design choice that allows for higher throughput. - ## Concurrency and Throughput JavaScript execution in Node.js is single threaded, so concurrency refers to the @@ -106,7 +103,6 @@ capacity just by choosing to use **non-blocking** methods instead of The event loop is different than models in many other languages where additional threads may be created to handle concurrent work. - ## Dangers of Mixing Blocking and Non-Blocking Code There are some patterns that should be avoided when dealing with I/O. Let's look @@ -126,7 +122,6 @@ In the above example, `fs.unlinkSync()` is likely to be run before better way to write this, which is completely **non-blocking** and guaranteed to execute in the correct order is: - ```js const fs = require('fs'); fs.readFile('/file.md', (readFileErr, data) => { @@ -141,7 +136,6 @@ fs.readFile('/file.md', (readFileErr, data) => { The above places a **non-blocking** call to `fs.unlink()` within the callback of `fs.readFile()` which guarantees the correct order of operations. - ## Additional Resources - [libuv](https://libuv.org/) diff --git a/locale/en/docs/guides/diagnostics-flamegraph.md b/locale/en/docs/guides/diagnostics-flamegraph.md index 982e92666348d..43a59a69e4e8d 100644 --- a/locale/en/docs/guides/diagnostics-flamegraph.md +++ b/locale/en/docs/guides/diagnostics-flamegraph.md @@ -114,7 +114,6 @@ node`_ZN2v88internal11interpreter17BytecodeGenerator15VisitStatementsEPNS0_8Zone ``` it means the Linux perf you're using was not compiled with demangle support, see https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1396654 for example - ## Examples Practice capturing flame graphs yourself with [a flame graph exercise](https://github.com/naugtur/node-example-flamegraph)! diff --git a/locale/en/docs/guides/domain-postmortem.md b/locale/en/docs/guides/domain-postmortem.md index 6426c2a73361a..310d7c7ee2b93 100644 --- a/locale/en/docs/guides/domain-postmortem.md +++ b/locale/en/docs/guides/domain-postmortem.md @@ -22,13 +22,11 @@ Here's an example of how one indirectly linked modules can affect another: const b = require('./b'); const c = require('./c'); - // module b.js const d = require('domain').create(); d.on('error', () => { /* silence everything */ }); d.enter(); - // module c.js const dep = require('some-dep'); dep.method(); // Uh-oh! This method doesn't actually exist. @@ -99,7 +97,6 @@ automatically bubble. Unfortunately both these situations occur, leading to potentially confusing behavior that may even be prone to difficult to debug timing conflicts. - ### API Gaps While APIs based on using `EventEmitter` can use `bind()` and errback style @@ -109,7 +106,6 @@ wanted to support domains using a mechanism alternative to those mentioned they must manually implement domain support themselves. Instead of being able to leverage the implicit mechanisms already in place. - ### Error Propagation Propagating errors across nested domains is not straight forward, if even @@ -155,7 +151,6 @@ several asynchronous requests and each one then `write()`'s data back to the client many more errors will arise from attempting to `write()` to a closed handle. More on this in _Resource Cleanup on Exception_. - ### Resource Cleanup on Exception The following script contains a more complex example of properly cleaning up @@ -333,7 +328,6 @@ In the end, in terms of handling errors, domains aren't much more than a glorified `'uncaughtException'` handler. Except with more implicit and unobservable behavior by third-parties. - ### Resource Propagation Another use case for domains was to use it to propagate data along asynchronous @@ -408,7 +402,6 @@ user's callback is called. Also the instantiation of `DataStream` in the In short, for this to have a prayer of a chance usage would need to strictly adhere to a set of guidelines that would be difficult to enforce or test. - ## Performance Issues A significant deterrent from using domains is the overhead. Using node's @@ -433,7 +426,6 @@ will result in a 17% performance loss. Granted, this is for the optimized scenario of the benchmark, but I believe this demonstrates the necessity for a mechanism such as domain to be as cheap to run as possible. - ## Looking Ahead The domain module has been soft deprecated since Dec 2014, but has not yet been diff --git a/locale/en/docs/guides/event-loop-timers-and-nexttick.md b/locale/en/docs/guides/event-loop-timers-and-nexttick.md index 53314763fefd7..683bb8bebc2f6 100644 --- a/locale/en/docs/guides/event-loop-timers-and-nexttick.md +++ b/locale/en/docs/guides/event-loop-timers-and-nexttick.md @@ -71,7 +71,6 @@ demonstration. The most important parts are here. There are actually seven or eight steps, but the ones we care about — ones that Node.js actually uses - are those above._ - ## Phases Overview * **timers**: this phase executes callbacks scheduled by `setTimeout()` @@ -123,7 +122,6 @@ setTimeout(() => { console.log(`${delay}ms have passed since I was scheduled`); }, 100); - // do someAsyncOperation which takes 95 ms to complete someAsyncOperation(() => { const startCallback = Date.now(); @@ -233,7 +231,6 @@ cycle (i.e. the main module), the order in which the two timers are executed is non-deterministic, as it is bound by the performance of the process: - ```js // timeout_vs_immediate.js setTimeout(() => { diff --git a/locale/en/docs/guides/index.md b/locale/en/docs/guides/index.md index da99977b300e8..fd5158b720604 100644 --- a/locale/en/docs/guides/index.md +++ b/locale/en/docs/guides/index.md @@ -14,7 +14,6 @@ layout: docs.hbs - [Dockerizing a Node.js web app](nodejs-docker-webapp/) - [Migrating to safe Buffer constructors](buffer-constructor-deprecation/) - ## Node.js core concepts - [Overview of Blocking vs Non-Blocking](blocking-vs-non-blocking/) @@ -22,7 +21,6 @@ layout: docs.hbs - [Don't Block the Event Loop (or the Worker Pool)](dont-block-the-event-loop/) - [Timers in Node.js](timers-in-node/) - ## Module-related guides - [Anatomy of an HTTP Transaction](anatomy-of-an-http-transaction/) diff --git a/locale/en/download/package-manager.md b/locale/en/download/package-manager.md index 8ab29e1926b45..370223e16d990 100644 --- a/locale/en/download/package-manager.md +++ b/locale/en/download/package-manager.md @@ -213,7 +213,6 @@ Or build manually from pkgsrc: cd pkgsrc/lang/nodejs && bmake install ``` - ## Solus Solus provides node.js in its main repository. @@ -222,7 +221,6 @@ Solus provides node.js in its main repository. sudo eopkg install nodejs ``` - ## Void Linux Void Linux ships node.js stable in the main repository. diff --git a/locale/en/get-involved/index.md b/locale/en/get-involved/index.md index 9e127110e3425..ba8a982e6e8e2 100644 --- a/locale/en/get-involved/index.md +++ b/locale/en/get-involved/index.md @@ -15,7 +15,6 @@ layout: contribute.hbs - [Node.js Collection](https://medium.com/the-node-js-collection) is a collection of community-curated content on Medium. - The [Community Committee](https://github.com/nodejs/community-committee) is a top-level committee in the Node.js Foundation focused on community-facing efforts. - ## Learning - [Official API reference documentation](/api/) details the Node.js API. diff --git a/locale/en/get-involved/node-meetups.md b/locale/en/get-involved/node-meetups.md index f2c3cce633daf..e1ee42c35cae1 100644 --- a/locale/en/get-involved/node-meetups.md +++ b/locale/en/get-involved/node-meetups.md @@ -427,7 +427,6 @@ REQUIREMENTS - Organizer name - Matt Pardee - Organizer contact info - - #### Colorado ##### Denver @@ -587,7 +586,6 @@ REQUIREMENTS - Organizer name - Aaron Seth Madsen - Organizer contact info - - #### Washington ##### Seattle @@ -654,7 +652,6 @@ REQUIREMENTS - Organizer names - Michael Antczak - Organizers contact info - [AntczakMichael](https://twitter.com/AntczakMichael) - ### Ukraine #### Kiev diff --git a/locale/en/knowledge/HTTP/clients/how-to-create-a-HTTP-request.md b/locale/en/knowledge/HTTP/clients/how-to-create-a-HTTP-request.md index dd4810a13d865..44b9ad4f1f31e 100644 --- a/locale/en/knowledge/HTTP/clients/how-to-create-a-HTTP-request.md +++ b/locale/en/knowledge/HTTP/clients/how-to-create-a-HTTP-request.md @@ -8,7 +8,6 @@ difficulty: 2 layout: knowledge-post.hbs --- - Another extremely common programming task is making an HTTP request to a web server. Node.js provides an extremely simple API for this functionality in the form of `http.request`. As an example, we are going to preform a GET request to [www.random.org/integers/?num=1&min=1&max=10&col=1&base=10&format=plain&rnd=new](www.random.org/integers/?num=1&min=1&max=10&col=1&base=10&format=plain&rnd=new) (which returns a random integer between 1 and 10) and print the result to the console. @@ -37,7 +36,6 @@ As an example, we are going to preform a GET request to [www.random.org/integers http.request(options, callback).end(); - Making a POST request is just as easy. We will make a POST request to `www.nodejitsu.com:1337` which is running a server that will echo back what we post. The code for making a POST request is almost identical to making a GET request, just a few simple modifications: var http = require('http'); diff --git a/locale/en/knowledge/HTTP/servers/how-to-create-a-HTTP-server.md b/locale/en/knowledge/HTTP/servers/how-to-create-a-HTTP-server.md index b69c81767b38c..7777ef6554b5b 100644 --- a/locale/en/knowledge/HTTP/servers/how-to-create-a-HTTP-server.md +++ b/locale/en/knowledge/HTTP/servers/how-to-create-a-HTTP-server.md @@ -7,7 +7,6 @@ difficulty: 1 layout: knowledge-post.hbs --- - 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. Let's take a look at a very simple example: diff --git a/locale/en/knowledge/HTTP/servers/how-to-read-POST-data.md b/locale/en/knowledge/HTTP/servers/how-to-read-POST-data.md index 132a049b7fd7b..494aeb5f81c99 100644 --- a/locale/en/knowledge/HTTP/servers/how-to-read-POST-data.md +++ b/locale/en/knowledge/HTTP/servers/how-to-read-POST-data.md @@ -41,4 +41,3 @@ With the HTML out of the way, we [create a server](/how-do-i-create-a-http-serve Something important to note is that the event listeners are being added immediately after the request object is received. If you don't immediately set them, then there is a possibility of missing some of the events. If, for example, an event listener was attached from inside a callback, then the `data` and `end` events might be fired in the meantime with no listeners attached! You can save this script to `server.js` and run it with `node server.js`. Once you run it you will notice that occasionally you will see lines with no data, e.g. `POSTed:`. This happens because regular `GET` requests go through the same codepath. In a more 'real-world' application, it would be proper practice to check the type of request and handle the different request types differently. - diff --git a/locale/en/knowledge/advanced/streams/how-to-use-fs-create-read-stream.md b/locale/en/knowledge/advanced/streams/how-to-use-fs-create-read-stream.md index d0a4823c575b1..db4464bad2168 100644 --- a/locale/en/knowledge/advanced/streams/how-to-use-fs-create-read-stream.md +++ b/locale/en/knowledge/advanced/streams/how-to-use-fs-create-read-stream.md @@ -32,4 +32,3 @@ The function `fs.createReadStream()` allows you to open up a readable stream in res.end(err); }); }).listen(8080); - diff --git a/locale/en/knowledge/advanced/streams/what-are-streams.md b/locale/en/knowledge/advanced/streams/what-are-streams.md index 26908207c0385..977c15bbd1039 100644 --- a/locale/en/knowledge/advanced/streams/what-are-streams.md +++ b/locale/en/knowledge/advanced/streams/what-are-streams.md @@ -8,8 +8,6 @@ difficulty: 3 layout: knowledge-post.hbs --- - - Streams are another basic construct in node.js that encourages asynchronous coding. Streams allow you to process the data as it is generated or retrieved. Streams can be readable, writeable, or both. In other words, Streams use events to deal with data as it happens, rather than only with a callback at the end. Readable streams emit the event `data` for each chunk of data that comes in, and an `end` event, which is emitted when there is no more data. Writeable streams can be written to with the `write()` function, and closed with the `end()` function. All types of streams emit `error` events when errors arise. @@ -41,5 +39,4 @@ Run this script with arguments like `node cp.js src.txt dest.txt`. This would me console.log("ERROR", err); }); - This sets up a readable stream from the source file and a writable stream to the destination file. Then whenever the readable stream gets data, it gets written to the writeable stream. Then finally it closes the writable stream when the readable stream is finished. NOTE: it would have been better to use [pipe](/how-to-use-stream-pipe) like `readStream.pipe(writeStream);`, however, to show how streams work, we have done things the long way. diff --git a/locale/en/knowledge/child-processes/how-to-spawn-a-child-process.md b/locale/en/knowledge/child-processes/how-to-spawn-a-child-process.md index 6134f1d7a49bc..f0077c1433cd8 100644 --- a/locale/en/knowledge/child-processes/how-to-spawn-a-child-process.md +++ b/locale/en/knowledge/child-processes/how-to-spawn-a-child-process.md @@ -8,7 +8,6 @@ difficulty: 2 layout: knowledge-post.hbs --- - 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. 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. diff --git a/locale/en/knowledge/command-line/how-to-get-colors-on-the-command-line.md b/locale/en/knowledge/command-line/how-to-get-colors-on-the-command-line.md index 11d8ba8df4534..8d45bb8b015c1 100644 --- a/locale/en/knowledge/command-line/how-to-get-colors-on-the-command-line.md +++ b/locale/en/knowledge/command-line/how-to-get-colors-on-the-command-line.md @@ -7,7 +7,6 @@ difficulty: 1 layout: knowledge-post.hbs --- - When working on the command line, it can be both fun and extremely useful to colorize one's output. To colorize console output, you need to use ANSI escape codes. The module [colors.js](https://www.npmjs.com/package/colors), available on `npm`, provides an extremely easy to use wrapper that makes adding colors a breeze. First, install it to the directory you'd like to work in. diff --git a/locale/en/knowledge/command-line/how-to-parse-command-line-arguments.md b/locale/en/knowledge/command-line/how-to-parse-command-line-arguments.md index df0712e5501e7..3d7413b457139 100644 --- a/locale/en/knowledge/command-line/how-to-parse-command-line-arguments.md +++ b/locale/en/knowledge/command-line/how-to-parse-command-line-arguments.md @@ -7,7 +7,6 @@ difficulty: 1 layout: knowledge-post.hbs --- - Passing in arguments via the command line is an extremely basic programming task, and a necessity for anyone trying to write a simple Command-Line Interface (CLI). In Node.js, as in C and many related environments, all command-line arguments received by the shell are given to the process in an array called `argv` (short for 'argument values'). Node.js exposes this array for every running process in the form of `process.argv` - let's take a look at an example. Make a file called `argv.js` and add this line: diff --git a/locale/en/knowledge/cryptography/how-to-use-the-tls-module.md b/locale/en/knowledge/cryptography/how-to-use-the-tls-module.md index 689d5d5d3a9f4..57d7fc0c5250a 100644 --- a/locale/en/knowledge/cryptography/how-to-use-the-tls-module.md +++ b/locale/en/knowledge/cryptography/how-to-use-the-tls-module.md @@ -51,7 +51,6 @@ In most ways, the tls module's server api is similar to that of the net module. s.pipe(s); }).listen(8000); - In this example, a "hello world" tls server is created, listening on port 8000. The options object includes two properties: `key` and `cert`. The contents of these properties come directly from the private key and public certificate stored on the filesystem. In this case they are binary buffers, but the tls module can also accept unicode strings. ### Generating Your Private Key And Certificate With OpenSSL: @@ -131,8 +130,6 @@ The tls module also supplies tools for connecting to such a server: console.log(); }); - - conn.on("data", function (data) { console.log(data.toString()); conn.end(); diff --git a/locale/en/knowledge/errors/what-are-the-error-conventions.md b/locale/en/knowledge/errors/what-are-the-error-conventions.md index 6dd2d64f19d84..e7145b46975d3 100644 --- a/locale/en/knowledge/errors/what-are-the-error-conventions.md +++ b/locale/en/knowledge/errors/what-are-the-error-conventions.md @@ -8,7 +8,6 @@ difficulty: 1 layout: knowledge-post.hbs --- - 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. It's simpler than it sounds; let's demonstrate. diff --git a/locale/en/knowledge/file-system/how-to-search-files-and-directories-in-nodejs.md b/locale/en/knowledge/file-system/how-to-search-files-and-directories-in-nodejs.md index a708eb556f33a..ea4225f60f86e 100644 --- a/locale/en/knowledge/file-system/how-to-search-files-and-directories-in-nodejs.md +++ b/locale/en/knowledge/file-system/how-to-search-files-and-directories-in-nodejs.md @@ -19,7 +19,6 @@ Suppose you want to list all the files in the current directory. One approach i console.log(files); }); - 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). To install `node-findit`, simply use npm: diff --git a/locale/en/knowledge/file-system/how-to-store-local-config-data.md b/locale/en/knowledge/file-system/how-to-store-local-config-data.md index 4e6aba75d9ed0..52a298af08e5d 100644 --- a/locale/en/knowledge/file-system/how-to-store-local-config-data.md +++ b/locale/en/knowledge/file-system/how-to-store-local-config-data.md @@ -8,7 +8,6 @@ difficulty: 1 layout: knowledge-post.hbs --- - Storing your Node.js application's configuration data is quite simple - every object in JavaScript can be easily rendered as [JSON](/what-is-json), which in turn is just string data that can be sent or saved any way you'd like. The simplest way to do this involves the built-in `JSON.parse()` and `JSON.stringify()` methods. Let's take a look at a very simple (and contrived) example. First, to save some very simple data: @@ -82,4 +81,3 @@ After that, the syntax is a breeze. Have a look at an example: The only tricky thing to notice here is the delimiter - ':'. When accessing nested properties with `nconf`, a colon is used to delimit the namespaces of key names. If a specific sub-key is not provided, the whole object is set or returned. When using `nconf` to store your configuration data to a file, `nconf.save()` and `nconf.load()` are the only times that any actual file interaction will happen. All other access is performed on an in-memory copy of your data, which will not persist without a call to `nconf.save()`. Similarly, if you're trying to bring back configuration data from the last time your application ran, it will not exist in memory without a call to `nconf.load()`, as shown above. - diff --git a/locale/en/knowledge/file-system/how-to-use-the-path-module.md b/locale/en/knowledge/file-system/how-to-use-the-path-module.md index 584f0ff4583dd..e3e9bb0ef4225 100644 --- a/locale/en/knowledge/file-system/how-to-use-the-path-module.md +++ b/locale/en/knowledge/file-system/how-to-use-the-path-module.md @@ -65,4 +65,3 @@ Blocking isn't always a bad thing. Checking the existence of a vital configurat > path.existsSync('/etc') true - diff --git a/locale/en/knowledge/getting-started/control-flow/how-to-write-asynchronous-code.md b/locale/en/knowledge/getting-started/control-flow/how-to-write-asynchronous-code.md index 2e3c622d40503..b961928bd89ec 100644 --- a/locale/en/knowledge/getting-started/control-flow/how-to-write-asynchronous-code.md +++ b/locale/en/knowledge/getting-started/control-flow/how-to-write-asynchronous-code.md @@ -37,7 +37,6 @@ The asynchronous version, on the other hand, does not stop time - instead, the c When only reading a file or two, or saving something quickly, the difference between synchronous and asynchronous file I/O can be quite small. On the other hand, though, when you have multiple requests coming in per second that require file or database IO, trying to do that IO synchronously would be quite thoroughly disastrous for performance. - ### Callbacks Callbacks are a basic idiom in node.js for asynchronous operations. When most people talk about callbacks, they mean the function that is passed as the last parameter to an asynchronous function. The callback is then later called with any return value or error message that the function produced. For more details, see the article on [callbacks](/en/knowledge/getting-started/control-flow/what-are-callbacks) diff --git a/locale/en/knowledge/getting-started/control-flow/what-are-callbacks.md b/locale/en/knowledge/getting-started/control-flow/what-are-callbacks.md index 022b5194a8f74..a5c3093f3588c 100644 --- a/locale/en/knowledge/getting-started/control-flow/what-are-callbacks.md +++ b/locale/en/knowledge/getting-started/control-flow/what-are-callbacks.md @@ -10,7 +10,6 @@ difficulty: 1 layout: knowledge-post.hbs --- - In a synchronous program, you would write something along the lines of: function processData () { diff --git a/locale/en/knowledge/getting-started/control-flow/what-are-event-emitters.md b/locale/en/knowledge/getting-started/control-flow/what-are-event-emitters.md index f3bf0effa48e2..65ca1e9e992c1 100644 --- a/locale/en/knowledge/getting-started/control-flow/what-are-event-emitters.md +++ b/locale/en/knowledge/getting-started/control-flow/what-are-event-emitters.md @@ -9,7 +9,6 @@ difficulty: 2 layout: knowledge-post.hbs --- - In node.js an event can be described simply as a string with a corresponding callback. An event can be "emitted" (or in other words, the corresponding callback be called) multiple times or you can choose to only listen for the first time it is emitted. So a simple example ran on the node [REPL](/en/knowledge/REPL/how-to-use-nodejs-repl): var example_emitter = new (require('events').EventEmitter); @@ -100,4 +99,3 @@ If you want remove a specific callback, you can use `removeListener`. If you wan false NOTE: If you want create more than 10 listeners on a single event, you will have to make a call to `ee.setMaxListeners(n)` where n is the max numbers of listeners (with zero being unlimited number of listeners). This is used to make sure you aren't accidentally leaking event listeners. - diff --git a/locale/en/knowledge/getting-started/how-to-debug-nodejs-applications.md b/locale/en/knowledge/getting-started/how-to-debug-nodejs-applications.md index f20cdc8d67c4f..69e0ab0145409 100644 --- a/locale/en/knowledge/getting-started/how-to-debug-nodejs-applications.md +++ b/locale/en/knowledge/getting-started/how-to-debug-nodejs-applications.md @@ -9,7 +9,6 @@ layout: knowledge-post.hbs Often times, not just in the Node.js community but in software at large, people debug simply with a liberal sprinkle of standard output statements. This allows you to track down where unexpected values are being generated. However, this method can be tedious, or worse yet, not robust enough to detect the real problem. - ### Set up Thankfully, through the use of `node-inspector`, we can harness to power of the webkit-debuggers to work with our node.js code. The process itself is simple. diff --git a/locale/en/knowledge/getting-started/how-to-use-util-inspect.md b/locale/en/knowledge/getting-started/how-to-use-util-inspect.md index 9f9844ddebd74..fcbd433e6f60c 100644 --- a/locale/en/knowledge/getting-started/how-to-use-util-inspect.md +++ b/locale/en/knowledge/getting-started/how-to-use-util-inspect.md @@ -46,4 +46,3 @@ Finally, the optional argument `colorize` is a boolean that adds ANSI escape cod var util = require('util'); console.log(util.inspect({a:1, b:"b"}, false,2,true)); - diff --git a/locale/en/knowledge/getting-started/npm/how-to-access-module-package-info.md b/locale/en/knowledge/getting-started/npm/how-to-access-module-package-info.md index 7c4b67ae7cf4a..1f7457256ae52 100644 --- a/locale/en/knowledge/getting-started/npm/how-to-access-module-package-info.md +++ b/locale/en/knowledge/getting-started/npm/how-to-access-module-package-info.md @@ -8,7 +8,6 @@ difficulty: 1 layout: knowledge-post.hbs --- - 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. Let's take a look at pkginfo - first, install via npm: diff --git a/locale/en/knowledge/getting-started/npm/what-is-npm.md b/locale/en/knowledge/getting-started/npm/what-is-npm.md index c87b486f30333..d6f25d0d369fc 100644 --- a/locale/en/knowledge/getting-started/npm/what-is-npm.md +++ b/locale/en/knowledge/getting-started/npm/what-is-npm.md @@ -9,7 +9,6 @@ layout: knowledge-post.hbs `npm`, short for Node Package Manager, is two things: first and foremost, it is an online repository for the publishing of open-source Node.js projects; second, it is a command-line utility for interacting with said repository that aids in package installation, version management, and dependency management. A plethora of node.js libraries and applications are published on npm, and many more are added every day. These applications can be searched for on http://search.npmjs.org/. Once you have a package you want to install, it can be installed with a single command-line command. - Let's say you're hard at work one day, developing the Next Great Application. You come across a problem, and you decide that it's time to use that cool library you keep hearing about - let's use Caolan McMahon's [async](https://github.com/caolan/async) as an example. Thankfully, `npm` is very simple to use: you only have to run `npm install async`, and the specified module will be installed in the current directory under `./node_modules/`. Once installed to your `node_modules` folder, you'll be able to use `require()` on them just like they were built-ins. Let's look at an example of a global install - let's say `coffee-script`. The npm command is simple: `npm install coffee-script -g`. This will typically install the program and put a symlink to it in `/usr/local/bin/`. This will then allow you to run the program from the console just like any other CLI tool. In this case, running `coffee` will now allow you to use the coffee-script REPL. @@ -23,4 +22,3 @@ Example: npm install After running those commands, you will see a `node_modules` folder containing all of the project dependencies specified in the package.json. - diff --git a/locale/en/knowledge/getting-started/the-console-module.md b/locale/en/knowledge/getting-started/the-console-module.md index 0b7342e13441c..55fd6518e83a1 100644 --- a/locale/en/knowledge/getting-started/the-console-module.md +++ b/locale/en/knowledge/getting-started/the-console-module.md @@ -9,7 +9,6 @@ difficulty: 1 layout: knowledge-post.hbs --- - Anyone familiar with browser-side development has probably used `console.log` for debugging purposes - Node.js has implemented a built-in `console` object to mimic much of this experience. Since we're working server-side, however, it wraps `stdout`, `stdin`, and `stderr` instead of the browser's debugging console. Because of this browser parallel, the `console` module has become home to quite a bit of Node's standard output functionality. The simplest is `console.log()`. diff --git a/locale/en/knowledge/getting-started/the-process-module.md b/locale/en/knowledge/getting-started/the-process-module.md index 7793b20b5cc29..9b18f9226aa59 100644 --- a/locale/en/knowledge/getting-started/the-process-module.md +++ b/locale/en/knowledge/getting-started/the-process-module.md @@ -8,7 +8,6 @@ difficulty: 2 layout: knowledge-post.hbs --- - Each Node.js process has a set of built-in functionality, accessible through the global `process` module. The `process` module doesn't need to be required - it is somewhat literally a wrapper around the currently executing process, and many of the methods it exposes are actually wrappers around calls into some of Node's core C libraries. ## Events diff --git a/locale/en/knowledge/getting-started/what-is-require.md b/locale/en/knowledge/getting-started/what-is-require.md index 8f5367b00ca45..f79b5a472f175 100644 --- a/locale/en/knowledge/getting-started/what-is-require.md +++ b/locale/en/knowledge/getting-started/what-is-require.md @@ -51,10 +51,8 @@ It is worth noting that each time you subsequently require an already-required f node> require('./example.js') //One might think that this "reloads" the file... { message: 'hey', say: [Function] } //...but the message is still "hey" because of the module cache. - As you can see from the above, `example.js` is evaluated the first time, but all subsequent calls to `require()` only invoke the module cache, rather than reading the file again. As seen above, this can occasionally produce side effects. The rules of where `require` finds the files can be a little complex, but a simple rule of thumb is that if the file doesn't start with "./" or "/", then it is either considered a core module (and the local Node path is checked), or a dependency in the local `node_modules` folder. If the file starts with "./" it is considered a relative file to the file that called `require`. If the file starts with "/", it is considered an absolute path. NOTE: you can omit ".js" and `require` will automatically append it if needed. For more detailed information, see [the official docs](https://nodejs.org/docs/v0.4.2/api/modules.htmll#all_Together...) An extra note: if the filename passed to `require` is actually a directory, it will first look for `package.json` in the directory and load the file referenced in the `main` property. Otherwise, it will look for an `index.js`. - diff --git a/locale/en/security.md b/locale/en/security.md index 3e728366ad6fd..54dc5a971e7cb 100644 --- a/locale/en/security.md +++ b/locale/en/security.md @@ -54,7 +54,6 @@ the severity of the bug or difficulty in applying a fix. effort will be made to handle the bug in as timely a manner as possible; however, it’s important that we follow the release process above to ensure that the disclosure is handled in a consistent manner. - ## Receiving Security Updates Security notifications will be distributed via the following methods. diff --git a/locale/es/download/package-manager.md b/locale/es/download/package-manager.md index 5753bcfbfb21e..99082d037a1eb 100644 --- a/locale/es/download/package-manager.md +++ b/locale/es/download/package-manager.md @@ -44,7 +44,6 @@ Paquetes para Node.js y npm están disponibles en el repositorio de la comunidad pacman -S nodejs npm ``` - ## Distribuciones de Linux basadas en Debian y Ubuntu, Enterprise Linux/Fedora y Snap [Las distribuciones de binarios oficiales de Node.js](https://github.com/nodesource/distributions/blob/master/README.md) son proporcinadas por NodeSource. @@ -81,7 +80,6 @@ pkg install node pkg install node-devel ``` - ## Gentoo Node.js está disponible en el árbol de portage. @@ -90,7 +88,6 @@ Node.js está disponible en el árbol de portage. emerge nodejs ``` - ## NetBSD Node.js está disponible en el árbol de pkgsrc: @@ -105,7 +102,6 @@ cd /usr/pkgsrc/lang/nodejs && make install pkgin -y install nodejs ``` - ## openSUSE y SLE [Descargue Node.js mediante openSUSE one-click](http://software.opensuse.org/download.html?project=devel%3Alanguages%3Anodejs&package=nodejs). @@ -121,7 +117,6 @@ sudo zypper ar \ sudo zypper in nodejs nodejs-devel ``` - ## macOS Simplemente descargue el [Instalador para macOS](https://nodejs.org/#download) directamente desde el sitio web de [nodejs.org](https://nodejs.org). @@ -177,7 +172,6 @@ pkgin -y install nodejs cd pkgsrc/lang/nodejs && bmake install ``` - ## Solus Solus provides node.js in its main repository. @@ -186,7 +180,6 @@ Solus provides node.js in its main repository. sudo eopkg install nodejs ``` - ## Void Linux Void Linux incluye node.js estable en el repositorio principal. @@ -195,7 +188,6 @@ Void Linux incluye node.js estable en el repositorio principal. xbps-install -Sy nodejs ``` - ## Windows Simplemente descargue el [Instalador para Windows](https://nodejs.org/#download) directamente desde el sitio web de [nodejs.org](https://nodejs.org). diff --git a/locale/es/download/releases.md b/locale/es/download/releases.md index bb2ca70313175..1748ce19302e3 100644 --- a/locale/es/download/releases.md +++ b/locale/es/download/releases.md @@ -19,4 +19,3 @@ Las versiones desde la 1.x hasta la 3.x fueron llamadas "io.js" ya que fueron pa
  • Todas las versiones
    • - diff --git a/locale/es/get-involved/index.md b/locale/es/get-involved/index.md index 5527aef55cc01..fad2dc1bbb5e6 100644 --- a/locale/es/get-involved/index.md +++ b/locale/es/get-involved/index.md @@ -14,14 +14,12 @@ layout: contribute.hbs - [Node Weekly](https://nodeweekly.com/) es una lista de correo que recopila los últimos eventos y noticias alrededor de la comunidad de Node.js. - La [Community Committee](https://github.com/nodejs/community-committee) es un comité de alto nivel de la Fundación Node.js centrado en los esfuerzos de la comunidad. - ## Aprendizaje - La [Documentación oficial de la API](/api/) detalla la API de Node. - [NodeSchool.io](https://nodeschool.io/) le enseñará conceptos de Node.js de forma interactiva mediante juegos utilizando la línea de comandos. - La [etiqueta de Node.js en Stack Overflow](https://stackoverflow.com/questions/tagged/node.js) colecciona nueva información cada día. - ## Sitios de la comunidad internacional y proyectos - [Comunidad China](https://cnodejs.org/) diff --git a/locale/es/security.md b/locale/es/security.md index b14ef818c5358..7866fefa0baae 100644 --- a/locale/es/security.md +++ b/locale/es/security.md @@ -50,7 +50,6 @@ Las notificaciones de seguridad serán distribuidas usando los siguientes medios - - - ## Comentarios sobre esta política Si usted tiene sugerencias sobre como puede ser mejorado ese proceso, por favor envíe un [pull request](https://github.com/nodejs/nodejs.org) diff --git a/locale/fa/about/index.md b/locale/fa/about/index.md index 814c0bede44c2..5d412095bd922 100644 --- a/locale/fa/about/index.md +++ b/locale/fa/about/index.md @@ -9,7 +9,6 @@ trademark: نشان تجاری به عنوان یک اجرا کننده رویدادهای ناهماهنگ در جاوا اسکریپت، Node.js به شکلی طراحی شده است که بتوان با آن برنامه‌های تحت وب توسعه پذیر ساخت. در مثال "hello world" پایین، تعداد خیلی زیادی اتصال به صورت هم زمان انجام گیرد. پس از هر اتصال یه فراخوان (callback) اجرا خواهد شد، اما اگر کاری برای انجام نباشد نود می‌خوابد. - ```javascript const http = require('http'); @@ -46,8 +45,7 @@ Node.js مدل رویداد را کمی به جلوتر می‌برد و [event و در پایان یک سرور را از طریق یک تماس مسدود کننده مانند `EventMachine::run()` اجرا می‌کند. در Node.js چیزی به عنوان فراخوان برای شروع حلقه رویداد وجود ندارد. Node.js پس از اجرای اسکریپت ورودی به حلقه رویداد وارد می‌شود. این رفتار ماننده جاوااسکریپت در مرورگر است - حلقه رویداد از کاربر مخفی می‌ماند. - - + HTTP در Node.js شهروند درجه یک محسوب می‌شود، طراحی شده با درنظر گیری streaming و زمان تأخیر کم. این امر Node.js را به یک گزینه مناسب برای بنیاد کتابخانه وب و یا یک چارچوب تبدیل می‌کند. فقط به خاطر اینکه Node.js بدون Threadها طراحی شده، به این معنی نیست که نتوانید از چند هسته در محیط خود بهره ببرید. فرایند‌های زیرین می‌توانند توسط ‌[`child_process.fork()`][] API اجرا شوند. فرایند های زیرین به شکلی طراحی شده‌اند که تعامل کردن با آن‌ها به سادگی انجام شود. diff --git a/locale/fa/docs/guides/anatomy-of-an-http-transaction.md b/locale/fa/docs/guides/anatomy-of-an-http-transaction.md index 289514b9c5537..e7cdb03e47bf4 100644 --- a/locale/fa/docs/guides/anatomy-of-an-http-transaction.md +++ b/locale/fa/docs/guides/anatomy-of-an-http-transaction.md @@ -401,8 +401,6 @@ From these basics, Node.js HTTP servers for many typical use cases can be constructed. There are plenty of other things these APIs provide, so be sure to read through the API docs for [`EventEmitters`][], [`Streams`][], and [`HTTP`][]. - - [`EventEmitters`]: https://nodejs.org/api/events.html [`Streams`]: https://nodejs.org/api/stream.html [`createServer`]: https://nodejs.org/api/http.html#http_http_createserver_requestlistener diff --git a/locale/fa/docs/guides/backpressuring-in-streams.md b/locale/fa/docs/guides/backpressuring-in-streams.md index a03622f9a6f12..1444a2e871243 100644 --- a/locale/fa/docs/guides/backpressuring-in-streams.md +++ b/locale/fa/docs/guides/backpressuring-in-streams.md @@ -592,7 +592,6 @@ Be sure to read up more on [`Stream`][] for other API functions to help improve and unleash your streaming capabilities when building an application with Node.js. - [`Stream`]: https://nodejs.org/api/stream.html [`Buffer`]: https://nodejs.org/api/buffer.html [`EventEmitters`]: https://nodejs.org/api/events.html diff --git a/locale/fa/docs/guides/blocking-vs-non-blocking.md b/locale/fa/docs/guides/blocking-vs-non-blocking.md index 94d8cf98a9c0a..4a3a25db5424b 100644 --- a/locale/fa/docs/guides/blocking-vs-non-blocking.md +++ b/locale/fa/docs/guides/blocking-vs-non-blocking.md @@ -13,7 +13,6 @@ basic understanding of the JavaScript language and Node.js callback pattern. > "I/O" refers primarily to interaction with the system's disk and > network supported by [libuv](https://libuv.org/). - ## Blocking **Blocking** is when the execution of additional JavaScript in the Node.js @@ -32,7 +31,6 @@ versions, which are **non-blocking**, and accept callback functions. Some methods also have **blocking** counterparts, which have names that end with `Sync`. - ## Comparing Code **Blocking** methods execute **synchronously** and **non-blocking** methods @@ -87,7 +85,6 @@ can continue and `moreWork()` will be called first. The ability to run `moreWork()` without waiting for the file read to complete is a key design choice that allows for higher throughput. - ## Concurrency and Throughput JavaScript execution in Node.js is single threaded, so concurrency refers to the @@ -106,7 +103,6 @@ capacity just by choosing to use **non-blocking** methods instead of The event loop is different than models in many other languages where additional threads may be created to handle concurrent work. - ## Dangers of Mixing Blocking and Non-Blocking Code There are some patterns that should be avoided when dealing with I/O. Let's look @@ -126,7 +122,6 @@ In the above example, `fs.unlinkSync()` is likely to be run before better way to write this that is completely **non-blocking** and guaranteed to execute in the correct order is: - ```js const fs = require('fs'); fs.readFile('/file.md', (readFileErr, data) => { @@ -141,7 +136,6 @@ fs.readFile('/file.md', (readFileErr, data) => { The above places a **non-blocking** call to `fs.unlink()` within the callback of `fs.readFile()` which guarantees the correct order of operations. - ## Additional Resources - [libuv](https://libuv.org/) diff --git a/locale/fa/docs/guides/domain-postmortem.md b/locale/fa/docs/guides/domain-postmortem.md index 6426c2a73361a..310d7c7ee2b93 100644 --- a/locale/fa/docs/guides/domain-postmortem.md +++ b/locale/fa/docs/guides/domain-postmortem.md @@ -22,13 +22,11 @@ Here's an example of how one indirectly linked modules can affect another: const b = require('./b'); const c = require('./c'); - // module b.js const d = require('domain').create(); d.on('error', () => { /* silence everything */ }); d.enter(); - // module c.js const dep = require('some-dep'); dep.method(); // Uh-oh! This method doesn't actually exist. @@ -99,7 +97,6 @@ automatically bubble. Unfortunately both these situations occur, leading to potentially confusing behavior that may even be prone to difficult to debug timing conflicts. - ### API Gaps While APIs based on using `EventEmitter` can use `bind()` and errback style @@ -109,7 +106,6 @@ wanted to support domains using a mechanism alternative to those mentioned they must manually implement domain support themselves. Instead of being able to leverage the implicit mechanisms already in place. - ### Error Propagation Propagating errors across nested domains is not straight forward, if even @@ -155,7 +151,6 @@ several asynchronous requests and each one then `write()`'s data back to the client many more errors will arise from attempting to `write()` to a closed handle. More on this in _Resource Cleanup on Exception_. - ### Resource Cleanup on Exception The following script contains a more complex example of properly cleaning up @@ -333,7 +328,6 @@ In the end, in terms of handling errors, domains aren't much more than a glorified `'uncaughtException'` handler. Except with more implicit and unobservable behavior by third-parties. - ### Resource Propagation Another use case for domains was to use it to propagate data along asynchronous @@ -408,7 +402,6 @@ user's callback is called. Also the instantiation of `DataStream` in the In short, for this to have a prayer of a chance usage would need to strictly adhere to a set of guidelines that would be difficult to enforce or test. - ## Performance Issues A significant deterrent from using domains is the overhead. Using node's @@ -433,7 +426,6 @@ will result in a 17% performance loss. Granted, this is for the optimized scenario of the benchmark, but I believe this demonstrates the necessity for a mechanism such as domain to be as cheap to run as possible. - ## Looking Ahead The domain module has been soft deprecated since Dec 2014, but has not yet been diff --git a/locale/fa/docs/guides/event-loop-timers-and-nexttick.md b/locale/fa/docs/guides/event-loop-timers-and-nexttick.md index 53314763fefd7..683bb8bebc2f6 100644 --- a/locale/fa/docs/guides/event-loop-timers-and-nexttick.md +++ b/locale/fa/docs/guides/event-loop-timers-and-nexttick.md @@ -71,7 +71,6 @@ demonstration. The most important parts are here. There are actually seven or eight steps, but the ones we care about — ones that Node.js actually uses - are those above._ - ## Phases Overview * **timers**: this phase executes callbacks scheduled by `setTimeout()` @@ -123,7 +122,6 @@ setTimeout(() => { console.log(`${delay}ms have passed since I was scheduled`); }, 100); - // do someAsyncOperation which takes 95 ms to complete someAsyncOperation(() => { const startCallback = Date.now(); @@ -233,7 +231,6 @@ cycle (i.e. the main module), the order in which the two timers are executed is non-deterministic, as it is bound by the performance of the process: - ```js // timeout_vs_immediate.js setTimeout(() => { diff --git a/locale/fa/docs/guides/index.md b/locale/fa/docs/guides/index.md index da99977b300e8..fd5158b720604 100644 --- a/locale/fa/docs/guides/index.md +++ b/locale/fa/docs/guides/index.md @@ -14,7 +14,6 @@ layout: docs.hbs - [Dockerizing a Node.js web app](nodejs-docker-webapp/) - [Migrating to safe Buffer constructors](buffer-constructor-deprecation/) - ## Node.js core concepts - [Overview of Blocking vs Non-Blocking](blocking-vs-non-blocking/) @@ -22,7 +21,6 @@ layout: docs.hbs - [Don't Block the Event Loop (or the Worker Pool)](dont-block-the-event-loop/) - [Timers in Node.js](timers-in-node/) - ## Module-related guides - [Anatomy of an HTTP Transaction](anatomy-of-an-http-transaction/) diff --git a/locale/fa/download/package-manager.md b/locale/fa/download/package-manager.md index 94c71db1b31e4..cf8adfcf11863 100644 --- a/locale/fa/download/package-manager.md +++ b/locale/fa/download/package-manager.md @@ -47,7 +47,6 @@ Node.js and npm packages are available in the Community Repository. pacman -S nodejs npm ``` - ## Debian and Ubuntu based Linux distributions Also including: **Linux Mint**, **Linux Mint Debian Edition (LMDE)**, **elementaryOS**, **bash on Windows** and others. @@ -253,7 +252,6 @@ Node.js is available in the portage tree. emerge nodejs ``` - ## NetBSD Node.js is available in the pkgsrc tree: @@ -380,7 +378,6 @@ Or build manually from pkgsrc: cd pkgsrc/lang/nodejs && bmake install ``` - ## Void Linux Void Linux ships node.js stable in the main repository. @@ -397,7 +394,6 @@ Solus provides node.js in its main repository. sudo eopkg install nodejs ``` - ## Windows Simply download the [Windows Installer](https://nodejs.org/#download) directly from the [nodejs.org](https://nodejs.org) web site. diff --git a/locale/fa/get-involved/index.md b/locale/fa/get-involved/index.md index 2351bfd3326ea..41eab15a85467 100644 --- a/locale/fa/get-involved/index.md +++ b/locale/fa/get-involved/index.md @@ -14,7 +14,6 @@ layout: contribute.hbs - [Node.js Collection](https://medium.com/the-node-js-collection) is a collection of community-curated content on Medium. - The [Community Committee](https://github.com/nodejs/community-committee) is a top-level committee in the Node.js Foundation focused on community-facing efforts. - ## Learning - [Official API reference documentation](/api/) details the Node API. diff --git a/locale/fa/knowledge/HTTP/clients/how-to-access-query-string-parameters.md b/locale/fa/knowledge/HTTP/clients/how-to-access-query-string-parameters.md index 8538a2874e09a..3ce5db155507d 100644 --- a/locale/fa/knowledge/HTTP/clients/how-to-access-query-string-parameters.md +++ b/locale/fa/knowledge/HTTP/clients/how-to-access-query-string-parameters.md @@ -22,5 +22,3 @@ In Node.js, functionality to aid in the accessing of URL query string parameters }).listen(8080); 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. - - diff --git a/locale/fa/knowledge/HTTP/clients/how-to-create-a-HTTP-request.md b/locale/fa/knowledge/HTTP/clients/how-to-create-a-HTTP-request.md index 29e6003314887..44b9ad4f1f31e 100644 --- a/locale/fa/knowledge/HTTP/clients/how-to-create-a-HTTP-request.md +++ b/locale/fa/knowledge/HTTP/clients/how-to-create-a-HTTP-request.md @@ -36,7 +36,6 @@ As an example, we are going to preform a GET request to [www.random.org/integers http.request(options, callback).end(); - Making a POST request is just as easy. We will make a POST request to `www.nodejitsu.com:1337` which is running a server that will echo back what we post. The code for making a POST request is almost identical to making a GET request, just a few simple modifications: var http = require('http'); diff --git a/locale/fa/knowledge/HTTP/servers/how-to-read-POST-data.md b/locale/fa/knowledge/HTTP/servers/how-to-read-POST-data.md index 132a049b7fd7b..494aeb5f81c99 100644 --- a/locale/fa/knowledge/HTTP/servers/how-to-read-POST-data.md +++ b/locale/fa/knowledge/HTTP/servers/how-to-read-POST-data.md @@ -41,4 +41,3 @@ With the HTML out of the way, we [create a server](/how-do-i-create-a-http-serve Something important to note is that the event listeners are being added immediately after the request object is received. If you don't immediately set them, then there is a possibility of missing some of the events. If, for example, an event listener was attached from inside a callback, then the `data` and `end` events might be fired in the meantime with no listeners attached! You can save this script to `server.js` and run it with `node server.js`. Once you run it you will notice that occasionally you will see lines with no data, e.g. `POSTed:`. This happens because regular `GET` requests go through the same codepath. In a more 'real-world' application, it would be proper practice to check the type of request and handle the different request types differently. - diff --git a/locale/fa/knowledge/advanced/streams/how-to-use-fs-create-read-stream.md b/locale/fa/knowledge/advanced/streams/how-to-use-fs-create-read-stream.md index d0a4823c575b1..db4464bad2168 100644 --- a/locale/fa/knowledge/advanced/streams/how-to-use-fs-create-read-stream.md +++ b/locale/fa/knowledge/advanced/streams/how-to-use-fs-create-read-stream.md @@ -32,4 +32,3 @@ The function `fs.createReadStream()` allows you to open up a readable stream in res.end(err); }); }).listen(8080); - diff --git a/locale/fa/knowledge/advanced/streams/what-are-streams.md b/locale/fa/knowledge/advanced/streams/what-are-streams.md index 777af6c9ff2ca..977c15bbd1039 100644 --- a/locale/fa/knowledge/advanced/streams/what-are-streams.md +++ b/locale/fa/knowledge/advanced/streams/what-are-streams.md @@ -39,5 +39,4 @@ Run this script with arguments like `node cp.js src.txt dest.txt`. This would me console.log("ERROR", err); }); - This sets up a readable stream from the source file and a writable stream to the destination file. Then whenever the readable stream gets data, it gets written to the writeable stream. Then finally it closes the writable stream when the readable stream is finished. NOTE: it would have been better to use [pipe](/how-to-use-stream-pipe) like `readStream.pipe(writeStream);`, however, to show how streams work, we have done things the long way. diff --git a/locale/fa/knowledge/child-processes/how-to-spawn-a-child-process.md b/locale/fa/knowledge/child-processes/how-to-spawn-a-child-process.md index f8e5b7f7a7bae..fb05d9b25dc71 100644 --- a/locale/fa/knowledge/child-processes/how-to-spawn-a-child-process.md +++ b/locale/fa/knowledge/child-processes/how-to-spawn-a-child-process.md @@ -34,5 +34,3 @@ NODE PRO TIP: `error.stack` is a stack trace to the point that the [Error object 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. 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. - - diff --git a/locale/fa/knowledge/command-line/how-to-prompt-for-command-line-input.md b/locale/fa/knowledge/command-line/how-to-prompt-for-command-line-input.md index c64fdec2e3581..db68702a5ed7d 100644 --- a/locale/fa/knowledge/command-line/how-to-prompt-for-command-line-input.md +++ b/locale/fa/knowledge/command-line/how-to-prompt-for-command-line-input.md @@ -32,7 +32,6 @@ Here's a simple example. Try the following in a new file: console.log('Now that process.stdin is paused, there is nothing more to do.'); process.exit(); } - If all of this sounds complicated, or if you want a higher-level interface to this sort of thing, don't worry - as usual, the Node.js community has come to the rescue. One particularly friendly module to use for this is Prompt, maintained by Nodejitsu. It's available on `npm`: diff --git a/locale/fa/knowledge/cryptography/how-to-use-the-tls-module.md b/locale/fa/knowledge/cryptography/how-to-use-the-tls-module.md index 689d5d5d3a9f4..57d7fc0c5250a 100644 --- a/locale/fa/knowledge/cryptography/how-to-use-the-tls-module.md +++ b/locale/fa/knowledge/cryptography/how-to-use-the-tls-module.md @@ -51,7 +51,6 @@ In most ways, the tls module's server api is similar to that of the net module. s.pipe(s); }).listen(8000); - In this example, a "hello world" tls server is created, listening on port 8000. The options object includes two properties: `key` and `cert`. The contents of these properties come directly from the private key and public certificate stored on the filesystem. In this case they are binary buffers, but the tls module can also accept unicode strings. ### Generating Your Private Key And Certificate With OpenSSL: @@ -131,8 +130,6 @@ The tls module also supplies tools for connecting to such a server: console.log(); }); - - conn.on("data", function (data) { console.log(data.toString()); conn.end(); diff --git a/locale/fa/knowledge/file-system/how-to-search-files-and-directories-in-nodejs.md b/locale/fa/knowledge/file-system/how-to-search-files-and-directories-in-nodejs.md index a708eb556f33a..ea4225f60f86e 100644 --- a/locale/fa/knowledge/file-system/how-to-search-files-and-directories-in-nodejs.md +++ b/locale/fa/knowledge/file-system/how-to-search-files-and-directories-in-nodejs.md @@ -19,7 +19,6 @@ Suppose you want to list all the files in the current directory. One approach i console.log(files); }); - 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). To install `node-findit`, simply use npm: diff --git a/locale/fa/knowledge/file-system/how-to-store-local-config-data.md b/locale/fa/knowledge/file-system/how-to-store-local-config-data.md index e285bce5c0bb5..52a298af08e5d 100644 --- a/locale/fa/knowledge/file-system/how-to-store-local-config-data.md +++ b/locale/fa/knowledge/file-system/how-to-store-local-config-data.md @@ -81,4 +81,3 @@ After that, the syntax is a breeze. Have a look at an example: The only tricky thing to notice here is the delimiter - ':'. When accessing nested properties with `nconf`, a colon is used to delimit the namespaces of key names. If a specific sub-key is not provided, the whole object is set or returned. When using `nconf` to store your configuration data to a file, `nconf.save()` and `nconf.load()` are the only times that any actual file interaction will happen. All other access is performed on an in-memory copy of your data, which will not persist without a call to `nconf.save()`. Similarly, if you're trying to bring back configuration data from the last time your application ran, it will not exist in memory without a call to `nconf.load()`, as shown above. - diff --git a/locale/fa/knowledge/file-system/how-to-use-the-path-module.md b/locale/fa/knowledge/file-system/how-to-use-the-path-module.md index 584f0ff4583dd..e3e9bb0ef4225 100644 --- a/locale/fa/knowledge/file-system/how-to-use-the-path-module.md +++ b/locale/fa/knowledge/file-system/how-to-use-the-path-module.md @@ -65,4 +65,3 @@ Blocking isn't always a bad thing. Checking the existence of a vital configurat > path.existsSync('/etc') true - diff --git a/locale/fa/knowledge/getting-started/control-flow/how-to-write-asynchronous-code.md b/locale/fa/knowledge/getting-started/control-flow/how-to-write-asynchronous-code.md index 5f78d1a2e0c3c..1cf257406d513 100644 --- a/locale/fa/knowledge/getting-started/control-flow/how-to-write-asynchronous-code.md +++ b/locale/fa/knowledge/getting-started/control-flow/how-to-write-asynchronous-code.md @@ -37,7 +37,6 @@ The asynchronous version, on the other hand, does not stop time - instead, the c When only reading a file or two, or saving something quickly, the difference between synchronous and asynchronous file I/O can be quite small. On the other hand, though, when you have multiple requests coming in per second that require file or database IO, trying to do that IO synchronously would be quite thoroughly disastrous for performance. - ### Callbacks Callbacks are a basic idiom in node.js for asynchronous operations. When most people talk about callbacks, they mean the function that is passed as the last parameter to an asynchronous function. The callback is then later called with any return value or error message that the function produced. For more details, see the article on [callbacks](/fa/knowledge/getting-started/control-flow/what-are-callbacks) diff --git a/locale/fa/knowledge/getting-started/control-flow/what-are-event-emitters.md b/locale/fa/knowledge/getting-started/control-flow/what-are-event-emitters.md index e75dd5a496d35..7428ca375712f 100644 --- a/locale/fa/knowledge/getting-started/control-flow/what-are-event-emitters.md +++ b/locale/fa/knowledge/getting-started/control-flow/what-are-event-emitters.md @@ -99,4 +99,3 @@ If you want remove a specific callback, you can use `removeListener`. If you wan false NOTE: If you want create more than 10 listeners on a single event, you will have to make a call to `ee.setMaxListeners(n)` where n is the max numbers of listeners (with zero being unlimited number of listeners). This is used to make sure you aren't accidentally leaking event listeners. - diff --git a/locale/fa/knowledge/getting-started/how-to-debug-nodejs-applications.md b/locale/fa/knowledge/getting-started/how-to-debug-nodejs-applications.md index f20cdc8d67c4f..69e0ab0145409 100644 --- a/locale/fa/knowledge/getting-started/how-to-debug-nodejs-applications.md +++ b/locale/fa/knowledge/getting-started/how-to-debug-nodejs-applications.md @@ -9,7 +9,6 @@ layout: knowledge-post.hbs Often times, not just in the Node.js community but in software at large, people debug simply with a liberal sprinkle of standard output statements. This allows you to track down where unexpected values are being generated. However, this method can be tedious, or worse yet, not robust enough to detect the real problem. - ### Set up Thankfully, through the use of `node-inspector`, we can harness to power of the webkit-debuggers to work with our node.js code. The process itself is simple. diff --git a/locale/fa/knowledge/getting-started/how-to-use-util-inspect.md b/locale/fa/knowledge/getting-started/how-to-use-util-inspect.md index 9f9844ddebd74..fcbd433e6f60c 100644 --- a/locale/fa/knowledge/getting-started/how-to-use-util-inspect.md +++ b/locale/fa/knowledge/getting-started/how-to-use-util-inspect.md @@ -46,4 +46,3 @@ Finally, the optional argument `colorize` is a boolean that adds ANSI escape cod var util = require('util'); console.log(util.inspect({a:1, b:"b"}, false,2,true)); - diff --git a/locale/fa/knowledge/getting-started/npm/what-is-npm.md b/locale/fa/knowledge/getting-started/npm/what-is-npm.md index 54f24d3b2676c..02508ca6f8977 100644 --- a/locale/fa/knowledge/getting-started/npm/what-is-npm.md +++ b/locale/fa/knowledge/getting-started/npm/what-is-npm.md @@ -9,7 +9,6 @@ layout: knowledge-post.hbs `npm`, short for Node Package Manager, is two things: first and foremost, it is an online repository for the publishing of open-source Node.js projects; second, it is a command-line utility for interacting with said repository that aids in package installation, version management, and dependency management. A plethora of node.js libraries and applications are published on npm, and many more are added every day. These applications can be searched for on http://search.npmjs.org/. Once you have a package you want to install, it can be installed with a single command-line command. - Let's say you're hard at work one day, developing the Next Great Application. You come across a problem, and you decide that it's time to use that cool library you keep hearing about - let's use Caolan McMahon's [async](https://github.com/caolan/async) as an example. Thankfully, `npm` is very simple to use: you only have to run `npm install async`, and the specified module will be installed in the current directory under `./node_modules/`. Once installed to your `node_modules` folder, you'll be able to use `require()` on them just like they were built-ins. Let's look at an example of a global install - let's say `coffee-script`. The npm command is simple: `npm install coffee-script -g`. This will typically install the program and put a symlink to it in `/usr/local/bin/`. This will then allow you to run the program from the console just like any other CLI tool. In this case, running `coffee` will now allow you to use the coffee-script REPL. @@ -23,4 +22,3 @@ Example: npm install After running those commands, you will see a `node_modules` folder containing all of the project dependencies specified in the package.json. - diff --git a/locale/fa/knowledge/getting-started/what-is-require.md b/locale/fa/knowledge/getting-started/what-is-require.md index 8f5367b00ca45..f79b5a472f175 100644 --- a/locale/fa/knowledge/getting-started/what-is-require.md +++ b/locale/fa/knowledge/getting-started/what-is-require.md @@ -51,10 +51,8 @@ It is worth noting that each time you subsequently require an already-required f node> require('./example.js') //One might think that this "reloads" the file... { message: 'hey', say: [Function] } //...but the message is still "hey" because of the module cache. - As you can see from the above, `example.js` is evaluated the first time, but all subsequent calls to `require()` only invoke the module cache, rather than reading the file again. As seen above, this can occasionally produce side effects. The rules of where `require` finds the files can be a little complex, but a simple rule of thumb is that if the file doesn't start with "./" or "/", then it is either considered a core module (and the local Node path is checked), or a dependency in the local `node_modules` folder. If the file starts with "./" it is considered a relative file to the file that called `require`. If the file starts with "/", it is considered an absolute path. NOTE: you can omit ".js" and `require` will automatically append it if needed. For more detailed information, see [the official docs](https://nodejs.org/docs/v0.4.2/api/modules.htmll#all_Together...) An extra note: if the filename passed to `require` is actually a directory, it will first look for `package.json` in the directory and load the file referenced in the `main` property. Otherwise, it will look for an `index.js`. - diff --git a/locale/fa/knowledge/javascript-conventions/how-to-create-default-parameters-for-functions.md b/locale/fa/knowledge/javascript-conventions/how-to-create-default-parameters-for-functions.md index c522dac0eca75..563fe0524a07b 100644 --- a/locale/fa/knowledge/javascript-conventions/how-to-create-default-parameters-for-functions.md +++ b/locale/fa/knowledge/javascript-conventions/how-to-create-default-parameters-for-functions.md @@ -36,7 +36,6 @@ The first idiom is giving a default value for the last parameter. This is done b example(""); betterExample(""); - If the optional value is in the middle it can cause some undesired effects, since all the parameters are shifted over. The optional parameter is not the `undefined` value in this case - the last parameter is the `undefined` one. So you have to check if the last parameter is `undefined` and then manually fix all the other parameters before continuing in the code. This example shows you how to do that: example = function (param1, optParam, callback) { diff --git a/locale/fa/knowledge/javascript-conventions/what-are-the-built-in-timer-functions.md b/locale/fa/knowledge/javascript-conventions/what-are-the-built-in-timer-functions.md index 1159525e33f7e..e4b0de6d6f07c 100644 --- a/locale/fa/knowledge/javascript-conventions/what-are-the-built-in-timer-functions.md +++ b/locale/fa/knowledge/javascript-conventions/what-are-the-built-in-timer-functions.md @@ -58,7 +58,6 @@ The final trick for the timer objects is you can pass parameters to the callback setTimeout(console.log, 1000, "This", "has", 4, "parameters"); setInterval(console.log, 1000, "This only has one"); - This has 4 parameters This only has one This only has one diff --git a/locale/fa/security.md b/locale/fa/security.md index e1932c1a04b2e..b95788ee922dd 100644 --- a/locale/fa/security.md +++ b/locale/fa/security.md @@ -9,12 +9,10 @@ title: امنیت تمامی مشکلات امنیتی در Node.js جدی گرفته می‌شوند و باید از طریق [HackerOne](https://hackerone.com/nodejs) یا رایانامه [security@nodejs.org](mailto:security@nodejs.org) گزارش داده شوند. این گزارش به زیر مجموعه‌ای از تیم هسته Node.js که مسئول رفع کردن مشکلات امنیتی هستند تحویل داده خواهد شد. - گزارش شما حداکثر تا ۲۴ ساعت تصدیق خوهد شد و حداکثر تا ۴۸ ساعت پاسخ دقیقی به گزارش خود دریافت خواهید کرد که نشان خواهد داد کام های بعدی در رسیدگی به درخواست شما چیست. پس از پاسخ اولیه به گزارش شما، تیم امنیتی تلاش خواهد کرد تا شما را از پیشرفت کار در جهت یک اعلامیه کامل و تعمیر مطلع سازد و ممکن است از شما در رابطه با اطلاعات تکمیلی یا راهنمایی در حیطه مسئله گزارش شده سوال پرسیده شود. این به‌روزرسانی حداقل هر پنج روز یک بار ارسال خواهد شد. اما در عمل امکان بیشتری وجود دارد که هر ۲۴ تا ۴۸ ساعت یک بار ارسال شوند. - ### برنامه جایزه پیدا کردن باگ در Node.js پروژه Node.js در یک برنامه رسمی جایزه برای باگ شرکت می‌کند که برای فعالان امنیتی و افشاهای عمومی است. @@ -24,7 +22,6 @@ title: امنیت ## گزارش باگ در ماژول‌های سوم شخص گزارش‌های باگ در ماژول‌های سوم شخص باید به نگاه دارندگان آن ها اعلام شود و همجنین باید از طریق [تیم اکو سیستم Node](https://hackerone.com/nodejs-ecosystem) رایانامه [security-ecosystem@nodejs.org](mailto:security-ecosystem@nodejs.org) اعلام شود. - اطلاعات بیشتر در رابطه با این فرایند را می‌توانید در [مخزن گروه کاری امینت](https://github.com/nodejs/security-wg/blob/master/processes/third_party_vuln_process.md). پیدا کنید. @@ -32,7 +29,6 @@ title: امنیت از شما بابت بهتر کردن امنیت Node.js و اکوسیستم آن متشکریم. از تلاش‌ها و فاش‌سازی مسئولانه شما بسیار استقبال میکنیم و متوجه آن خواهیم بود. - ## سیاست افشاگری - گزارش امنیتی دریافت و سپس به یک رسیدگی کننده اصلی محول خواهد شد. این شخص مختصات تعمیر را مشخص و منتشر خواهد کرد. @@ -46,16 +42,13 @@ title: امنیت تغییرات به مخزن عمومی اعمال خواهند شد و ساخت های جدید در nodejs.org مستقر خواهند شد. ظرف مدت ۶ ساعت از اطلاع‌رسانی به فهرست رایانامه، یک رونویس از مشاوره بر روی بلاگ Node.js منتشر خواهد شد. - - به طور معمول تاریخ منع ۷۲ ساعت پس از ثبت CVE تنظیم خواهد شد. با این حال، این ممکن است به نسبت به شدت اشکال یا سختی تعمیر، متفاوت باشد. - - این فرایند ممکن است کمی زمان ببرد، مخصوصاً زمانی که هماهنگی با نگهدارندگان پروژه‌های دیگر نیاز است. تلاش خواهد شد تا باگ‌ها در سریع‌ترین حالت ممکن رسیدگی شوند. با این حال مهم است که ما فرایند انتشار بالا را تا پیدا کردن یک راه مشخص برای رفع مشکل دنبال کنیم. ## دریافت به‌روزرسانی‌های امنیتی - اعلان‌های امنیتی به روش‌های زیر توزیع خواهند شد. - [گروه گوگل https://groups.google.com/group/nodejs-sec](https://groups.google.com/group/nodejs-sec) diff --git a/locale/fr/get-involved/index.md b/locale/fr/get-involved/index.md index 2ac14bc285de1..faf55b3648959 100644 --- a/locale/fr/get-involved/index.md +++ b/locale/fr/get-involved/index.md @@ -21,7 +21,6 @@ layout: contribute.hbs - La [Community Committee](https://github.com/nodejs/community-committee) s'agit d'un comité de haut niveau de la Fondation Node.js axé sur les efforts communautaires. - ## Apprentissage - [La documentation officielle de l'API de référence](/api/) détaille l'API Node (en anglais). @@ -36,7 +35,6 @@ layout: contribute.hbs - [How To Node](http://howtonode.org/) a de nombreux tutoriaux utiles (en anglais). - ## Site et projets des commuanutés internationales - [communauté chinoise](https://cnodejs.org/) diff --git a/locale/fr/security.md b/locale/fr/security.md index cbb71622e18b4..47b33fa6bea0c 100644 --- a/locale/fr/security.md +++ b/locale/fr/security.md @@ -43,7 +43,6 @@ Voici la politique de divulgation des failles de sécurité pour Node.js : - Ce processus peut prendre du temps, surtout lorsqu'il requiert une coordination avec des personnes qui maintiennent d'autres projets. Tous les efforts possibles seront mis en œuvre pour résoudre la faille aussi vite que possible ; toutefois, il est important que nous suivions la procédure ci-dessus pour nous assurer que la divulgation s'effectue de la manière la plus responsable possible. - ## Recevoir les alertes de sécurité Les alertes de sécurité sont relayées sur les canaux suivants. diff --git a/locale/gl/security.md b/locale/gl/security.md index e55998e0b13b2..76d2cde27d33f 100644 --- a/locale/gl/security.md +++ b/locale/gl/security.md @@ -56,7 +56,6 @@ As notificacións de seguridade serán distribuídas usando os seguintes medios. - - - ## Comentarios sobre esta política Se tes suxerencias sobre como este proceso podería ser mellorado, por favor envíe un [pull request](https://github.com/nodejs/nodejs.org) diff --git a/locale/it/about/index.md b/locale/it/about/index.md index 6bff8ffe28ee4..d63ce757260f6 100644 --- a/locale/it/about/index.md +++ b/locale/it/about/index.md @@ -10,7 +10,6 @@ Come runtime JavaScript guidato da eventi asincroni, Node.js è progettato per creare applicazioni di rete scalabili. Nel seguente esempio "Hello World", molte connessioni possono essere gestite contemporaneamente. Ad ogni connessione viene chiamata la callback, ma se non c'è nulla da fare, Node.js rimarrà inattivo. - ```javascript const http = require('http'); @@ -36,8 +35,6 @@ blocco permanente del processo, poiché non ci sono blocchi. Quasi nessuna funzi esegue direttamente I/O, quindi il processo non blocca mai. Dal momento che nulla si blocca, è molto facile sviluppare sistemi scalabili in Node.js - - Se alcuni dei termini utilizzati non ti sono familiari, ecco un articolo completo (in inglese) [Bloccante vs Non Bloccante][]. @@ -58,7 +55,6 @@ HTTP ha un posto di rilievo in Node.js, che è stato progettato per lo streaming Solo perché Node.js è progettato senza thread, non significa che non è possibile sfruttare i multi-core nel proprio ambiente. I processi figlio possono essere generati utilizzando la API [`child_process.fork()`][], con cui è possibile comunicare facilmente. Costruito sulla stessa interfaccia è il modulo [`cluster`][], che consente di condividere i socket tra i processi per consentire il bilanciamento del carico sui core. - [Bloccante vs Non Bloccante]: https://nodejs.org/en/docs/guides/blocking-vs-non-blocking/ [`child_process.fork()`]: https://nodejs.org/api/child_process.html#child_process_child_process_fork_modulepath_args_options [`cluster`]: https://nodejs.org/api/cluster.html diff --git a/locale/it/docs/guides/anatomy-of-an-http-transaction.md b/locale/it/docs/guides/anatomy-of-an-http-transaction.md index 289514b9c5537..e7cdb03e47bf4 100644 --- a/locale/it/docs/guides/anatomy-of-an-http-transaction.md +++ b/locale/it/docs/guides/anatomy-of-an-http-transaction.md @@ -401,8 +401,6 @@ From these basics, Node.js HTTP servers for many typical use cases can be constructed. There are plenty of other things these APIs provide, so be sure to read through the API docs for [`EventEmitters`][], [`Streams`][], and [`HTTP`][]. - - [`EventEmitters`]: https://nodejs.org/api/events.html [`Streams`]: https://nodejs.org/api/stream.html [`createServer`]: https://nodejs.org/api/http.html#http_http_createserver_requestlistener diff --git a/locale/it/docs/guides/backpressuring-in-streams.md b/locale/it/docs/guides/backpressuring-in-streams.md index a03622f9a6f12..1444a2e871243 100644 --- a/locale/it/docs/guides/backpressuring-in-streams.md +++ b/locale/it/docs/guides/backpressuring-in-streams.md @@ -592,7 +592,6 @@ Be sure to read up more on [`Stream`][] for other API functions to help improve and unleash your streaming capabilities when building an application with Node.js. - [`Stream`]: https://nodejs.org/api/stream.html [`Buffer`]: https://nodejs.org/api/buffer.html [`EventEmitters`]: https://nodejs.org/api/events.html diff --git a/locale/it/docs/guides/blocking-vs-non-blocking.md b/locale/it/docs/guides/blocking-vs-non-blocking.md index 94d8cf98a9c0a..4a3a25db5424b 100644 --- a/locale/it/docs/guides/blocking-vs-non-blocking.md +++ b/locale/it/docs/guides/blocking-vs-non-blocking.md @@ -13,7 +13,6 @@ basic understanding of the JavaScript language and Node.js callback pattern. > "I/O" refers primarily to interaction with the system's disk and > network supported by [libuv](https://libuv.org/). - ## Blocking **Blocking** is when the execution of additional JavaScript in the Node.js @@ -32,7 +31,6 @@ versions, which are **non-blocking**, and accept callback functions. Some methods also have **blocking** counterparts, which have names that end with `Sync`. - ## Comparing Code **Blocking** methods execute **synchronously** and **non-blocking** methods @@ -87,7 +85,6 @@ can continue and `moreWork()` will be called first. The ability to run `moreWork()` without waiting for the file read to complete is a key design choice that allows for higher throughput. - ## Concurrency and Throughput JavaScript execution in Node.js is single threaded, so concurrency refers to the @@ -106,7 +103,6 @@ capacity just by choosing to use **non-blocking** methods instead of The event loop is different than models in many other languages where additional threads may be created to handle concurrent work. - ## Dangers of Mixing Blocking and Non-Blocking Code There are some patterns that should be avoided when dealing with I/O. Let's look @@ -126,7 +122,6 @@ In the above example, `fs.unlinkSync()` is likely to be run before better way to write this that is completely **non-blocking** and guaranteed to execute in the correct order is: - ```js const fs = require('fs'); fs.readFile('/file.md', (readFileErr, data) => { @@ -141,7 +136,6 @@ fs.readFile('/file.md', (readFileErr, data) => { The above places a **non-blocking** call to `fs.unlink()` within the callback of `fs.readFile()` which guarantees the correct order of operations. - ## Additional Resources - [libuv](https://libuv.org/) diff --git a/locale/it/docs/guides/domain-postmortem.md b/locale/it/docs/guides/domain-postmortem.md index 6426c2a73361a..310d7c7ee2b93 100644 --- a/locale/it/docs/guides/domain-postmortem.md +++ b/locale/it/docs/guides/domain-postmortem.md @@ -22,13 +22,11 @@ Here's an example of how one indirectly linked modules can affect another: const b = require('./b'); const c = require('./c'); - // module b.js const d = require('domain').create(); d.on('error', () => { /* silence everything */ }); d.enter(); - // module c.js const dep = require('some-dep'); dep.method(); // Uh-oh! This method doesn't actually exist. @@ -99,7 +97,6 @@ automatically bubble. Unfortunately both these situations occur, leading to potentially confusing behavior that may even be prone to difficult to debug timing conflicts. - ### API Gaps While APIs based on using `EventEmitter` can use `bind()` and errback style @@ -109,7 +106,6 @@ wanted to support domains using a mechanism alternative to those mentioned they must manually implement domain support themselves. Instead of being able to leverage the implicit mechanisms already in place. - ### Error Propagation Propagating errors across nested domains is not straight forward, if even @@ -155,7 +151,6 @@ several asynchronous requests and each one then `write()`'s data back to the client many more errors will arise from attempting to `write()` to a closed handle. More on this in _Resource Cleanup on Exception_. - ### Resource Cleanup on Exception The following script contains a more complex example of properly cleaning up @@ -333,7 +328,6 @@ In the end, in terms of handling errors, domains aren't much more than a glorified `'uncaughtException'` handler. Except with more implicit and unobservable behavior by third-parties. - ### Resource Propagation Another use case for domains was to use it to propagate data along asynchronous @@ -408,7 +402,6 @@ user's callback is called. Also the instantiation of `DataStream` in the In short, for this to have a prayer of a chance usage would need to strictly adhere to a set of guidelines that would be difficult to enforce or test. - ## Performance Issues A significant deterrent from using domains is the overhead. Using node's @@ -433,7 +426,6 @@ will result in a 17% performance loss. Granted, this is for the optimized scenario of the benchmark, but I believe this demonstrates the necessity for a mechanism such as domain to be as cheap to run as possible. - ## Looking Ahead The domain module has been soft deprecated since Dec 2014, but has not yet been diff --git a/locale/it/docs/guides/event-loop-timers-and-nexttick.md b/locale/it/docs/guides/event-loop-timers-and-nexttick.md index 53314763fefd7..683bb8bebc2f6 100644 --- a/locale/it/docs/guides/event-loop-timers-and-nexttick.md +++ b/locale/it/docs/guides/event-loop-timers-and-nexttick.md @@ -71,7 +71,6 @@ demonstration. The most important parts are here. There are actually seven or eight steps, but the ones we care about — ones that Node.js actually uses - are those above._ - ## Phases Overview * **timers**: this phase executes callbacks scheduled by `setTimeout()` @@ -123,7 +122,6 @@ setTimeout(() => { console.log(`${delay}ms have passed since I was scheduled`); }, 100); - // do someAsyncOperation which takes 95 ms to complete someAsyncOperation(() => { const startCallback = Date.now(); @@ -233,7 +231,6 @@ cycle (i.e. the main module), the order in which the two timers are executed is non-deterministic, as it is bound by the performance of the process: - ```js // timeout_vs_immediate.js setTimeout(() => { diff --git a/locale/it/docs/guides/index.md b/locale/it/docs/guides/index.md index 1592c62a3c0bc..3886e2d51709e 100644 --- a/locale/it/docs/guides/index.md +++ b/locale/it/docs/guides/index.md @@ -14,7 +14,6 @@ layout: docs.hbs - [Dockerizing a Node.js web app](nodejs-docker-webapp/) - [Migrating to safe Buffer constructors](buffer-constructor-deprecation/) - ## Node.js core concepts - [Overview of Blocking vs Non-Blocking](blocking-vs-non-blocking/) @@ -22,7 +21,6 @@ layout: docs.hbs - [Don't Block the Event Loop (or the Worker Pool)](dont-block-the-event-loop/) - [Timers in Node.js](timers-in-node/) - ## Module related guides - [Anatomy of an HTTP Transaction](anatomy-of-an-http-transaction/) diff --git a/locale/it/download/package-manager.md b/locale/it/download/package-manager.md index d7fa4cd27198f..9aea2284a4e4c 100644 --- a/locale/it/download/package-manager.md +++ b/locale/it/download/package-manager.md @@ -48,7 +48,6 @@ Node.js and npm packages are available in the Community Repository. pacman -S nodejs npm ``` - ## Debian and Ubuntu based Linux distributions Also including: **Linux Mint**, **Linux Mint Debian Edition (LMDE)**, **elementaryOS**, **bash on Windows** and others. @@ -254,7 +253,6 @@ Node.js is available in the portage tree. emerge nodejs ``` - ## NetBSD Node.js is available in the pkgsrc tree: @@ -381,7 +379,6 @@ Or build manually from pkgsrc: cd pkgsrc/lang/nodejs && bmake install ``` - ## Void Linux Void Linux ships node.js stable in the main repository. @@ -398,7 +395,6 @@ Solus provides node.js in its main repository. sudo eopkg install nodejs ``` - ## Windows Simply download the [Windows Installer](https://nodejs.org/#download) directly from the [nodejs.org](https://nodejs.org) web site. diff --git a/locale/it/get-involved/index.md b/locale/it/get-involved/index.md index 9e127110e3425..ba8a982e6e8e2 100644 --- a/locale/it/get-involved/index.md +++ b/locale/it/get-involved/index.md @@ -15,7 +15,6 @@ layout: contribute.hbs - [Node.js Collection](https://medium.com/the-node-js-collection) is a collection of community-curated content on Medium. - The [Community Committee](https://github.com/nodejs/community-committee) is a top-level committee in the Node.js Foundation focused on community-facing efforts. - ## Learning - [Official API reference documentation](/api/) details the Node.js API. diff --git a/locale/it/security.md b/locale/it/security.md index f623023b5c57e..36f8b94defec0 100644 --- a/locale/it/security.md +++ b/locale/it/security.md @@ -43,7 +43,6 @@ Queste fix non sono pubblicate nel repository ma piuttosto mantenute localmente - Questo processo può richiedere del tempo, specialmente nel momento in cui è richiesto un coordinamento con i manutentori di altri progetti. Ogni sforzo verrà fatto per gestire il bug nella maniera più rapida possibile; d'altro canto, è importante che noi seguiamo il processo di rilascio sovrastante per assicurare che la scoperta venga gestita in modo coerente. - ## Ricezione aggiornamenti di sicurezza Le notifiche di sicurezza verranno distribuite nei seguenti modi. @@ -54,4 +53,3 @@ Le notifiche di sicurezza verranno distribuite nei seguenti modi. ## Commenti su questa Politica Se hai suggerimenti su come questo processo potrebbe essere migliorato per favore invia una [pull request](https://github.com/nodejs/nodejs.org) o [crea una segnalazione](https://github.com/nodejs/security-wg/issues/new) per discuterne. - diff --git a/locale/ja/docs/guides/anatomy-of-an-http-transaction.md b/locale/ja/docs/guides/anatomy-of-an-http-transaction.md index 289514b9c5537..e7cdb03e47bf4 100644 --- a/locale/ja/docs/guides/anatomy-of-an-http-transaction.md +++ b/locale/ja/docs/guides/anatomy-of-an-http-transaction.md @@ -401,8 +401,6 @@ From these basics, Node.js HTTP servers for many typical use cases can be constructed. There are plenty of other things these APIs provide, so be sure to read through the API docs for [`EventEmitters`][], [`Streams`][], and [`HTTP`][]. - - [`EventEmitters`]: https://nodejs.org/api/events.html [`Streams`]: https://nodejs.org/api/stream.html [`createServer`]: https://nodejs.org/api/http.html#http_http_createserver_requestlistener diff --git a/locale/ja/docs/guides/backpressuring-in-streams.md b/locale/ja/docs/guides/backpressuring-in-streams.md index a03622f9a6f12..1444a2e871243 100644 --- a/locale/ja/docs/guides/backpressuring-in-streams.md +++ b/locale/ja/docs/guides/backpressuring-in-streams.md @@ -592,7 +592,6 @@ Be sure to read up more on [`Stream`][] for other API functions to help improve and unleash your streaming capabilities when building an application with Node.js. - [`Stream`]: https://nodejs.org/api/stream.html [`Buffer`]: https://nodejs.org/api/buffer.html [`EventEmitters`]: https://nodejs.org/api/events.html diff --git a/locale/ja/docs/guides/blocking-vs-non-blocking.md b/locale/ja/docs/guides/blocking-vs-non-blocking.md index 7312ee76716fb..a275ffed2933f 100644 --- a/locale/ja/docs/guides/blocking-vs-non-blocking.md +++ b/locale/ja/docs/guides/blocking-vs-non-blocking.md @@ -14,7 +14,6 @@ basic understanding of the JavaScript language and Node.js callback pattern. > "I/O" refers primarily to interaction with the system's disk and > network supported by [libuv](https://libuv.org/). - --> # ブロッキングとノンブロッキングの概要 @@ -26,7 +25,6 @@ basic understanding of the JavaScript language and Node.js callback pattern. > "I/O" とは、主に [libuv](https://libuv.org/) がサポートしている > システムのディスクやネットワークとのやり取りを指します。 - ## ブロッキング @@ -66,7 +63,6 @@ Node.js 標準ライブラリのすべての I/O メソッドは非同期バー 一部のメソッドには**ブロッキング**に対応したものもあり、 その名前は `Sync` で終わります。 - ## コードを比較する @@ -178,7 +173,6 @@ moreWork(); // console.log の前に実行されます ファイルの読み込みが完了するのを待たずに `moreWork()` を実行する機能は、 より高いスループットを可能にする重要な設計上の選択です。 - ## 並行性とスループット @@ -218,7 +211,6 @@ I/O などの JavaScript 以外の操作が発生しても、 イベントループは、 並行作業を処理するために追加のスレッドが作成される可能性がある他の多くの言語のモデルとは異なります。 - ## ブロッキングコードとノンブロッキングコードが混在する危険性 @@ -276,7 +266,6 @@ fs.unlinkSync('/file.md'); これを書くためのより良い方法は、 完全に**ノンブロッキング**で正しい順序で実行されることが保証されていることです。 - ```js const fs = require('fs'); fs.readFile('/file.md', (readFileErr, data) => { @@ -291,7 +280,6 @@ fs.readFile('/file.md', (readFileErr, data) => { 上記は、`fs.readFile()`のコールバック内で `fs.unlink()` への**ノンブロッキング**呼び出しを行います。 これにより、正しい操作順序が保証されます。 - ### フレームグラフのラベルが壊れている @@ -251,7 +249,6 @@ node`_ZN2v88internal11interpreter17BytecodeGenerator15VisitStatementsEPNS0_8Zone ``` それは使っている Linux の perf が demangle サポート付きでコンパイルされていないことを意味します。例は https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1396654 を参照してください。 - パッケージマネージャを利用した Node.js のインストール - ***注意:*** このページにあるパッケージはそれぞれのパッケージ管理者によってメンテナンスされています。Node.js コアチームによるものでは**ありません**。遭遇した問題はパッケージの管理者に報告してください。もしその問題が Node.js 自体のバグだと判明した場合は、管理者が報告をあげてくれます。 @@ -48,7 +47,6 @@ Node.js と npm のパッケージがコミュニティのリポジトリから pacman -S nodejs npm ``` - ## Debian と Ubuntu ベースの Linux ディストリビューション、エンタープライズ Linux/Fedora と Snap パッケージ @@ -92,7 +90,6 @@ pkg install node pkg install node-devel ``` - ## Gentoo @@ -136,7 +133,6 @@ cd /usr/pkgsrc/lang/nodejs && make install pkgin -y install nodejs ``` - ## openSUSE と SLE @@ -156,7 +152,6 @@ sudo zypper ar \ sudo zypper in nodejs nodejs-devel ``` - ## macOS @@ -219,7 +214,6 @@ pkgin -y install nodejs cd pkgsrc/lang/nodejs && bmake install ``` - ## Solus Solus provides node.js in its main repository. @@ -228,7 +222,6 @@ Solus provides node.js in its main repository. sudo eopkg install nodejs ``` - ## Void Linux @@ -238,7 +231,6 @@ Void Linux にはメインリポジトリに node.js の安定版があります xbps-install -Sy nodejs ``` - ## Windows diff --git a/locale/ja/get-involved/index.md b/locale/ja/get-involved/index.md index 6b0f50cff607f..4fe222230f02c 100644 --- a/locale/ja/get-involved/index.md +++ b/locale/ja/get-involved/index.md @@ -16,7 +16,6 @@ layout: contribute.hbs - [Node.js Collection](https://medium.com/the-node-js-collection) is a collection of community-curated content on Medium. - The [Community Committee](https://github.com/nodejs/community-committee) is a top-level committee in the Node.js Foundation focused on community-facing efforts. - --> # 参加する diff --git a/locale/ja/get-involved/node-meetups.md b/locale/ja/get-involved/node-meetups.md index 42d19b1f499a4..26191e3eb170d 100644 --- a/locale/ja/get-involved/node-meetups.md +++ b/locale/ja/get-involved/node-meetups.md @@ -382,7 +382,6 @@ REQUIREMENTS - Organizer name - Matt Pardee - Organizer contact info - - #### Colorado ##### Denver @@ -537,7 +536,6 @@ REQUIREMENTS - Organizer name - Aaron Seth Madsen - Organizer contact info - - #### Washington ##### Seattle @@ -596,7 +594,6 @@ REQUIREMENTS - Organizer names - Marcus Noble, Seren Davies - Organizers contact info - organisers@jsoxford.com - ### Ukraine #### Kiev diff --git a/locale/ko/about/releases.md b/locale/ko/about/releases.md index 9ffd70cea7430..acf1cfc7ce07c 100644 --- a/locale/ko/about/releases.md +++ b/locale/ko/about/releases.md @@ -18,4 +18,3 @@ schedule-footer: 날짜는 변경될 수 있습니다. --- # 릴리스 - diff --git a/locale/ko/docs/guides/blocking-vs-non-blocking.md b/locale/ko/docs/guides/blocking-vs-non-blocking.md index 02ad7ee770974..af152b54b48d6 100644 --- a/locale/ko/docs/guides/blocking-vs-non-blocking.md +++ b/locale/ko/docs/guides/blocking-vs-non-blocking.md @@ -237,7 +237,6 @@ In the above example, `fs.unlinkSync()` is likely to be run before better way to write this that is completely **non-blocking** and guaranteed to execute in the correct order is: - ```js const fs = require('fs'); fs.readFile('/file.md', (readFileErr, data) => { @@ -269,7 +268,6 @@ fs.readFile('/file.md', (readFileErr, data) => { The above places a **non-blocking** call to `fs.unlink()` within the callback of `fs.readFile()` which guarantees the correct order of operations. - ## Additional Resources - [libuv](https://libuv.org/) @@ -278,7 +276,6 @@ The above places a **non-blocking** call to `fs.unlink()` within the callback of 여기서는 `fs.readFile()`의 콜백에서 `fs.unlink()`를 **논블로킹**으로 호출하도록 해서 작업 순서가 올바르도록 보장했습니다. - ## 추가 자료 - [libuv](https://libuv.org/) diff --git a/locale/ko/docs/guides/domain-postmortem.md b/locale/ko/docs/guides/domain-postmortem.md index 3c818216b563e..432a2e5bfcc96 100644 --- a/locale/ko/docs/guides/domain-postmortem.md +++ b/locale/ko/docs/guides/domain-postmortem.md @@ -37,13 +37,11 @@ Here's an example of how one indirectly linked modules can affect another: const b = require('./b'); const c = require('./c'); - // module b.js const d = require('domain').create(); d.on('error', () => { /* silence everything */ }); d.enter(); - // module c.js const dep = require('some-dep'); dep.method(); // Uh-oh! This method doesn't actually exist. @@ -63,13 +61,11 @@ running. const b = require('./b'); const c = require('./c'); - // 모듈 b.js const d = require('domain').create(); d.on('error', () => { /* 모든 것을 무시합니다. */ }); d.enter(); - // 모듈 c.js const dep = require('some-dep'); dep.method(); // 앗! 이 메서드는 실제로 존재하지 않습니다. @@ -194,7 +190,6 @@ d.run(() => { 아니면 이 예외가 절대 자동으로 버블링되지 않기를 기대할 수 있습니다. 불행히도 두 가지 상황이 모두 발생하고 이는 시점의 충돌을 디버깅하기 어렵게 만들기 쉬운 혼란스러운 동작입니다. - Então, para finalizar tudo, quando usar callbacks, se um erro aparecer, passe-o como primeiro argumento. Caso contrário, passe `null` primeiro e depois seus argumentos de retorno. Na extremidade receptora, dentro da função de retorno de chamada, verifique se o primeiro parâmetro não é nulo; se for, manipule como um erro. - diff --git a/locale/pt-br/knowledge/errors/what-is-try-catch.md b/locale/pt-br/knowledge/errors/what-is-try-catch.md index 7811c0ee6b0cf..67a2266448066 100644 --- a/locale/pt-br/knowledge/errors/what-is-try-catch.md +++ b/locale/pt-br/knowledge/errors/what-is-try-catch.md @@ -52,4 +52,3 @@ Note que você pode omitir o bloco `catch` ou `finally`, mas um deles deve exist No core da biblioteca node.js, o único lugar que realmente *precisamos* usar um bloco try-catch é ao redor do método `JSON.parse()`. Todos os outros métodos usam o objeto Error padrão através do primeiro parâmetro do callback ou emitem um evento de `error`. Por causa disso, geralmente é considerado [padrão](/what-are-the-error-conventions) retornar erros por meio de callback, em vez de usar a instrução `throw`. - diff --git a/locale/pt-br/knowledge/file-system/how-to-search-files-and-directories-in-nodejs.md b/locale/pt-br/knowledge/file-system/how-to-search-files-and-directories-in-nodejs.md index d152e543cc2b9..95eb6253a4974 100644 --- a/locale/pt-br/knowledge/file-system/how-to-search-files-and-directories-in-nodejs.md +++ b/locale/pt-br/knowledge/file-system/how-to-search-files-and-directories-in-nodejs.md @@ -19,7 +19,6 @@ Suponha que você queira listar todos os arquivos no seu diretório atual. Uma console.log(files); }); - Infelizmente, se você quiser fazer uma lista recursiva dos arquivos, então as coisas rapidamente ficarão muito mais complicadas. Para evitar toda essa complexidade assustadora, esta é uma das circunstâncias onde uma biblioteca feita por usuários pode salvar o dia. [Node-findit](https://github.com/substack/node-findit), pela SubStack, é um módulo auxiliar para facilitar a busca por arquivos. Ele tem interfaces para permitir você trabalhar com callbacks, eventos, ou simplesmente da velha forma síncrona (o que na maioria das vezes não é uma boa ideia). Para instalar `node-findit`, simplesmente use npm: diff --git a/locale/pt-br/knowledge/file-system/how-to-store-local-config-data.md b/locale/pt-br/knowledge/file-system/how-to-store-local-config-data.md index 5686290b30b68..6a2c2634aaab6 100644 --- a/locale/pt-br/knowledge/file-system/how-to-store-local-config-data.md +++ b/locale/pt-br/knowledge/file-system/how-to-store-local-config-data.md @@ -8,7 +8,6 @@ difficulty: 1 layout: knowledge-post.hbs --- - Armazenar os dados de configuração da sua aplicação Node.js é muito simples - cada objeto no JavaScript pode ser facilmente renderizado como [JSON](/what-is-json), que por sua vez é apenas dados em string que podem ser enviados ou salvos da maneira que você preferir. A forma mais simples de fazer isso envolve os métodos built-in `JSON.parse()` e `JSON.stringify()`. Vamos dar uma olhada em um exemplo muito simples (e imaginário). Primeiro, para salvar alguns dados bem simples: @@ -82,4 +81,3 @@ Após isso, a sintaxe é moleza. Veja um exemplo: A única coisa que requer atenção aqui é o delimitador - ':'. Quando se acessa propriedades aninhadas com o `nconf`, os dois-pontos são usados para delimitar os namespaces dos nomes das chaves. Se uma sub-chave específica não é fornecida, o objeto inteiro é definido ou retornado. Quando usa-se o `nconf` para guardar seus dados de configurações em um arquivo, `nconf.save()` e `nconf.load()` são os únicos momentos em que acontecerá interações com o arquivo atual. Todos os outros acessos são realizados em uma cópia de seus dados em memória, que não serão persistidos sem uma chamada do `nconf.save()`. De maneira semelhante, se você está tentando trazer de volta dados de configuração da última vez que sua aplicação rodou, eles não existirão em memória sem uma chamada para `nconf.load()`, como mostrado acima. - diff --git a/locale/pt-br/knowledge/file-system/how-to-use-the-path-module.md b/locale/pt-br/knowledge/file-system/how-to-use-the-path-module.md index ab899c3effde6..0a1feef1c50ac 100644 --- a/locale/pt-br/knowledge/file-system/how-to-use-the-path-module.md +++ b/locale/pt-br/knowledge/file-system/how-to-use-the-path-module.md @@ -65,4 +65,3 @@ Bloqueio nem sempre é uma coisa ruim. Checar a existência de um arquivo de co > path.existsSync('/etc') true - diff --git a/locale/pt-br/security.md b/locale/pt-br/security.md index 0d5cc38aaa9ef..483ae01819621 100644 --- a/locale/pt-br/security.md +++ b/locale/pt-br/security.md @@ -44,7 +44,6 @@ O código é auditado para encontrar possíveis problemas similares em potencial - Este processo pode levar algum tempo, especialmente quando é necessária uma coordenação com _maintainers_ de outros projetos. Todo esforço será feito para garantir que o bug seja corrigida a tempo. Entretanto, é importante que acompanhe o processo de release acima para garantir que o anúncio seja feito de forma consistente. - ## Recebendo Atualizações de segurança Notificaçōes de segurança serão distribuídas através dos seguintes métodos. diff --git a/locale/ru/docs/guides/anatomy-of-an-http-transaction.md b/locale/ru/docs/guides/anatomy-of-an-http-transaction.md index 289514b9c5537..e7cdb03e47bf4 100644 --- a/locale/ru/docs/guides/anatomy-of-an-http-transaction.md +++ b/locale/ru/docs/guides/anatomy-of-an-http-transaction.md @@ -401,8 +401,6 @@ From these basics, Node.js HTTP servers for many typical use cases can be constructed. There are plenty of other things these APIs provide, so be sure to read through the API docs for [`EventEmitters`][], [`Streams`][], and [`HTTP`][]. - - [`EventEmitters`]: https://nodejs.org/api/events.html [`Streams`]: https://nodejs.org/api/stream.html [`createServer`]: https://nodejs.org/api/http.html#http_http_createserver_requestlistener diff --git a/locale/ru/docs/guides/backpressuring-in-streams.md b/locale/ru/docs/guides/backpressuring-in-streams.md index a03622f9a6f12..1444a2e871243 100644 --- a/locale/ru/docs/guides/backpressuring-in-streams.md +++ b/locale/ru/docs/guides/backpressuring-in-streams.md @@ -592,7 +592,6 @@ Be sure to read up more on [`Stream`][] for other API functions to help improve and unleash your streaming capabilities when building an application with Node.js. - [`Stream`]: https://nodejs.org/api/stream.html [`Buffer`]: https://nodejs.org/api/buffer.html [`EventEmitters`]: https://nodejs.org/api/events.html diff --git a/locale/ru/docs/guides/blocking-vs-non-blocking.md b/locale/ru/docs/guides/blocking-vs-non-blocking.md index cee920cd74406..94f0f250b429b 100644 --- a/locale/ru/docs/guides/blocking-vs-non-blocking.md +++ b/locale/ru/docs/guides/blocking-vs-non-blocking.md @@ -14,7 +14,6 @@ layout: docs.hbs > Обозначение "I/O" (Ввод/Вывод) в первую очередь ссылается на взаимодействие > с системным диском и сетью при поддержке [libuv](https://libuv.org/). - ## Блокирование О **блокировании** говорят, когда выполнение JS кода в Node.js @@ -33,7 +32,6 @@ layout: docs.hbs в качестве аргумента. Некоторые методы также имеют свои **блокирующие** аналоги. Названия таких методов закнчиваются на `Sync`. - ## Сравнение Кода **Блокирующие** методы исполняются **синхронно**, а **неблокирующие** методы @@ -90,7 +88,6 @@ JavaScript может продолжаться, не дожидаясь окон дожидаться окончания чтения файла и других системных вызовов — ключевое инженерное решение, которое обеспечивает высокую пропускную способность Node.js. - ## Конкурентность и Пропускная Способность Исполнение JavaScript в Node.js является однопоточным. Поэтому, говоря о конкурентности @@ -108,7 +105,6 @@ JavaScript может продолжаться, не дожидаясь окон отличается от подходов во многих других языках программрования, в которых могут создаваться дополнительные потоки. - ## Опасность смешивания Блокирующего и Неблокирующего Кода Существуют паттерны, которые следует избегать при работе с I/O. Взглянем на пример: @@ -126,7 +122,6 @@ fs.unlinkSync('/file.md'); `fs.readFile()`. Это приведет к удалению файла до его прочтения. Лучше переписать этот код в **неблокирующем** виде, что гарантирует правильный порядок исполнения методов: - ```js const fs = require('fs'); fs.readFile('/file.md', (readFileErr, data) => { @@ -141,7 +136,6 @@ fs.readFile('/file.md', (readFileErr, data) => { В последнем примере **неблокирующий** вызов метода `fs.unlink()` расположен внутри функции обратного вызова `fs.readFile()`. Такой подход гарантирует парвильную последовательность операций. - ## Дополнительные рессурсы - [libuv](https://libuv.org/) diff --git a/locale/ru/docs/guides/diagnostics-flamegraph.md b/locale/ru/docs/guides/diagnostics-flamegraph.md index 37756478bbd14..fa15f5515c51e 100644 --- a/locale/ru/docs/guides/diagnostics-flamegraph.md +++ b/locale/ru/docs/guides/diagnostics-flamegraph.md @@ -114,7 +114,6 @@ node`_ZN2v88internal11interpreter17BytecodeGenerator15VisitStatementsEPNS0_8Zone ``` it means the Linux perf you're using was not compiled with demangle support, see https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1396654 for example - ## Examples Practice capturing flame graphs yourself with [a flame graph exercise](https://github.com/naugtur/node-example-flamegraph)! diff --git a/locale/ru/docs/guides/domain-postmortem.md b/locale/ru/docs/guides/domain-postmortem.md index 6426c2a73361a..310d7c7ee2b93 100644 --- a/locale/ru/docs/guides/domain-postmortem.md +++ b/locale/ru/docs/guides/domain-postmortem.md @@ -22,13 +22,11 @@ Here's an example of how one indirectly linked modules can affect another: const b = require('./b'); const c = require('./c'); - // module b.js const d = require('domain').create(); d.on('error', () => { /* silence everything */ }); d.enter(); - // module c.js const dep = require('some-dep'); dep.method(); // Uh-oh! This method doesn't actually exist. @@ -99,7 +97,6 @@ automatically bubble. Unfortunately both these situations occur, leading to potentially confusing behavior that may even be prone to difficult to debug timing conflicts. - ### API Gaps While APIs based on using `EventEmitter` can use `bind()` and errback style @@ -109,7 +106,6 @@ wanted to support domains using a mechanism alternative to those mentioned they must manually implement domain support themselves. Instead of being able to leverage the implicit mechanisms already in place. - ### Error Propagation Propagating errors across nested domains is not straight forward, if even @@ -155,7 +151,6 @@ several asynchronous requests and each one then `write()`'s data back to the client many more errors will arise from attempting to `write()` to a closed handle. More on this in _Resource Cleanup on Exception_. - ### Resource Cleanup on Exception The following script contains a more complex example of properly cleaning up @@ -333,7 +328,6 @@ In the end, in terms of handling errors, domains aren't much more than a glorified `'uncaughtException'` handler. Except with more implicit and unobservable behavior by third-parties. - ### Resource Propagation Another use case for domains was to use it to propagate data along asynchronous @@ -408,7 +402,6 @@ user's callback is called. Also the instantiation of `DataStream` in the In short, for this to have a prayer of a chance usage would need to strictly adhere to a set of guidelines that would be difficult to enforce or test. - ## Performance Issues A significant deterrent from using domains is the overhead. Using node's @@ -433,7 +426,6 @@ will result in a 17% performance loss. Granted, this is for the optimized scenario of the benchmark, but I believe this demonstrates the necessity for a mechanism such as domain to be as cheap to run as possible. - ## Looking Ahead The domain module has been soft deprecated since Dec 2014, but has not yet been diff --git a/locale/ru/docs/guides/event-loop-timers-and-nexttick.md b/locale/ru/docs/guides/event-loop-timers-and-nexttick.md index 53314763fefd7..683bb8bebc2f6 100644 --- a/locale/ru/docs/guides/event-loop-timers-and-nexttick.md +++ b/locale/ru/docs/guides/event-loop-timers-and-nexttick.md @@ -71,7 +71,6 @@ demonstration. The most important parts are here. There are actually seven or eight steps, but the ones we care about — ones that Node.js actually uses - are those above._ - ## Phases Overview * **timers**: this phase executes callbacks scheduled by `setTimeout()` @@ -123,7 +122,6 @@ setTimeout(() => { console.log(`${delay}ms have passed since I was scheduled`); }, 100); - // do someAsyncOperation which takes 95 ms to complete someAsyncOperation(() => { const startCallback = Date.now(); @@ -233,7 +231,6 @@ cycle (i.e. the main module), the order in which the two timers are executed is non-deterministic, as it is bound by the performance of the process: - ```js // timeout_vs_immediate.js setTimeout(() => { diff --git a/locale/ru/docs/guides/index.md b/locale/ru/docs/guides/index.md index 22d0db771aec2..c4e7d08462f73 100644 --- a/locale/ru/docs/guides/index.md +++ b/locale/ru/docs/guides/index.md @@ -14,7 +14,6 @@ layout: docs.hbs - [Dockerizing a Node.js web app](nodejs-docker-webapp/) - [Migrating to safe Buffer constructors](buffer-constructor-deprecation/) - ## Ключевые концепции Node.js - [Блокирующие и Неблокирующие Вызовы](blocking-vs-non-blocking/) @@ -22,7 +21,6 @@ layout: docs.hbs - [Don't Block the Event Loop (or the Worker Pool)](dont-block-the-event-loop/) - [Timers in Node.js](timers-in-node/) - ## Module-related guides - [Anatomy of an HTTP Transaction](anatomy-of-an-http-transaction/) diff --git a/locale/ru/download/package-manager.md b/locale/ru/download/package-manager.md index 4c882daadd44e..07a5d16b6580e 100644 --- a/locale/ru/download/package-manager.md +++ b/locale/ru/download/package-manager.md @@ -200,7 +200,6 @@ pkgin -y install nodejs cd pkgsrc/lang/nodejs && bmake install ``` - ## Solus Solus предоставляет node.js в своем основном репозитории. @@ -209,7 +208,6 @@ Solus предоставляет node.js в своем основном репо sudo eopkg install nodejs ``` - ## Void Linux Void Linux поставляет стабильный файл node.js в основном репозитории. diff --git a/locale/ru/get-involved/index.md b/locale/ru/get-involved/index.md index 127b581152229..0af017e320065 100644 --- a/locale/ru/get-involved/index.md +++ b/locale/ru/get-involved/index.md @@ -15,7 +15,6 @@ layout: contribute.hbs - [Node.js](https://medium.com/the-node-js-collection) контент, создаваемый сообществом Medium. - [Community Committee](https://github.com/nodejs/community-committee) является комитетом высшего уровня в Фонде Node.js, ориентированным на развитие сообщества. - ## Обучение - [Официальная справочная документация по API](/api/) описывает API Node.js diff --git a/locale/ru/get-involved/node-meetups.md b/locale/ru/get-involved/node-meetups.md index e131b0db6e250..4e2e3d770a968 100644 --- a/locale/ru/get-involved/node-meetups.md +++ b/locale/ru/get-involved/node-meetups.md @@ -382,7 +382,6 @@ layout: contribute.hbs - Организаторы ― Matt Pardee - Контакты организаторов - - #### Colorado ##### Denver @@ -537,7 +536,6 @@ layout: contribute.hbs - Организаторы ― Aaron Seth Madsen - Контакты организаторов - - #### Washington ##### Seattle @@ -596,7 +594,6 @@ layout: contribute.hbs - Организаторы ― Marcus Noble, Seren Davies - Organizers contact info ― organisers@jsoxford.com - ### Ukraine #### Kiev diff --git a/locale/ru/knowledge/HTTP/clients/how-to-access-query-string-parameters.md b/locale/ru/knowledge/HTTP/clients/how-to-access-query-string-parameters.md index 8538a2874e09a..3ce5db155507d 100644 --- a/locale/ru/knowledge/HTTP/clients/how-to-access-query-string-parameters.md +++ b/locale/ru/knowledge/HTTP/clients/how-to-access-query-string-parameters.md @@ -22,5 +22,3 @@ In Node.js, functionality to aid in the accessing of URL query string parameters }).listen(8080); 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. - - diff --git a/locale/ru/knowledge/HTTP/clients/how-to-create-a-HTTP-request.md b/locale/ru/knowledge/HTTP/clients/how-to-create-a-HTTP-request.md index 29e6003314887..44b9ad4f1f31e 100644 --- a/locale/ru/knowledge/HTTP/clients/how-to-create-a-HTTP-request.md +++ b/locale/ru/knowledge/HTTP/clients/how-to-create-a-HTTP-request.md @@ -36,7 +36,6 @@ As an example, we are going to preform a GET request to [www.random.org/integers http.request(options, callback).end(); - Making a POST request is just as easy. We will make a POST request to `www.nodejitsu.com:1337` which is running a server that will echo back what we post. The code for making a POST request is almost identical to making a GET request, just a few simple modifications: var http = require('http'); diff --git a/locale/ru/knowledge/HTTP/servers/how-to-read-POST-data.md b/locale/ru/knowledge/HTTP/servers/how-to-read-POST-data.md index 132a049b7fd7b..494aeb5f81c99 100644 --- a/locale/ru/knowledge/HTTP/servers/how-to-read-POST-data.md +++ b/locale/ru/knowledge/HTTP/servers/how-to-read-POST-data.md @@ -41,4 +41,3 @@ With the HTML out of the way, we [create a server](/how-do-i-create-a-http-serve Something important to note is that the event listeners are being added immediately after the request object is received. If you don't immediately set them, then there is a possibility of missing some of the events. If, for example, an event listener was attached from inside a callback, then the `data` and `end` events might be fired in the meantime with no listeners attached! You can save this script to `server.js` and run it with `node server.js`. Once you run it you will notice that occasionally you will see lines with no data, e.g. `POSTed:`. This happens because regular `GET` requests go through the same codepath. In a more 'real-world' application, it would be proper practice to check the type of request and handle the different request types differently. - diff --git a/locale/ru/knowledge/advanced/streams/how-to-use-fs-create-read-stream.md b/locale/ru/knowledge/advanced/streams/how-to-use-fs-create-read-stream.md index d0a4823c575b1..db4464bad2168 100644 --- a/locale/ru/knowledge/advanced/streams/how-to-use-fs-create-read-stream.md +++ b/locale/ru/knowledge/advanced/streams/how-to-use-fs-create-read-stream.md @@ -32,4 +32,3 @@ The function `fs.createReadStream()` allows you to open up a readable stream in res.end(err); }); }).listen(8080); - diff --git a/locale/ru/knowledge/advanced/streams/what-are-streams.md b/locale/ru/knowledge/advanced/streams/what-are-streams.md index 777af6c9ff2ca..977c15bbd1039 100644 --- a/locale/ru/knowledge/advanced/streams/what-are-streams.md +++ b/locale/ru/knowledge/advanced/streams/what-are-streams.md @@ -39,5 +39,4 @@ Run this script with arguments like `node cp.js src.txt dest.txt`. This would me console.log("ERROR", err); }); - This sets up a readable stream from the source file and a writable stream to the destination file. Then whenever the readable stream gets data, it gets written to the writeable stream. Then finally it closes the writable stream when the readable stream is finished. NOTE: it would have been better to use [pipe](/how-to-use-stream-pipe) like `readStream.pipe(writeStream);`, however, to show how streams work, we have done things the long way. diff --git a/locale/ru/knowledge/child-processes/how-to-spawn-a-child-process.md b/locale/ru/knowledge/child-processes/how-to-spawn-a-child-process.md index f8e5b7f7a7bae..fb05d9b25dc71 100644 --- a/locale/ru/knowledge/child-processes/how-to-spawn-a-child-process.md +++ b/locale/ru/knowledge/child-processes/how-to-spawn-a-child-process.md @@ -34,5 +34,3 @@ NODE PRO TIP: `error.stack` is a stack trace to the point that the [Error object 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. 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. - - diff --git a/locale/ru/knowledge/command-line/how-to-prompt-for-command-line-input.md b/locale/ru/knowledge/command-line/how-to-prompt-for-command-line-input.md index c64fdec2e3581..db68702a5ed7d 100644 --- a/locale/ru/knowledge/command-line/how-to-prompt-for-command-line-input.md +++ b/locale/ru/knowledge/command-line/how-to-prompt-for-command-line-input.md @@ -32,7 +32,6 @@ Here's a simple example. Try the following in a new file: console.log('Now that process.stdin is paused, there is nothing more to do.'); process.exit(); } - If all of this sounds complicated, or if you want a higher-level interface to this sort of thing, don't worry - as usual, the Node.js community has come to the rescue. One particularly friendly module to use for this is Prompt, maintained by Nodejitsu. It's available on `npm`: diff --git a/locale/ru/knowledge/cryptography/how-to-use-the-tls-module.md b/locale/ru/knowledge/cryptography/how-to-use-the-tls-module.md index 689d5d5d3a9f4..57d7fc0c5250a 100644 --- a/locale/ru/knowledge/cryptography/how-to-use-the-tls-module.md +++ b/locale/ru/knowledge/cryptography/how-to-use-the-tls-module.md @@ -51,7 +51,6 @@ In most ways, the tls module's server api is similar to that of the net module. s.pipe(s); }).listen(8000); - In this example, a "hello world" tls server is created, listening on port 8000. The options object includes two properties: `key` and `cert`. The contents of these properties come directly from the private key and public certificate stored on the filesystem. In this case they are binary buffers, but the tls module can also accept unicode strings. ### Generating Your Private Key And Certificate With OpenSSL: @@ -131,8 +130,6 @@ The tls module also supplies tools for connecting to such a server: console.log(); }); - - conn.on("data", function (data) { console.log(data.toString()); conn.end(); diff --git a/locale/ru/knowledge/file-system/how-to-search-files-and-directories-in-nodejs.md b/locale/ru/knowledge/file-system/how-to-search-files-and-directories-in-nodejs.md index a708eb556f33a..ea4225f60f86e 100644 --- a/locale/ru/knowledge/file-system/how-to-search-files-and-directories-in-nodejs.md +++ b/locale/ru/knowledge/file-system/how-to-search-files-and-directories-in-nodejs.md @@ -19,7 +19,6 @@ Suppose you want to list all the files in the current directory. One approach i console.log(files); }); - 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). To install `node-findit`, simply use npm: diff --git a/locale/ru/knowledge/file-system/how-to-store-local-config-data.md b/locale/ru/knowledge/file-system/how-to-store-local-config-data.md index e285bce5c0bb5..52a298af08e5d 100644 --- a/locale/ru/knowledge/file-system/how-to-store-local-config-data.md +++ b/locale/ru/knowledge/file-system/how-to-store-local-config-data.md @@ -81,4 +81,3 @@ After that, the syntax is a breeze. Have a look at an example: The only tricky thing to notice here is the delimiter - ':'. When accessing nested properties with `nconf`, a colon is used to delimit the namespaces of key names. If a specific sub-key is not provided, the whole object is set or returned. When using `nconf` to store your configuration data to a file, `nconf.save()` and `nconf.load()` are the only times that any actual file interaction will happen. All other access is performed on an in-memory copy of your data, which will not persist without a call to `nconf.save()`. Similarly, if you're trying to bring back configuration data from the last time your application ran, it will not exist in memory without a call to `nconf.load()`, as shown above. - diff --git a/locale/ru/knowledge/file-system/how-to-use-the-path-module.md b/locale/ru/knowledge/file-system/how-to-use-the-path-module.md index 584f0ff4583dd..e3e9bb0ef4225 100644 --- a/locale/ru/knowledge/file-system/how-to-use-the-path-module.md +++ b/locale/ru/knowledge/file-system/how-to-use-the-path-module.md @@ -65,4 +65,3 @@ Blocking isn't always a bad thing. Checking the existence of a vital configurat > path.existsSync('/etc') true - diff --git a/locale/ru/knowledge/getting-started/control-flow/how-to-write-asynchronous-code.md b/locale/ru/knowledge/getting-started/control-flow/how-to-write-asynchronous-code.md index 00ed81f3d072b..9841fb3162ed7 100644 --- a/locale/ru/knowledge/getting-started/control-flow/how-to-write-asynchronous-code.md +++ b/locale/ru/knowledge/getting-started/control-flow/how-to-write-asynchronous-code.md @@ -37,7 +37,6 @@ The asynchronous version, on the other hand, does not stop time - instead, the c When only reading a file or two, or saving something quickly, the difference between synchronous and asynchronous file I/O can be quite small. On the other hand, though, when you have multiple requests coming in per second that require file or database IO, trying to do that IO synchronously would be quite thoroughly disastrous for performance. - ### Callbacks Callbacks are a basic idiom in node.js for asynchronous operations. When most people talk about callbacks, they mean the function that is passed as the last parameter to an asynchronous function. The callback is then later called with any return value or error message that the function produced. For more details, see the article on [callbacks](/ru/knowledge/getting-started/control-flow/what-are-callbacks) diff --git a/locale/ru/knowledge/getting-started/control-flow/what-are-event-emitters.md b/locale/ru/knowledge/getting-started/control-flow/what-are-event-emitters.md index a62e8ff1b2fa8..a9948a3631417 100644 --- a/locale/ru/knowledge/getting-started/control-flow/what-are-event-emitters.md +++ b/locale/ru/knowledge/getting-started/control-flow/what-are-event-emitters.md @@ -99,4 +99,3 @@ If you want remove a specific callback, you can use `removeListener`. If you wan false NOTE: If you want create more than 10 listeners on a single event, you will have to make a call to `ee.setMaxListeners(n)` where n is the max numbers of listeners (with zero being unlimited number of listeners). This is used to make sure you aren't accidentally leaking event listeners. - diff --git a/locale/ru/knowledge/getting-started/how-to-debug-nodejs-applications.md b/locale/ru/knowledge/getting-started/how-to-debug-nodejs-applications.md index f20cdc8d67c4f..69e0ab0145409 100644 --- a/locale/ru/knowledge/getting-started/how-to-debug-nodejs-applications.md +++ b/locale/ru/knowledge/getting-started/how-to-debug-nodejs-applications.md @@ -9,7 +9,6 @@ layout: knowledge-post.hbs Often times, not just in the Node.js community but in software at large, people debug simply with a liberal sprinkle of standard output statements. This allows you to track down where unexpected values are being generated. However, this method can be tedious, or worse yet, not robust enough to detect the real problem. - ### Set up Thankfully, through the use of `node-inspector`, we can harness to power of the webkit-debuggers to work with our node.js code. The process itself is simple. diff --git a/locale/ru/knowledge/getting-started/how-to-use-util-inspect.md b/locale/ru/knowledge/getting-started/how-to-use-util-inspect.md index 9f9844ddebd74..fcbd433e6f60c 100644 --- a/locale/ru/knowledge/getting-started/how-to-use-util-inspect.md +++ b/locale/ru/knowledge/getting-started/how-to-use-util-inspect.md @@ -46,4 +46,3 @@ Finally, the optional argument `colorize` is a boolean that adds ANSI escape cod var util = require('util'); console.log(util.inspect({a:1, b:"b"}, false,2,true)); - diff --git a/locale/ru/knowledge/getting-started/npm/what-is-npm.md b/locale/ru/knowledge/getting-started/npm/what-is-npm.md index b64eab7e91e67..25a483efecc95 100644 --- a/locale/ru/knowledge/getting-started/npm/what-is-npm.md +++ b/locale/ru/knowledge/getting-started/npm/what-is-npm.md @@ -9,7 +9,6 @@ layout: knowledge-post.hbs `npm`, short for Node Package Manager, is two things: first and foremost, it is an online repository for the publishing of open-source Node.js projects; second, it is a command-line utility for interacting with said repository that aids in package installation, version management, and dependency management. A plethora of node.js libraries and applications are published on npm, and many more are added every day. These applications can be searched for on http://search.npmjs.org/. Once you have a package you want to install, it can be installed with a single command-line command. - Let's say you're hard at work one day, developing the Next Great Application. You come across a problem, and you decide that it's time to use that cool library you keep hearing about - let's use Caolan McMahon's [async](https://github.com/caolan/async) as an example. Thankfully, `npm` is very simple to use: you only have to run `npm install async`, and the specified module will be installed in the current directory under `./node_modules/`. Once installed to your `node_modules` folder, you'll be able to use `require()` on them just like they were built-ins. Let's look at an example of a global install - let's say `coffee-script`. The npm command is simple: `npm install coffee-script -g`. This will typically install the program and put a symlink to it in `/usr/local/bin/`. This will then allow you to run the program from the console just like any other CLI tool. In this case, running `coffee` will now allow you to use the coffee-script REPL. @@ -23,4 +22,3 @@ Example: npm install After running those commands, you will see a `node_modules` folder containing all of the project dependencies specified in the package.json. - diff --git a/locale/ru/knowledge/getting-started/what-is-require.md b/locale/ru/knowledge/getting-started/what-is-require.md index 8f5367b00ca45..f79b5a472f175 100644 --- a/locale/ru/knowledge/getting-started/what-is-require.md +++ b/locale/ru/knowledge/getting-started/what-is-require.md @@ -51,10 +51,8 @@ It is worth noting that each time you subsequently require an already-required f node> require('./example.js') //One might think that this "reloads" the file... { message: 'hey', say: [Function] } //...but the message is still "hey" because of the module cache. - As you can see from the above, `example.js` is evaluated the first time, but all subsequent calls to `require()` only invoke the module cache, rather than reading the file again. As seen above, this can occasionally produce side effects. The rules of where `require` finds the files can be a little complex, but a simple rule of thumb is that if the file doesn't start with "./" or "/", then it is either considered a core module (and the local Node path is checked), or a dependency in the local `node_modules` folder. If the file starts with "./" it is considered a relative file to the file that called `require`. If the file starts with "/", it is considered an absolute path. NOTE: you can omit ".js" and `require` will automatically append it if needed. For more detailed information, see [the official docs](https://nodejs.org/docs/v0.4.2/api/modules.htmll#all_Together...) An extra note: if the filename passed to `require` is actually a directory, it will first look for `package.json` in the directory and load the file referenced in the `main` property. Otherwise, it will look for an `index.js`. - diff --git a/locale/ru/knowledge/javascript-conventions/how-to-create-default-parameters-for-functions.md b/locale/ru/knowledge/javascript-conventions/how-to-create-default-parameters-for-functions.md index c522dac0eca75..563fe0524a07b 100644 --- a/locale/ru/knowledge/javascript-conventions/how-to-create-default-parameters-for-functions.md +++ b/locale/ru/knowledge/javascript-conventions/how-to-create-default-parameters-for-functions.md @@ -36,7 +36,6 @@ The first idiom is giving a default value for the last parameter. This is done b example(""); betterExample(""); - If the optional value is in the middle it can cause some undesired effects, since all the parameters are shifted over. The optional parameter is not the `undefined` value in this case - the last parameter is the `undefined` one. So you have to check if the last parameter is `undefined` and then manually fix all the other parameters before continuing in the code. This example shows you how to do that: example = function (param1, optParam, callback) { diff --git a/locale/ru/knowledge/javascript-conventions/what-are-the-built-in-timer-functions.md b/locale/ru/knowledge/javascript-conventions/what-are-the-built-in-timer-functions.md index 1159525e33f7e..e4b0de6d6f07c 100644 --- a/locale/ru/knowledge/javascript-conventions/what-are-the-built-in-timer-functions.md +++ b/locale/ru/knowledge/javascript-conventions/what-are-the-built-in-timer-functions.md @@ -58,7 +58,6 @@ The final trick for the timer objects is you can pass parameters to the callback setTimeout(console.log, 1000, "This", "has", 4, "parameters"); setInterval(console.log, 1000, "This only has one"); - This has 4 parameters This only has one This only has one diff --git a/locale/uk/download/package-manager.md b/locale/uk/download/package-manager.md index 56604f9397737..eadedf27977ac 100644 --- a/locale/uk/download/package-manager.md +++ b/locale/uk/download/package-manager.md @@ -200,7 +200,6 @@ Or build manually from pkgsrc: cd pkgsrc/lang/nodejs && bmake install ``` - ## Solus Solus provides node.js in its main repository. @@ -209,7 +208,6 @@ Solus provides node.js in its main repository. sudo eopkg install nodejs ``` - ## Void Linux Void Linux ships node.js stable in the main repository. diff --git a/locale/uk/get-involved/code-and-learn.md b/locale/uk/get-involved/code-and-learn.md index 4bb7f692a101f..d534257740143 100644 --- a/locale/uk/get-involved/code-and-learn.md +++ b/locale/uk/get-involved/code-and-learn.md @@ -26,4 +26,3 @@ Code + Learn це всесвітня ініціатива воркшопів, щ - Tokyo in November 2016 - Amsterdam in September 2016 - Dublin and London in September 2015 - diff --git a/locale/uk/get-involved/index.md b/locale/uk/get-involved/index.md index d2962fe5622d9..1298bf58e677d 100644 --- a/locale/uk/get-involved/index.md +++ b/locale/uk/get-involved/index.md @@ -14,14 +14,12 @@ layout: contribute.hbs - [Node Weekly](https://nodeweekly.com/) це поштове розсилання, що збирає найсвіжіші події та новини довкола спільноти Node.js. - [Community Committee](https://github.com/nodejs/community-committee) є комітетом вищого рівня в Node.js Фонд зосереджений на спільних зусиллях. - ## Навчання - [Офіційна довідкова документація по API](/api/) описує Node API. - [NodeSchool.io](https://nodeschool.io/) навчить вас концепцій Node.js через інтерактивні консольні ігри. - [Stack Overflow Node.js tag](https://stackoverflow.com/questions/tagged/node.js) щодня поповнюється новою інформацією. - ## Сайти міжнародних спільнот та проекти - [Chinese community](https://cnodejs.org/) diff --git a/locale/uk/knowledge/HTTP/clients/how-to-access-query-string-parameters.md b/locale/uk/knowledge/HTTP/clients/how-to-access-query-string-parameters.md index 8538a2874e09a..3ce5db155507d 100644 --- a/locale/uk/knowledge/HTTP/clients/how-to-access-query-string-parameters.md +++ b/locale/uk/knowledge/HTTP/clients/how-to-access-query-string-parameters.md @@ -22,5 +22,3 @@ In Node.js, functionality to aid in the accessing of URL query string parameters }).listen(8080); 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. - - diff --git a/locale/uk/knowledge/HTTP/clients/how-to-create-a-HTTP-request.md b/locale/uk/knowledge/HTTP/clients/how-to-create-a-HTTP-request.md index 29e6003314887..44b9ad4f1f31e 100644 --- a/locale/uk/knowledge/HTTP/clients/how-to-create-a-HTTP-request.md +++ b/locale/uk/knowledge/HTTP/clients/how-to-create-a-HTTP-request.md @@ -36,7 +36,6 @@ As an example, we are going to preform a GET request to [www.random.org/integers http.request(options, callback).end(); - Making a POST request is just as easy. We will make a POST request to `www.nodejitsu.com:1337` which is running a server that will echo back what we post. The code for making a POST request is almost identical to making a GET request, just a few simple modifications: var http = require('http'); diff --git a/locale/uk/knowledge/HTTP/servers/how-to-read-POST-data.md b/locale/uk/knowledge/HTTP/servers/how-to-read-POST-data.md index 132a049b7fd7b..494aeb5f81c99 100644 --- a/locale/uk/knowledge/HTTP/servers/how-to-read-POST-data.md +++ b/locale/uk/knowledge/HTTP/servers/how-to-read-POST-data.md @@ -41,4 +41,3 @@ With the HTML out of the way, we [create a server](/how-do-i-create-a-http-serve Something important to note is that the event listeners are being added immediately after the request object is received. If you don't immediately set them, then there is a possibility of missing some of the events. If, for example, an event listener was attached from inside a callback, then the `data` and `end` events might be fired in the meantime with no listeners attached! You can save this script to `server.js` and run it with `node server.js`. Once you run it you will notice that occasionally you will see lines with no data, e.g. `POSTed:`. This happens because regular `GET` requests go through the same codepath. In a more 'real-world' application, it would be proper practice to check the type of request and handle the different request types differently. - diff --git a/locale/uk/knowledge/advanced/streams/how-to-use-fs-create-read-stream.md b/locale/uk/knowledge/advanced/streams/how-to-use-fs-create-read-stream.md index d0a4823c575b1..db4464bad2168 100644 --- a/locale/uk/knowledge/advanced/streams/how-to-use-fs-create-read-stream.md +++ b/locale/uk/knowledge/advanced/streams/how-to-use-fs-create-read-stream.md @@ -32,4 +32,3 @@ The function `fs.createReadStream()` allows you to open up a readable stream in res.end(err); }); }).listen(8080); - diff --git a/locale/uk/knowledge/advanced/streams/what-are-streams.md b/locale/uk/knowledge/advanced/streams/what-are-streams.md index 777af6c9ff2ca..977c15bbd1039 100644 --- a/locale/uk/knowledge/advanced/streams/what-are-streams.md +++ b/locale/uk/knowledge/advanced/streams/what-are-streams.md @@ -39,5 +39,4 @@ Run this script with arguments like `node cp.js src.txt dest.txt`. This would me console.log("ERROR", err); }); - This sets up a readable stream from the source file and a writable stream to the destination file. Then whenever the readable stream gets data, it gets written to the writeable stream. Then finally it closes the writable stream when the readable stream is finished. NOTE: it would have been better to use [pipe](/how-to-use-stream-pipe) like `readStream.pipe(writeStream);`, however, to show how streams work, we have done things the long way. diff --git a/locale/uk/knowledge/child-processes/how-to-spawn-a-child-process.md b/locale/uk/knowledge/child-processes/how-to-spawn-a-child-process.md index f8e5b7f7a7bae..fb05d9b25dc71 100644 --- a/locale/uk/knowledge/child-processes/how-to-spawn-a-child-process.md +++ b/locale/uk/knowledge/child-processes/how-to-spawn-a-child-process.md @@ -34,5 +34,3 @@ NODE PRO TIP: `error.stack` is a stack trace to the point that the [Error object 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. 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. - - diff --git a/locale/uk/knowledge/command-line/how-to-prompt-for-command-line-input.md b/locale/uk/knowledge/command-line/how-to-prompt-for-command-line-input.md index c64fdec2e3581..db68702a5ed7d 100644 --- a/locale/uk/knowledge/command-line/how-to-prompt-for-command-line-input.md +++ b/locale/uk/knowledge/command-line/how-to-prompt-for-command-line-input.md @@ -32,7 +32,6 @@ Here's a simple example. Try the following in a new file: console.log('Now that process.stdin is paused, there is nothing more to do.'); process.exit(); } - If all of this sounds complicated, or if you want a higher-level interface to this sort of thing, don't worry - as usual, the Node.js community has come to the rescue. One particularly friendly module to use for this is Prompt, maintained by Nodejitsu. It's available on `npm`: diff --git a/locale/uk/knowledge/cryptography/how-to-use-the-tls-module.md b/locale/uk/knowledge/cryptography/how-to-use-the-tls-module.md index 689d5d5d3a9f4..57d7fc0c5250a 100644 --- a/locale/uk/knowledge/cryptography/how-to-use-the-tls-module.md +++ b/locale/uk/knowledge/cryptography/how-to-use-the-tls-module.md @@ -51,7 +51,6 @@ In most ways, the tls module's server api is similar to that of the net module. s.pipe(s); }).listen(8000); - In this example, a "hello world" tls server is created, listening on port 8000. The options object includes two properties: `key` and `cert`. The contents of these properties come directly from the private key and public certificate stored on the filesystem. In this case they are binary buffers, but the tls module can also accept unicode strings. ### Generating Your Private Key And Certificate With OpenSSL: @@ -131,8 +130,6 @@ The tls module also supplies tools for connecting to such a server: console.log(); }); - - conn.on("data", function (data) { console.log(data.toString()); conn.end(); diff --git a/locale/uk/knowledge/file-system/how-to-search-files-and-directories-in-nodejs.md b/locale/uk/knowledge/file-system/how-to-search-files-and-directories-in-nodejs.md index a708eb556f33a..ea4225f60f86e 100644 --- a/locale/uk/knowledge/file-system/how-to-search-files-and-directories-in-nodejs.md +++ b/locale/uk/knowledge/file-system/how-to-search-files-and-directories-in-nodejs.md @@ -19,7 +19,6 @@ Suppose you want to list all the files in the current directory. One approach i console.log(files); }); - 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). To install `node-findit`, simply use npm: diff --git a/locale/uk/knowledge/file-system/how-to-store-local-config-data.md b/locale/uk/knowledge/file-system/how-to-store-local-config-data.md index e285bce5c0bb5..52a298af08e5d 100644 --- a/locale/uk/knowledge/file-system/how-to-store-local-config-data.md +++ b/locale/uk/knowledge/file-system/how-to-store-local-config-data.md @@ -81,4 +81,3 @@ After that, the syntax is a breeze. Have a look at an example: The only tricky thing to notice here is the delimiter - ':'. When accessing nested properties with `nconf`, a colon is used to delimit the namespaces of key names. If a specific sub-key is not provided, the whole object is set or returned. When using `nconf` to store your configuration data to a file, `nconf.save()` and `nconf.load()` are the only times that any actual file interaction will happen. All other access is performed on an in-memory copy of your data, which will not persist without a call to `nconf.save()`. Similarly, if you're trying to bring back configuration data from the last time your application ran, it will not exist in memory without a call to `nconf.load()`, as shown above. - diff --git a/locale/uk/knowledge/file-system/how-to-use-the-path-module.md b/locale/uk/knowledge/file-system/how-to-use-the-path-module.md index 584f0ff4583dd..e3e9bb0ef4225 100644 --- a/locale/uk/knowledge/file-system/how-to-use-the-path-module.md +++ b/locale/uk/knowledge/file-system/how-to-use-the-path-module.md @@ -65,4 +65,3 @@ Blocking isn't always a bad thing. Checking the existence of a vital configurat > path.existsSync('/etc') true - diff --git a/locale/uk/knowledge/getting-started/control-flow/how-to-write-asynchronous-code.md b/locale/uk/knowledge/getting-started/control-flow/how-to-write-asynchronous-code.md index a480c9741d334..436b2423f6ba8 100644 --- a/locale/uk/knowledge/getting-started/control-flow/how-to-write-asynchronous-code.md +++ b/locale/uk/knowledge/getting-started/control-flow/how-to-write-asynchronous-code.md @@ -37,7 +37,6 @@ The asynchronous version, on the other hand, does not stop time - instead, the c When only reading a file or two, or saving something quickly, the difference between synchronous and asynchronous file I/O can be quite small. On the other hand, though, when you have multiple requests coming in per second that require file or database IO, trying to do that IO synchronously would be quite thoroughly disastrous for performance. - ### Callbacks Callbacks are a basic idiom in node.js for asynchronous operations. When most people talk about callbacks, they mean the function that is passed as the last parameter to an asynchronous function. The callback is then later called with any return value or error message that the function produced. For more details, see the article on [callbacks](/uk/knowledge/getting-started/control-flow/what-are-callbacks) diff --git a/locale/uk/knowledge/getting-started/control-flow/what-are-event-emitters.md b/locale/uk/knowledge/getting-started/control-flow/what-are-event-emitters.md index 45de4b13806c1..d6491e3789280 100644 --- a/locale/uk/knowledge/getting-started/control-flow/what-are-event-emitters.md +++ b/locale/uk/knowledge/getting-started/control-flow/what-are-event-emitters.md @@ -99,4 +99,3 @@ If you want remove a specific callback, you can use `removeListener`. If you wan false NOTE: If you want create more than 10 listeners on a single event, you will have to make a call to `ee.setMaxListeners(n)` where n is the max numbers of listeners (with zero being unlimited number of listeners). This is used to make sure you aren't accidentally leaking event listeners. - diff --git a/locale/uk/knowledge/getting-started/how-to-debug-nodejs-applications.md b/locale/uk/knowledge/getting-started/how-to-debug-nodejs-applications.md index f20cdc8d67c4f..69e0ab0145409 100644 --- a/locale/uk/knowledge/getting-started/how-to-debug-nodejs-applications.md +++ b/locale/uk/knowledge/getting-started/how-to-debug-nodejs-applications.md @@ -9,7 +9,6 @@ layout: knowledge-post.hbs Often times, not just in the Node.js community but in software at large, people debug simply with a liberal sprinkle of standard output statements. This allows you to track down where unexpected values are being generated. However, this method can be tedious, or worse yet, not robust enough to detect the real problem. - ### Set up Thankfully, through the use of `node-inspector`, we can harness to power of the webkit-debuggers to work with our node.js code. The process itself is simple. diff --git a/locale/uk/knowledge/getting-started/how-to-use-util-inspect.md b/locale/uk/knowledge/getting-started/how-to-use-util-inspect.md index 9f9844ddebd74..fcbd433e6f60c 100644 --- a/locale/uk/knowledge/getting-started/how-to-use-util-inspect.md +++ b/locale/uk/knowledge/getting-started/how-to-use-util-inspect.md @@ -46,4 +46,3 @@ Finally, the optional argument `colorize` is a boolean that adds ANSI escape cod var util = require('util'); console.log(util.inspect({a:1, b:"b"}, false,2,true)); - diff --git a/locale/uk/knowledge/getting-started/npm/what-is-npm.md b/locale/uk/knowledge/getting-started/npm/what-is-npm.md index 83ff5ec54523d..05985b7c39e51 100644 --- a/locale/uk/knowledge/getting-started/npm/what-is-npm.md +++ b/locale/uk/knowledge/getting-started/npm/what-is-npm.md @@ -9,7 +9,6 @@ layout: knowledge-post.hbs `npm`, short for Node Package Manager, is two things: first and foremost, it is an online repository for the publishing of open-source Node.js projects; second, it is a command-line utility for interacting with said repository that aids in package installation, version management, and dependency management. A plethora of node.js libraries and applications are published on npm, and many more are added every day. These applications can be searched for on http://search.npmjs.org/. Once you have a package you want to install, it can be installed with a single command-line command. - Let's say you're hard at work one day, developing the Next Great Application. You come across a problem, and you decide that it's time to use that cool library you keep hearing about - let's use Caolan McMahon's [async](https://github.com/caolan/async) as an example. Thankfully, `npm` is very simple to use: you only have to run `npm install async`, and the specified module will be installed in the current directory under `./node_modules/`. Once installed to your `node_modules` folder, you'll be able to use `require()` on them just like they were built-ins. Let's look at an example of a global install - let's say `coffee-script`. The npm command is simple: `npm install coffee-script -g`. This will typically install the program and put a symlink to it in `/usr/local/bin/`. This will then allow you to run the program from the console just like any other CLI tool. In this case, running `coffee` will now allow you to use the coffee-script REPL. @@ -23,4 +22,3 @@ Example: npm install After running those commands, you will see a `node_modules` folder containing all of the project dependencies specified in the package.json. - diff --git a/locale/uk/knowledge/getting-started/what-is-require.md b/locale/uk/knowledge/getting-started/what-is-require.md index 8f5367b00ca45..f79b5a472f175 100644 --- a/locale/uk/knowledge/getting-started/what-is-require.md +++ b/locale/uk/knowledge/getting-started/what-is-require.md @@ -51,10 +51,8 @@ It is worth noting that each time you subsequently require an already-required f node> require('./example.js') //One might think that this "reloads" the file... { message: 'hey', say: [Function] } //...but the message is still "hey" because of the module cache. - As you can see from the above, `example.js` is evaluated the first time, but all subsequent calls to `require()` only invoke the module cache, rather than reading the file again. As seen above, this can occasionally produce side effects. The rules of where `require` finds the files can be a little complex, but a simple rule of thumb is that if the file doesn't start with "./" or "/", then it is either considered a core module (and the local Node path is checked), or a dependency in the local `node_modules` folder. If the file starts with "./" it is considered a relative file to the file that called `require`. If the file starts with "/", it is considered an absolute path. NOTE: you can omit ".js" and `require` will automatically append it if needed. For more detailed information, see [the official docs](https://nodejs.org/docs/v0.4.2/api/modules.htmll#all_Together...) An extra note: if the filename passed to `require` is actually a directory, it will first look for `package.json` in the directory and load the file referenced in the `main` property. Otherwise, it will look for an `index.js`. - diff --git a/locale/uk/knowledge/javascript-conventions/how-to-create-default-parameters-for-functions.md b/locale/uk/knowledge/javascript-conventions/how-to-create-default-parameters-for-functions.md index c522dac0eca75..563fe0524a07b 100644 --- a/locale/uk/knowledge/javascript-conventions/how-to-create-default-parameters-for-functions.md +++ b/locale/uk/knowledge/javascript-conventions/how-to-create-default-parameters-for-functions.md @@ -36,7 +36,6 @@ The first idiom is giving a default value for the last parameter. This is done b example(""); betterExample(""); - If the optional value is in the middle it can cause some undesired effects, since all the parameters are shifted over. The optional parameter is not the `undefined` value in this case - the last parameter is the `undefined` one. So you have to check if the last parameter is `undefined` and then manually fix all the other parameters before continuing in the code. This example shows you how to do that: example = function (param1, optParam, callback) { diff --git a/locale/uk/knowledge/javascript-conventions/what-are-the-built-in-timer-functions.md b/locale/uk/knowledge/javascript-conventions/what-are-the-built-in-timer-functions.md index 1159525e33f7e..e4b0de6d6f07c 100644 --- a/locale/uk/knowledge/javascript-conventions/what-are-the-built-in-timer-functions.md +++ b/locale/uk/knowledge/javascript-conventions/what-are-the-built-in-timer-functions.md @@ -58,7 +58,6 @@ The final trick for the timer objects is you can pass parameters to the callback setTimeout(console.log, 1000, "This", "has", 4, "parameters"); setInterval(console.log, 1000, "This only has one"); - This has 4 parameters This only has one This only has one diff --git a/locale/zh-cn/docs/guides/abi-stability.md b/locale/zh-cn/docs/guides/abi-stability.md index 504f68cd7f308..c817d985ed4e2 100644 --- a/locale/zh-cn/docs/guides/abi-stability.md +++ b/locale/zh-cn/docs/guides/abi-stability.md @@ -28,7 +28,6 @@ Node.js 提供的一些头文件是由几个独立的团队维护的。举个例 对于这些收束，Node.js 已在版本 8.6.0 中引入了 N-API 并将其标记为项目的稳定组件——如 Node.js 8.12.0。这些 API 在头文件 [`node_api.h`][] 和 [`node_api_types.h`][]中定义，并提供跨越 Node.js 主要版本边界的前向兼容性保证。保证可以说明如下: - **N-API 的给定版本 *N* 将在其发布的 Node.js 的主要版本和所有后续版本的 Node.js 中提供，包括后续的主要版本。** 本地插件开发者可以通过确保插件只使用 `node_api.h` 中定义的 API 以及在 `node_api_types.h` 中定义的数据结构和常量，利用 N-API 向前兼容性保证。由此方式，开发者通过向生产用户表明其应用程序的维护负担将增加，而不是通过添加一个纯粹由 JavaScript 编写的包，从而简化其插件的采用。 diff --git a/locale/zh-cn/docs/guides/anatomy-of-an-http-transaction.md b/locale/zh-cn/docs/guides/anatomy-of-an-http-transaction.md index 167c7744eda83..3a49acfe91772 100644 --- a/locale/zh-cn/docs/guides/anatomy-of-an-http-transaction.md +++ b/locale/zh-cn/docs/guides/anatomy-of-an-http-transaction.md @@ -119,7 +119,6 @@ http.createServer((request, response) => { 谈了那么就，我们都还没有说到 `response` 对象。它是一个 [`ServerResponse`][] 实例，而 ServerRespose 又是 [`WritableStream`][]。它包含了很多方法可以用以把数据返回给客户端。我们下面就将涉及到此议题。 - ## HTTP 状态码 如果你嫌麻烦不想设置它，返回客户端的默认状态码总是 200。当然，不是每个 HTTP 返回码必须都是 200，在某些情况下你一定希望返回一个不同的状态码，所以你应该设置 `statusCode` 属性。 @@ -322,8 +321,6 @@ http.createServer((request, response) => { 从这些基础知识中，关于 Node.js 的 HTTP 服务一些实用案例已经逐步被构建起来，API 文档还提供了大量其它的说明，所以请详细阅读 [`EventEmitters`][]，[`Streams`][] 以及 [`HTTP`][]。 - - [`EventEmitters`]: https://nodejs.org/api/events.html [`Streams`]: https://nodejs.org/api/stream.html [`createServer`]: https://nodejs.org/api/http.html#http_http_createserver_requestlistener diff --git a/locale/zh-cn/docs/guides/backpressuring-in-streams.md b/locale/zh-cn/docs/guides/backpressuring-in-streams.md index e2fdcac4ee9e7..7997c3308797a 100644 --- a/locale/zh-cn/docs/guides/backpressuring-in-streams.md +++ b/locale/zh-cn/docs/guides/backpressuring-in-streams.md @@ -447,7 +447,6 @@ function doUncork(stream) { 在此之后请仔细阅读更多的有关 [`Stream`][] 其它 API 函数，这样有助于当你在构建 Node.js 的应用程序之时更好地理解关于流的能力。 - [`Stream`]: https://nodejs.org/api/stream.html [`Buffer`]: https://nodejs.org/api/buffer.html [`EventEmitter`]: https://nodejs.org/api/events.html diff --git a/locale/zh-cn/docs/guides/blocking-vs-non-blocking.md b/locale/zh-cn/docs/guides/blocking-vs-non-blocking.md index 5fd9ac14ffb72..2a8079c99fea2 100644 --- a/locale/zh-cn/docs/guides/blocking-vs-non-blocking.md +++ b/locale/zh-cn/docs/guides/blocking-vs-non-blocking.md @@ -17,7 +17,6 @@ layout: docs.hbs 在 Node.js 标准库中的所有 I/O 方法都提供异步版本，**非阻塞**，并且接受回调函数。某些方法也有对应的 **阻塞** 版本，名字以 `Sync` 结尾。 - ## 代码比较 **阻塞** 方法 **同步** 执行，**非阻塞** 方法 **异步** 执行。 @@ -62,7 +61,6 @@ moreWork(); // 在console.log之前执行 在上述第一个例子中， `console.log` 将在 `moreWork()` 之前被调用。在第二个例子中， `fs.readFile()` 是 **非阻塞** 的，所以 JavaScript 执行可以继续， `moreWork()` 将被首先调用。在不等待文件读取完成的情况下运行 `moreWork（）` 的能力是一个可以提高吞吐量的关键设计选择。 - ## 并发和吞吐量 在 Node.js 中 JavaScript 的执行是单线程的，因此并发性是指事件循环在完成其他工作后执行 JavaScript 回调函数的能力。任何预期以并行方式运行的代码必须让事件循环继续运行，因为非 JavaScript 操作（像 I/O ）正在发生。 @@ -71,7 +69,6 @@ moreWork(); // 在console.log之前执行 事件循环不同于许多其他语言的模型，其它语言创建额外线程来处理并发工作。 - ## 混合阻塞和非阻塞代码的危险 处理 I/O 时应该避免一些模式。我们来看一个例子： @@ -100,7 +97,6 @@ fs.readFile('/file.md', (readFileErr, data) => { 以上代码在 `fs.readFile()` 的回调中对 `fs.unlink()` 进行了 **非阻塞** 调用，这保证了正确的操作顺序。 - ## 其它资源 - [libuv](https://libuv.org/) diff --git a/locale/zh-cn/docs/guides/diagnostics-flamegraph.md b/locale/zh-cn/docs/guides/diagnostics-flamegraph.md index 4437ec08ad5af..99c3d7cf4e29a 100644 --- a/locale/zh-cn/docs/guides/diagnostics-flamegraph.md +++ b/locale/zh-cn/docs/guides/diagnostics-flamegraph.md @@ -111,7 +111,6 @@ node`_ZN2v88internal11interpreter17BytecodeGenerator15VisitStatementsEPNS0_8Zone ``` 这意味着你正在运行的 Linux 的 perf 没有用 demangle 支持方法编译，请以 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1396654 作为示例参考。 - ## 示例部分 请通过[火焰图练习](https://github.com/naugtur/node-example-flamegraph)来练习捕获你的火焰图吧！ diff --git a/locale/zh-cn/docs/guides/domain-postmortem.md b/locale/zh-cn/docs/guides/domain-postmortem.md index 1377a2d5b454e..1819b0324b435 100644 --- a/locale/zh-cn/docs/guides/domain-postmortem.md +++ b/locale/zh-cn/docs/guides/domain-postmortem.md @@ -18,13 +18,11 @@ layout: docs.hbs const b = require('./b'); const c = require('./c'); - // module b.js const d = require('domain').create(); d.on('error', () => { /* silence everything */ }); d.enter(); - // module c.js const dep = require('some-dep'); dep.method(); // Uh-oh! This method doesn't actually exist. @@ -75,12 +73,10 @@ d.run(() => { 可以预期嵌套域始终保持嵌套，并且总是将异常传播到域堆栈上。或者那些例外不会自动发生冒泡。不幸的是，这两种情况都会发生，导致可能混淆的行为，甚至可能很难调试时序冲突。 - ### API 缺陷 虽然基于 `EventEmitter` 的 API 可以使用 `bind()` ，而错误回调风格的回调可以使用 `intercept()`，但是隐式绑定到活动域的替代 API 必须在 `run()` 中执行。这意思是，如果模块作者想用一种机制来支持域，那么就可以使用必须手动实现域自身的支持机制。而不是能够利用已经存在的隐含机制。 - ### 错误传递 如果可能的话，跨嵌套域传播错误不是直截了当的。现有文档显示了在请求处理程序中出现错误时如何使用 `close()` 方法关闭 `http` 服务器的简单示例。它没有解释的是，如果请求处理程序为另一个异步请求创建另一个域实例，则如何关闭服务器。以下作为错误传播失败的简单例子： @@ -109,7 +105,6 @@ d1.run(() => setTimeout(() => { 这可能被认为是 API 的一个失败，但即使确定它在这方面可以运行，还有一个问题，就是当异步执行中的某个分支发生了失败，那么所有进一步的操作都必须终止。在 http 请求处理程序的示例中，如果我们发起几个异步请求，然后每个 `write()` 方法数据返回到客户端，试图对一个已经关闭的处理调用 `write()` 方法时会出现更多的错误。关于 _异常的资源清理_ 中对此进行了更多的讨论。 - ### 异常的资源清理 下面的脚本包含一个更复杂的示例。它是关于在一个小的资源依赖树中正确资源清理，在一个给定的连接或其任何依赖关系中发生异常的情况下，将脚本分解为基本操作： @@ -269,7 +264,6 @@ process.on('exit', () => { 最后，在处理错误方面，域不仅仅是一个值得骄傲的 `'uncaughtException'` 处理程序。除第三方更隐秘和不可观察的行为以外。 - ### 资源传播 域的另一个用例是使用它来沿着异步数据路径传播数据。一个问题是当在堆栈中有多个时，期望何时得到正确的域的模糊性（必须假定）。异步堆栈与其它模块一起工作。还可以依赖于域进行错误处理，同时也有可能用于检索必要的数据。 @@ -331,7 +325,6 @@ DataStream.prototype.data = function data(chunk) { 简而言之，倘若要祈祷有机会运用这样的方式处理问题，需要严格遵守一组很难实施或测试的指导方针。 - ## 性能问题 使用域名的显著威慑是开销。使用节点内置的 http 基准，`http_simple.js`，没有域，它可以处理超 22000 个请求/秒。而如果它运行的是 `NODE_USE_DOMAINS=1`，则该数字下降到 17000个请求/秒以下。在这种情况下只有一个全局域。如果我们编辑基准，那么 http 请求回调会创建一个新的域实例，性能进一步下降到 15000 个请求/秒。 @@ -341,7 +334,6 @@ DataStream.prototype.data = function data(chunk) { 使用 `AsyncWrap` 并跟踪次数 `init`/`pre`/`post`/`destroy` 在以上基准中所提及，我们发现所有事件的总和超过每秒 170000 次。这意味着即使为每种类型的设置增加 1 微秒的开销，任何类型的安装或拆除都会导致 17% 的性能损失。当然，这是针对基准的优化方案，但我相信这证明了一种机制，如域尽可能简单方便地运行的必要性。 - ## 展望未来 自从 2014 年 12 月以来，域模块已经被软弃用，但由于节点目前暂时没有替代功能，所以还没有彻底被移除。在撰写本文时，`AsyncWrap` 的 API 的工作正在进行，以及为 TC39 准备的区域的建议。在这种时候，如有合适的功能来替换域，它将经历完整的弃用周期而最终从核心移除。 diff --git a/locale/zh-cn/docs/guides/event-loop-timers-and-nexttick.md b/locale/zh-cn/docs/guides/event-loop-timers-and-nexttick.md index 53fd8ef29d980..c6ea6c1b27e4f 100644 --- a/locale/zh-cn/docs/guides/event-loop-timers-and-nexttick.md +++ b/locale/zh-cn/docs/guides/event-loop-timers-and-nexttick.md @@ -46,7 +46,6 @@ layout: docs.hbs _**注意：** 在 Windows 和 Unix/Linux 实现之间存在细微的差异，但这对演示来说并不重要。最重要的部分在这里。实际上有七或八个步骤，但我们关心的是 Node.js 实际上使用以上的某些步骤。_ - ## 阶段概述 * **定时器**：本阶段执行已经安排的 `setTimeout()` 和 `setInterval()` 的回调函数。 @@ -84,7 +83,6 @@ setTimeout(() => { console.log(`${delay}ms have passed since I was scheduled`); }, 100); - // do someAsyncOperation which takes 95 ms to complete someAsyncOperation(() => { const startCallback = Date.now(); diff --git a/locale/zh-cn/docs/guides/index.md b/locale/zh-cn/docs/guides/index.md index b5db138be9af0..7cb8485bf478d 100644 --- a/locale/zh-cn/docs/guides/index.md +++ b/locale/zh-cn/docs/guides/index.md @@ -14,7 +14,6 @@ layout: docs.hbs - [将 Node.js 网络应用安装到 Docker 中](nodejs-docker-webapp/) - [迁移到安全的 Buffer 构造函数中](buffer-constructor-deprecation/) - ## Node.js 核心概念 - [阻塞对比非阻塞一览](blocking-vs-non-blocking/) @@ -22,7 +21,6 @@ layout: docs.hbs - [不要阻塞你的事件轮询（或是工作池）](dont-block-the-event-loop/) - [Node.js 中的定时器](timers-in-node/) - ## 与模块相关的指南 - [HTTP 传输解析](anatomy-of-an-http-transaction/) diff --git a/locale/zh-cn/docs/guides/nodejs-docker-webapp.md b/locale/zh-cn/docs/guides/nodejs-docker-webapp.md index 1fc27420089cc..9b5fcc6bb3aff 100644 --- a/locale/zh-cn/docs/guides/nodejs-docker-webapp.md +++ b/locale/zh-cn/docs/guides/nodejs-docker-webapp.md @@ -11,7 +11,6 @@ layout: docs.hbs Docker 允许你以应用程序所有的依赖全部打包成一个标准化的单元，这被成为一个容器。对于应用开发而言，一个容器就是一个蜕化到最基础的 Linux 操作系统。一个镜像是你加载到容器中的软件。 - ## 创建 Node.js 应用 首先，创建一个新文件夹以便于容纳需要的所有文件，并且在此其中创建一个 `package.json` 文件，描述你应用程序以及需要的依赖： diff --git a/locale/zh-cn/docs/guides/working-with-different-filesystems.md b/locale/zh-cn/docs/guides/working-with-different-filesystems.md index f2582cd368a70..0abc65e8ba9f1 100644 --- a/locale/zh-cn/docs/guides/working-with-different-filesystems.md +++ b/locale/zh-cn/docs/guides/working-with-different-filesystems.md @@ -68,7 +68,6 @@ Unicode 不敏感编码和 Unicode 编码保存是两种不同的文件系统行 请注意，使用 `normalize()` 要求您的 Node 版本包括 ICU（否则 `normalize()` 函数将只返回原始字符串）。如果您从网站下载最新版本的 Node，那么它将包括 ICU。 - ## 时间戳解析 您可以将文件的 `mtime`（修改后的时间）设置为 `1444291759414`（毫秒分辨率），有时会惊讶地看到 `fs.stat` 返回新的 mtime 为 `1444291759000`（1 秒分辨率）或 `1444291758000`（2 秒分辨率）。这不是 Node 的 bug。Node 在文件系统存储时返回时间戳，而不是所有文件系统都支持纳秒、毫秒或 1 秒的时间戳解析。某些文件系统甚至对 atime 有非常粗略的分辨率。例如，某些 FAT 文件系统的 24 小时。 diff --git a/locale/zh-cn/download/package-manager.md b/locale/zh-cn/download/package-manager.md index 70034b822d799..fc4accf6e2138 100644 --- a/locale/zh-cn/download/package-manager.md +++ b/locale/zh-cn/download/package-manager.md @@ -214,7 +214,6 @@ pkgin -y install nodejs cd pkgsrc/lang/nodejs && bmake install ``` - ## Solus 在主版本库中，Solus 提供了 node.js。 @@ -223,7 +222,6 @@ cd pkgsrc/lang/nodejs && bmake install sudo eopkg install nodejs ``` - ## Void Linux 在主版本库中 Void Linux 发布稳定的 node.js。 diff --git a/locale/zh-cn/download/releases.md b/locale/zh-cn/download/releases.md index a1e426a8a6968..0abf377602a1a 100644 --- a/locale/zh-cn/download/releases.md +++ b/locale/zh-cn/download/releases.md @@ -19,4 +19,3 @@ modules: "NODE_MODULE_VERSION 指的是 Node.js 的 ABI (applicatio
  • all versions
    • - diff --git a/locale/zh-cn/get-involved/index.md b/locale/zh-cn/get-involved/index.md index 98da497d58951..2c41262eed4ce 100644 --- a/locale/zh-cn/get-involved/index.md +++ b/locale/zh-cn/get-involved/index.md @@ -15,7 +15,6 @@ layout: contribute.hbs - [Node.js Collection](https://medium.com/the-node-js-collection) 是一堆在媒体上的社区策划内容集合。 - [Community Committee](https://github.com/nodejs/community-committee) 是 Node.js 基金会中的高级委员会，专注于社区事务。 - ## 学习资源 - [官方 API 参考文档](/api/) 中详细介绍了 Node 的 API 函数。 diff --git a/locale/zh-cn/security.md b/locale/zh-cn/security.md index 4cd07ce9737a6..0e559beb80b31 100644 --- a/locale/zh-cn/security.md +++ b/locale/zh-cn/security.md @@ -45,7 +45,6 @@ Node.js 项目参与了一个为安全研究员和负责任的公众披露者的 - 这个过程可能需要一些时间，特别是当需要与其他项目的维护人员进行协调时。但是将尽一切努力尽可能及时地处理 缺陷漏洞。但是我们仍必须遵循上面的发布过程，以确保以一致的方式处理泄漏。 - ## 收到安全更新 安全通告将通过以下方式发布： diff --git a/locale/zh-tw/download/package-manager.md b/locale/zh-tw/download/package-manager.md index eaa90b233df62..a05eb19e75691 100644 --- a/locale/zh-tw/download/package-manager.md +++ b/locale/zh-tw/download/package-manager.md @@ -212,7 +212,6 @@ pkgin -y install nodejs cd pkgsrc/lang/nodejs && bmake install ``` - ## Solus Solus 在其主要軟體庫中提供了 Node.js。 @@ -221,7 +220,6 @@ Solus 在其主要軟體庫中提供了 Node.js。 sudo eopkg install nodejs ``` - ## Void Linux Void Linux 在其主要軟體庫中提供了 Node.js 穩定版。 diff --git a/locale/zh-tw/download/releases.md b/locale/zh-tw/download/releases.md index 39184408c13fd..037cfb0fb2a09 100644 --- a/locale/zh-tw/download/releases.md +++ b/locale/zh-tw/download/releases.md @@ -19,4 +19,3 @@ modules: "NODE_MODULE_VERSION 是 Node.js ABI (application binary i
  • 所有版本
    • - diff --git a/locale/zh-tw/get-involved/index.md b/locale/zh-tw/get-involved/index.md index da55bc9d9fb61..3d3553cca1ebf 100644 --- a/locale/zh-tw/get-involved/index.md +++ b/locale/zh-tw/get-involved/index.md @@ -15,7 +15,6 @@ layout: contribute.hbs - [Node.js Collection](https://medium.com/the-node-js-collection) 是個由社群策劃的 Medium 文章合集。 - [Community Committee](https://github.com/nodejs/community-committee) 是 Node.js 基金會中的高級委員會，專責社群事務。 - ## 學習資源 - [官方 API 參考文件](/api/)中詳細介紹了 Node API。 @@ -24,7 +23,6 @@ layout: contribute.hbs - [開發社區上的 Node.js 標籤](https://dev.to/t/node) 是一個共亯 Node.js項目、文章和教程，以及開始討論、並接受與 Node.js 相關的主題。歡迎所有技能級別的開發人員參與。 - [Nodeiflux](https://discordapp.com/invite/vUsrbjd) 是一個 Nodejs 後端開發者在 Discord 上互相支援的友好社區。 - ## 國際性社群網站及專案 - [漢語社群](https://cnodejs.org/) diff --git a/tests/scripts/CHANGELOG.fixture.md b/tests/scripts/CHANGELOG.fixture.md index c08ad273553e1..76d52a281c960 100644 --- a/tests/scripts/CHANGELOG.fixture.md +++ b/tests/scripts/CHANGELOG.fixture.md @@ -40,7 +40,6 @@ * [io.js](CHANGELOG_IOJS.md) * [Archive](CHANGELOG_ARCHIVE.md) - **Note:** Node.js v4 is covered by the [Node.js Long Term Support Plan](https://github.com/nodejs/LTS) and will be supported actively until April 2017 and maintained until April 2018. @@ -1308,7 +1307,6 @@ See https://github.com/nodejs/node/labels/confirmed-bug for complete and current ### Commits - * [[`8383c4fe00`](https://github.com/nodejs/node/commit/8383c4fe00)] - **assert**: support arrow functions in .throws() (Ben Noordhuis) [#3276](https://github.com/nodejs/node/pull/3276) * [[`3eaa593a32`](https://github.com/nodejs/node/commit/3eaa593a32)] - **async_wrap**: correctly pass parent to init callback (Trevor Norris) [#3216](https://github.com/nodejs/node/pull/3216) * [[`54795620f6`](https://github.com/nodejs/node/commit/54795620f6)] - **buffer**: don't abort on prototype getters (Trevor Norris) [#3302](https://github.com/nodejs/node/pull/3302)
    التخصيصالمعنى