My team was trying to decide what Javascript libraries to use to build our web tier for our project. After spending a few days trying to get our heads around the ecosystem, we just gave up and went running back to Rails. Couldn't be happier.
The problem with node is that if you switch from something like Rails to node you'll also need to switch to an entirely different architecture.
While there are some Rails-like frameworks for node (e.g. Sails), node simply lends itself to a more service-oriented architecture, with lots of much smaller, much more specialised applications rather than one big monolithic MVC behemoth.
IOW, if you were able to replace your node app with Rails, you probably were trying to build a Rails app in the first place. Otherwise you'd probably have used something more like Sinatra.
Good decision. Single-page-apps should be called "hashtag-hack-pages". If you want a real app you can always pick a proper mobile framework later on (e.g. Xamarin or something Ruby-based).
Or you could, y'know, build an isomorphic app that can be used without page refreshes but can also be rendered on the server so you don't need a loading screen for every single route.
