As someone who unsuccessfully tried it, replacing the asset pipeline without using gem versions of npm packages
-
-
-
Say more?
-
So asset pipeline + SPA = pain. Some get around that with creating a gem. That gem is tied to a (usually old) version of a JS asset. /1
-
The gem (e.g., bootstrap-rails) forces choosing between an old version of a front end asset or reimplementing workarounds for how the /2
-
Asset pipeline clobbers JS. No chance of lazy loading. Loses a lot of benefits with front end frameworks. /3
-
That said, it looks like ember has updated ember-rails gem to work around these issues pretty well since I last checked.
/4 -
I think ember-rails should use ember-cli
-
Ember-Cli-rails is a thing
- 1 more reply
New conversation -
-
-
thoughtbot/ember-cli-rails got us a long way there but could be better (at performance, caching, use middleware not controllers?)
-
Can you unpack those issues?
-
Performance/Caching: if you restart the Rails server, ember-cli-rails / `ember build` has to rebuild your assets from scratch
-
It'd be cool if either was faster at figuring out what hasn't changed since last build
End of conversation
New conversation -
-
-
My biggest win came with decoupling the client from the api and quitting trying to integrate ember into Rails assets.
-
Me too. Originally used Ember App Kit Rails. But switched over to cli and just used a catch all route in rails. Very few Rails views now.
End of conversation
New conversation -
-
-
JSONAPI integration -- both serialization/deserialization, and no compound doc saving
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Auth should be straight forward with ember-simple-Auth and the rails_api_auth engine
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
ember-data and rails controller boilerplate; tho perhaps solved with action model serializer now?
-
Have a look at https://github.com/cerebris/jsonapi-resources … - might solve the problem
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.