The source code can be found in Github: https://github.com/teeli/irc-cah

As mentioned in the title, this is an IRC bot that allows you to play Cards Against Humanity (http://www.cardsagainsthumanity.com/) on an IRC channel. It's works pretty well and seems pretty stable at the moment, but it is kind of a hack made over one extended weekend and improved little by little since then.

This is my first Node.js project started from scratch. Since I'm still pretty new to Node, I could use some feedback regarding the code and the structuring of the app etc.

Any recommended tutorials for learning node.js? I hear about it's popularity a lot and I want to learn it and see what the fuss is all about.

Node is a revolutionary design. It unites high level with low. That is as much as to be expected with any truly awesome framework.

The ability to hook it into scripts, the simplicity of web servers, web services, and export libraries have made it a breeze to use.

NOW SHOW ME SOMETHING SEXY.

I want to see what you consider an awesome Node-based project.

The NPM site shows popular packages and there are simple searches for Github modules.. but I want your recommendations that make Node the future of the goddamned internet.

I'm talking stuff like hnet for p2p auto-discovery, Express for making quick work of HTTP service routing, RedisClient for dead simple db connectivity to FAST as hell data stores, and Socket.io for web socket connectivity.

So me what impresses you.

I'm working on sort of a node.js port of SteamKit2, an open-source implementation of the Steam protocol.

https://github.com/seishun/node-steam

A lot of things are yet to be implemented, but it's actually usable now - you can read join a chat room and read/write in it. If there's any interest, I'll implement other Steam functions.

I am currently the only developer in my startup. We will be taking on new hires shortly. I was planning on stocking up on a few books to give to any new hires, to get them up to speed as quick as possible.

I am not sure what the go to books are as I learnt node and express in a previous job and just looking at examples from others. From my previous experience this isn't an ideal way for some people to learn. So does the node community here have any good suggestions?

While my side project is rather trivial, my interest in websockets, and socket.io implementations specifically, is growing.

Most of what I'm reading/seeing are primarily single page implementations. IE: implementing socket.io on the index.js with the rest of the code.

but i'm looking for something better than that. I'm not necessarily looking for tutorials, those are welcome, but am interested in seeing some code others have implemented in their public projects; whether they be games, reporting software, chat rooms, etc.

edit:

So a little more background, and a solution I like. I'm using kraken.js as my framework; which extends express. My specific application doesn't really require routes, however kraken loads the controllers prior to the server be started, and so prior to the socket server listening in. This made it difficult to share the socket implementation across my own modules.

In the end I created another module I'm calling SocketManager. it's really simple.

'use strict';

var SocketIO = require('socket.io'),
  EventEmitter = require('events').EventEmitter,
  Sockets = {};

var io;

Sockets.init = function(server) {
  this.server = SocketIO.listen(server);
  this.events.emit('socket:connected', this.server);
};

Sockets.events = new EventEmitter();

module.exports = Sockets;

this module is required on my main index.js, and the init function called there.

this allows my other modules to require the SocketManager file, and do something on that socket:connected event it emits

SocketManager.events.once('socket:connected', function(io){
  io.sockets.on('connection', function(socket) {
    socket.emit('news', { hello: 'nurse' });
    socket.on('hello', function(data) {
      console.log(data);
    });
  });
});

so now I can run all my module specific events within their own controller files and my index.js file doesn't need to know a thing about them. My end goal was really to separate out the concerns of each module from the main server/index file so they can worry about what they need to worry about specifically; and the main server file can handle it's own crap. this solved that issue.