ember-cli

I'd like to know how I can use SASS within an Ember-CLI addon? I have my styles in /app/styles folder, but I'm not sure that's the right location to have them. I have broccoli-sass installed in my addon project, my Dummy test website compiles properly the scss files when I include my folder in /tests/dummy/app/styles/app.scss . @import 'app/styles/app.scss'; But I don't know how I can compile the scss files to go into the /dist/assets/vendors.css , which is the file loaded by projects using this addon. OK I just found out the solution The style folder needs to be in /addon/styles instead of

I've been injecting Google DFP ads in my blog-posts by using a bound helper so far. Since all Handlebars APIs have been removed in Ember 2.0 what can I use as of Ember 2.0 instead? import Ember from "ember"; export default Ember.Handlebars.makeBoundHelper(function(value, options) { var parsedHtml = Ember.$('<div />').html(value) // Push the ads after the divs have been rendered Ember.run.schedule('afterRender', function() { googletag.cmd.push(function() { googletag.display('div-gpt-ad-111111111-0'); }); }) } return parsedHtml.html() }); You would use the Ember.Helper.helper syntax: import

Running ember server works fine locally on my dev machine but how do I do it on my host? All I can do is upload the dist folder which contains the output of the CLI build. But when I navigate to it there is a blank page. Ember serve/server/s fires up a server for local development, you shouldn't use it's files to deploy on a live host. Starts up the server. Default port is 4200. Use --proxy flag to proxy all ajax requests to the given address. For example ember server --proxy http://127.0.0.1:8080 will proxy all your apps XHR to your server running at port 8080. When you want to deploy you

Specs: Ember version: 1.13.8 node: 0.10.33 npm: 2.13.4 I have import Alias from "../../../services/alias"; .... moduleFor("controller:test", "Controller: test", { integration: true, beforeEach: function() { this.register('service:alias', Alias, {singleton: true}); this.inject.service('alias', { as: 'alias' }); this.advanceReadiness(); }, }); ... test('Alias Alias Alias ', function(assert) { var controller = this.subject(); //sample function controller.send("test"); assert.equal(true, controller.alias.get("alias"), "alias should be true"); }); (Using 'alias' as example because I'm not allow to

After updating my app to Ember 1.12.0, I notice lots of warnings like this: lookup was called on a Registry. The initializer API no longer receives a container, and you should use an instanceInitializer to look up objects from the container. See http://emberjs.com/guides/deprecations#toc_deprecate-access-to-instances-in-initializers for more details. This seems to be caused by using container.lookup from an initializer, which was fine in older versions of Ember. From the blog post about Ember 1.12.0, it seems like in a Global-based Ember application, the difference between making an