Laravel can act as the API backend to the frontend (basically a set of REST endpoints that the frontend can talk to), or alternatively the Vue components are used only where heavy client-side interactions are required, while the rest of the pages are still served up by Laravel normally.
For websockets, as an example, HHVM+proxygen should be as performant as node. Or, node should be roughly as good as php for developer speed on the normal, not-websockets side of the house.
Edit: For clarity, I mean there would be significant overlap in areas like data retrieval, sessions/auth, etc.
A Reddit like app would have read/write to and from the browser and to and from the database for many data structures. Users, admins, moderators, topic areas, topics, threads, users, etc. And different views depending on context. You see more of your own profile, less of others...and similar for moderated topic areas and so forth. So, 2 platforms means duplication of some of this data access, update, marshalling, acls, sessions, etc.
Assuming the node.js part is for the "real time posts", via websockets, it would need most of the above. Then, assuming php is handling the rest, including profile edit, rendering everything but the posts, etc...it also needs most of the above.
I assume that both would need to understand the concepts around: users, admins, moderators, topic areas, topics, threads, banning, moderating, vote counts, sessions, and so forth. And interacting with all of that both server<->browser and server<->database. Feels like a lot of duplicated classes, marshalling, etc.
Why? PHP works fine as a daemon, there are many servers written in pure PHP, as well as frameworks for "async" programming.
I guess we come back to _just because you can doesn't mean you should_. :)
Is there another Laravel other than the php one? Seems odd to roll out with both php and node.js. I don't know why you would need both.
Edit: Yes, I see each has it's strengths. But that has to drive a lot of doing the same thing twice, in two languages...they both interact with the same data. I would guess time-to-market is important at launch to react to things you missed. I would have settled on one or the other. Feels like premature optimization.