When Ember app is placed in Rails /app folder (i.e. default ember-cli-rails path), perf of Rails (rendering pages, serving assets, etc) degrades significantly due to large number of additional files (bower_components, node_modules) in Rails autoload path.
Quick profiling led to the following method call:
As a workaround, EmberCLI app can be just placed to any non-autoload path.
To avoid perf. problems I suggest the following:
I have only verified this issue on my local dev machine:
OS X 10.9.5
Yep, we've noticed that as well. I wonder if there's a way to tell reloader to skip certain directories entirely. I've googled around and it seems like there're none.
I guess we'll have to change the default directory for ember apps in the next major release.
@rwz I think that is probably a good idea. Kinda sucks for peeps with existent apps. Do you think we should display a depcrecation warning for people with cli-apps in that dir?
Yeah, I'm thinking of the best way to handle this.
Hello, I am running into the same problem, what would be a temporary fix? puts the emberjs app in a appjs folder? I also tested ember-rails but I feel I am gonna get stuck if I dont use ember-cli from the start.
@AlexCppns we've moved EmberCLI app into project root.
Deprecate putting Ember CLI app into Rails' app path
Change build_dir to `frontend`