Express 4 and Socket.io: Passing socket.io to routes.

Express 4 and Socket.io: Passing socket.io to routes - app.js

var app = express();
app.io = require('socket.io')();

var routes = require('./routes/index')(app.io);

app.use('/', routes);

index.js

//Normal code here

//then at the bottom:

module.exports = function (io) {
    //Socket.IO
    io.on('connection', function (socket) {
        console.log('User has connected to Index');
        //ON Events
        socket.on('admin', function () {
            console.log('Successful Socket Test');
        });

        //End ON Events
    });
    return router;
};

www

/**
 * Create HTTP server
 */

var server = http.createServer(app);
app.io.attach(server);
/**
 * Listen on provided port, on all network interfaces.
 */

server.listen(port);
server.on('error', onError);
server.on('listening', onListening);


/**
 * Normalize a port into a number, string, or false.
 */

Other sources of information on this topic:

http://stackoverflow.com/questions/31016350/using-socket-io-with-express-4-generator
expressjs/generator#25

thanks

thanks a lot

ulllltra thx :)

thank pro

i am getting error from index.js router undefined

wow what amazing, good person

amazing, thank you so much

nice, thank you

Do I also need to call the app route to access socket.io defined inside it?

THANKS A TON!

This works only with route associated with index.js, right? So if you have "global" connection/disconnect/reconect events it will duplicate the event and send the emits multiple times?

This works only with route associated with index.js, right? So if you have "global" connection/disconnect/reconect events it will duplicate the event and send the emits multiple times?

You say exactly, I had the same problem reloading the page and getting 1 more socket connection And I don't know how to handle it ..

This works only with route associated with index.js, right? So if you have "global" connection/disconnect/reconect events it will duplicate the event and send the emits multiple times?

You say exactly, I had the same problem reloading the page and getting 1 more socket connection And I don't know how to handle it ..

Use app.use(routes) instead app.use("/", routes)