So Remind Me Again, Why Do We Need the npm Registry?

While working on Supercomments [https://blog.salsitasoft.com/embed-reddit-comment-threads-right-on-your-blog-with-supercomments/] , I regularly came across third-party Node.js packages whose version in the npm registry was not the one I wanted. In most cases this was because the maintainer hadn't updated the version for a while, although in at least…

Library of The Week: Humane.js

Having covered Vex [https://blog.javascripting.com/2015/04/04/library-of-the-week-vex/] and SweetAlert [https://blog.javascripting.com/2015/05/09/library-of-the-week-sweetalert/], this week's topic is yet another notification library: Humane.js [https://www.javascripting.com/view/humane-js]. Humane has a slightly different purpose from the other two, which…

Library of The Week: Jailed

In the JavaScript world there is broad consensus about how to describe and exchange data: JSON. But some classes of application need more. In particular, you may need to describe and exchange behavior as well as data. It isn't easy to find a simple real-world example because you…

Library of The Week: SweetAlert

I have already written about Vex [https://blog.javascripting.com/2015/04/04/library-of-the-week-vex/], a library for creating modal dialogs. This week let's take a look at SweetAlert [http://www.javascripting.com/view/sweetalert], which is very similar to Vex. SweetAlert bills itself as "a beautiful replacement…

Library of The Week: Highland.js

A few weeks ago, writing about the increasingly obsolete Async.js, I promised to talk about Highland.js [http://highlandjs.org/]. This library is by Caolan McMahon, who also wrote Async.js, and can be considered its successor. Highland can be used as an alternative to promises for handling asynchronous…