socket.io or REST api?

[jaulz]

Any thoughts about how to integrate any of the both?

[iam4x]

For usage with socket.io, I would recommend reading: https://blog.rotenberg.io/million-user-webchat-with-full-stack-flux-react-redis-and-postgresql/

[jaulz]

Thanks for the link but I'm actually struggling where to exactly I should implement the API itself. Would you recommend to start a second project only for the API?

[iam4x]

With the new alt-resolver (#8) you can achieve easily the two possibilities:

fetch() {
  const promise = (resolve) => {
    if (process.env.BROWSER) {
      // fire xhr request
     users = xhr.fetch('http://example.com/api/users');
    }
    else {
      // retrieve users from database on the server
      const UserModel = require('user-model.js');
      users = UserModel.all();
    }
   return resolve();
  };
  altResolver.resolve(promise);
}

With UglifyJS well configured it will drop the condition as we build scripts for browser with process.env.BROWSER set to true.

[aegyed91]

So basically we have to make a separate node server as an api? Is there any way to simply ignore /api routes with react-router?

[iam4x]

@tsm91 you can: #45 (comment)

[aegyed91]

aaaa the middleware stack, i was putting api routes after react-router ;)

[aegyed91]

@iam4x i can't seem to get socket.io work while running webpack, i mean i constantly see the socketio pollings from browsersync and webpack probably.

any idea for that?

[iam4x]

I don't have any experience with socket.io sorry, but maybe would help: webpack/webpack-dev-server#76

[aegyed91]

Yep i've tried that, the original problem is, webpack-dev-server's socket connection is on the default path.
Browsersync have done this right by the way, and on top of that it even gives configuration options.

As mentioned here io({path: '/custom/path'}) will make socket.io to connect to window.location.href + the path specified, in my case http://localhost:3002/custom/path which normally would solve the problem however its not, it still picks up webpack-dev-server's emitted events, i think i wont implement socket.io for now xd