From 30048ea63358126a3f13622931526be7bd6fef9a Mon Sep 17 00:00:00 2001 From: Hans Kristian Flaatten Date: Sun, 1 Mar 2015 22:07:49 +0100 Subject: [PATCH] WIP --- _posts/2015-02-27-ukens-oppdatering.md | 166 +++++++++++++++++++++++++ 1 file changed, 166 insertions(+) create mode 100644 _posts/2015-02-27-ukens-oppdatering.md diff --git a/_posts/2015-02-27-ukens-oppdatering.md b/_posts/2015-02-27-ukens-oppdatering.md new file mode 100644 index 0000000..92cd3fa --- /dev/null +++ b/_posts/2015-02-27-ukens-oppdatering.md @@ -0,0 +1,166 @@ +--- +layout: left_align +title: Ukens oppdatering, 27. februar 2015 +date: "2015-02-20 21:20:00 +0100" +author: iojs +translator: starefossen +source: https://medium.com/node-js-javascript/io-js-week-of-february-17th-9422a589302a +--- + +## {{ page.title }} + +ARMv8, C++ Streams, 1.4.1-lansering, et forslag til forsoning, og mer. + +## io.js 1.4.1 er lansert + +*Merk: versjon **1.4.0** ble tagget og bygget, men lbe ikke lansert. En bug i +libuv ble oppdaget underveis slik at lanseringen ble avbrutt. Vi har hoppet til +1.4.1 til unngå forvirring.* + +### Viktige endringer + +* **process / promises:** En `unhandledRejection` hendelse blir sendt fra + process hver gang et Promise blir avvist og ingen feilshåndteringsfuksjon er + tilknyttet innen en runde av event loopen. En `rejectionHandled` hendelse blir + sendt når et Promise blir avvist og en feilshåndteringsfuksjon ble tilknyttet + etter en runde av event loopen. + [#758](https://github.com/iojs/io.js/pull/758) (Petka Antonov) + +* **streams:** Du kan nå bruke vanlige streams som underliggende socket for + `tls.connect()` [#926](https://github.com/iojs/io.js/pull/926) (Fedor Indutny) + +* **http:** En `abort` hendelse blir sendt når en `http.ClientRequest` blir + avbrudt av klienten. [#945](https://github.com/iojs/io.js/pull/945) (Evan + Lucas) + +* **V8:** Ble oppgradert til 4.1.0.21. Denne versjonen inkluderer en + hemmeligholdt feilretting, detaljer vil bli tilgjenglig når hemmeligholdet + blir opphevet. En ikke-bakoverkomptibel ABI-endringer har blitt holdt tilbake + fra denne oppgraderingen, som mulighens blir inkludert når io.js merger V8 + 4.2. Se [#952](https://github.com/iojs/io.js/pull/952) for diskusjon. + +* **npm**: Ble oppgradert til 2.6.0. Denne versjonen inkluderer funksjoner for å + støtte det nye registeret og forbedrede for `npm@3`. Se [npm sin + endringslogg](https://github.com/npm/npm/blob/master/CHANGELOG.md#v260-2015-02-12) + for flere detaljer. Sammendrag: + + * [#5068](https://github.com/npm/npm/issues/5068) Lagt til ny logg ut kommand, + og gjør den brukelig for både `bearer-based` og `basic-based` autentiserte + klienter. + + * [#6565](https://github.com/npm/npm/issues/6565) Advare om at oppførselen til + `peerDependency` kommer til å bli endret. + + * [#7171](https://github.com/npm/npm/issues/7171) Advare om at `engineStrict` + i `package.json` vil bli fjernet i neste større versjon av npm (kommer + snart!) + +* **libuv**: Ble oppgradert til 1.4.2. Se [libuv sin + endringslogg](https://github.com/libuv/libuv/blob/v1.x/ChangeLog) for flere + detaljer. + +## ARM offers support for io.js on ARMv8 + +ARM contacted Rod Vagg, lead of the io.js Build Working Group, to offer their +support to the io.js project. ARM and their hardware partners are on track to +make ARMv8 a viable server platform and the nimble nature of server-side +JavaScript make it a perfect fit to run on the new ARM. + +Since ARMv8 is already being adopted by mobile device manufacturers, newer +versions of V8 already have good support. Because of V8's pivotal role in +Android, io.js is perfectly suited to track that support, and even contribute +to it given our new relationships with the V8 team. + +From the beginning of the io.js project, Rod has championed the role of ARM for +io.js, for IoT, hobbyist, and server use. We already have ARMv6 builds of each +release for devices such as Raspberry Pi. and ARMv7 builds for many more +popular devices (including the Online Labs ARM-based cloud platform, who have +also offered help to io.js). ARMv8 is the logical extension of this, but also +has exciting potential for server-side applications, particularly given the new +64-bit support. + +The build team is in the process of being given access to the Linaro ARMv8 +Server Cluster for integration with the io.js CI platform, which should +eventually lead to regular ARMv8 binary releases. + +## Community Updates + +* [**Reconciliation Proposal**](https://github.com/iojs/io.js/issues/978): The + io.js project is preparing a plan for reconciliation that can be brought to + The Node.js Foundation. Input from the community is very important at this + early stage so please leave a comment. + +* **New internal C++ Streams API**: A [fresh C++ Streams + API](https://github.com/iojs/io.js/commit/b9686233fc0be679d7ba1262b611711629ee334e) + landed in io.js this week, allowing you to wrap a TLS stream into another TLS + stream. + +* **io.js Roadmap**: [The + Roadmap](https://github.com/iojs/io.js/blob/v1.x/ROADMAP.md) is the plan for + the future of io.js. It presents the plans for the stability policy, and lists + what the immediate priorities for io.js as a whole are. + +* **Roadmap Slides Finished and Ready for Translation**: The set of introductory + slides for the Roadmap of io.js [have been finished, and are ready for + translation](https://github.com/iojs/roadmap/issues/18). Do you think you + could present them to a group near you? Comment and we'll work with you to + prepare you to present! + +* **Microsoft io.js How-To for Azure Websites**: Microsoft [published a + how-to](http://azure.microsoft.com/en-us/documentation/articles/web-sites-nodejs-iojs/) + tutorial for their Azure platform that describes how to use io.js with Azure + Websites. + +* **Floobits moves to io.js**: The code pairing software Floobits [converted + their platform to + io.js](https://news.floobits.com/2015/02/23/on-moving-to-io.js/), in part + because of frustration with Node's slower release cycle, because the inclusion + of more ES6 features without the need for the `--harmony` flag, and because + they felt changes from 0.10.0 to 0.12.0 weren't very big. + +* **Anand Mani Sankar's _Node.js vs io.js: Why the fork?!?_**: Anand wrote a + good, for the most part objective, [post about the recent history of + io.js](http://anandmanisankar.com/posts/nodejs-iojs-why-the-fork/), and what + we hope to achieve with it. A good read for people who aren't engaged in the + community to catch up with. + +* **iojs-jp - New io.js Japanese Blog**: The iojs-jp community has created a + [localized io.js related blog](http://blog.iojs.jp/) to disseminate content in + their language. If you're interested, take a look! + +* **iojs-cn - New io.js Chinese Blog**: Similarly to the iojs-jp community, the + iojs-cn community created a [localized blog](http://cn.iojs.org/) to publish + posts about io.js to in their language. Make sure to visit if you're curious + about iojs-cn or Chinese news about io.js! + +* **[Roadmap Slides Review](https://www.youtube.com/watch?v=etI_UD4wXlo)** - A + review of the roadmap slides before they were released to ensure they met with + the message the project upholds. + +## io.js Support Added + +* **[Wallby.js](http://wallabyjs.com/)**, a while-you-write testing library for + JavaScript, hit version 1.0 and [added support for + io.js](http://dm.gl/2015/02/23/wallaby-version-one/)! + +* **[jsdom](https://github.com/tmpvar/jsdom)**, an implementation of the WHATWG + DOM and HTML standards, just hit [version + 4.0.0](https://github.com/tmpvar/jsdom/blob/master/Changelog.md#400), which + added a _requirement_ of io.js. + +* **[give](https://github.com/mmalecki/give)**'s creator + [tweeted](https://twitter.com/maciejmalecki/status/569629100215816192) that + newer versions of give support io.js. Give is a git-based node.js/io.js + version manager. + +* The **Firebase Realtime Client**, the official web/node.js JavaScript client + for Firebase, + [tweeted](https://twitter.com/FirebaseRelease/status/570000737343647744) + that they added support for io.js in [version + 2.2.1](https://www.firebase.com/docs/web/changelog.html#section-realtime-client) + +* **Semaphore**, a hosted continuous integrations service, + [tweeted](https://twitter.com/semaphoreapp/status/570987355005431809) about + added io.js support in their [Platform update on February 24th, + 2015](https://semaphoreapp.com/blog/2015/02/17/platform-update-on-february-24th.html). +