Issues » 64

io.js, the new Node.js fork, top 10 Node mistakes, getting started with npm, and more.
Read this e-mail on the Web
Node Weekly
December 5, 2014  #64

A day late due to poor health, apologies! The io.js Node fork is a huge topic this week. It's too early to tell where things are going but for now both io.js and Node will be covered here. We have and on standby just in case ;-)

Alexandru Vladutu
A long piece but full of tips. Includes not using enough automated tools, blocking the event loop, poor logging, executing a callback multiple times, and more.

Lin Clark
npm Inc has released a set of videos covering how to use npm, how to install and manage packages, fix permissions, and more.

Semaphore   Sponsored
Test and deploy your projects direct from GitHub or Bitbucket with zero setup. Join GitLab, 500px and many more organizations who have improved their productivity with Semaphore’s fast processors and a dedicated RubyGems mirror.


Essentially a fork of Node, discussed in further links and stories below. Further discussion can also be found here.

Read Write
Lauren Orsini presents a simple, high level overview of the Node/io.js situation, and notes that Uber may be switching over to the io.js fork.

Paul Krill interviews io.js team member Mikeal Rogers about the motivation behind the fork.


In brief

Node Weekly is curated by Peter Cooper and published by Cooper Press.
Node.js is a trademark of Joyent, Inc. Used with kind permission.

Send feedback by simply replying to this mail.
Want to sponsor an issue? See our media kit.
Want to post a job? E-mail us or use our self-serve system.

Unsubscribe : Change email address : Read this issue on the Web

© Cooper Press Ltd. Office 30, Lincoln Way, Louth, LN11 0LS, UK
Email policy Privacy policy

ONE e-mail each Friday. Easy to unsubscribe. No spam — your e-mail address is safe
Published by Cooper Press