I like the idea of this - especially for apps where rails is implemented more as an api server. I’ll be wanting to take a look at this asap. The fact that this is possible really highlights, IMO, that the the client and server can and should be neatly decoupled.
If you’re using Rails as an API, this is exactly what you don’t want, since it mixes the concerns of your front-end and back-end. Put that in a different front-end repository. Having more than one package manager in a repository is a big red flag.
I’ve been doing that of late by adding another repo… and a csrf exception. I guess I interpreted this as a move by rails to decouple and play a bit better with front-end frameworks. We’ll see! I’m with you though in that I’m kind of liking separate repos for front and back ends
I’m really glad that DHH is really starting to think about this. It’s long overdue – IMO, this should have been the focus for Rails 5, not ActionCable – but I’m glad it’s happening.