DailyJS

Node Roundup: npm jQuery, io.js 1.3.0, proginoskes

Alex R. Young

Subscribe

@dailyjs

Facebook

Google+

apps sponsored-content recruitment

Node Roundup: npm jQuery, io.js 1.3.0, proginoskes

Posted by Alex R. Young on .
Featured

apps sponsored-content recruitment

Node Roundup: npm jQuery, io.js 1.3.0, proginoskes

Posted by Alex R. Young on .

npm and jQuery

It's finally happened: jQuery is recommending npm for distributing plugins. My preferred client-side workflow is npm and Browserify, but I know many readers use Bower. Hopefully this shift will encourage more people to use npm for client-side libraries.

Lin Clark mentioned this in this week's npm Weekly, and also that npm has hit 1,000,000,000 downloads in a single month. Very impressive!

io.js 1.3.0

io.js 1.3.0 is out. As usual the details are in the nicely marked up changelog, which now contains links to commits. That makes it easier to look up what the commits actually do, because the one line descriptions can't always communicate the subtleties of the pull requests. You'll probably think I'm being sarcastic, but I was happy to see these changes:

It's all about attention to detail! In general this release feels like it's focused on quality control -- there are lots of JavaScript code quality fixes and documentation tweaks.

The new changelog formatting also lets you easily see which commits come from Node:

I think it's @rvagg who writes this document, so thanks Rod for making it easier for us to see what's going on.

proginoskes

Jason Gerfen sent in proginoskes (GitHub: jas-/proginoskes, License: MIT, npm: proginoskes), a module for monitoring logs from multiple sources by using SSH as the transport. It gives you an object stream, so you can format the results however you want. You can also easily see each source, because the objects have a server property.

This will work really well if you're used to writing ~/.ssh/config with aliases for servers and keys. The configuration options for proginoskes allow you to define the port, username, private key, and log file location. You could easily pipe your server logs to multiple locations for archival purposes, stats, and error notifications.

This project is based on the ssh2 module which is actually an SSH client by Brian White that's written in JavaScript. The ssh2 module also exposes a stream-based API, but for the underlying SSH protocol.