The asset pipline isn't removed, so you don't need to do anything special.
That said, I don't think that it's ideal for heavy JS apps. Lots of possible work that could be done in this area.
That said, I don't think that it's ideal for heavy JS apps. Lots of possible work that could be done in this area.
Rails-api churns out JSON, JS consumes it. I can think of performance being an issue.
What are the other issues?
Also, the pipeline has been re-written for Rails 4, but historically it's been kinda slow and buggy.
For an example of what I'm thinking about, rake-pipeline-web is interesting.