ember-cli 0.0.43

Wheat Germ

on Node.js NPM

Upgrading

In order to ensure a safe and easy upgrade please follow the following steps (from within your project directory):

1. npm install -g ember-cli -- This ensures that your global version is up to date.
2. npm install --save-dev ember-cli -- This ensures that your project's version is up to date.
3. ember init -- This runs the new project blueprint on your projects directory. Please follow the prompts, and review all changes (tip: you can see a diff by pressing d). The most common source of upgrade pain is missing changes in this step.

Changelog

Applications

• ember new diff
• [BUGFIX] Fix ember init command in empty directory. #1779
• [ENHANCEMENT] Add triggerEvent to tests/.jshintrc. #1782
• [ENHANCEMENT] Allow opting out of analytics via .ember-cli config file. #1797
• Bump ember-cli-qunit version.
• [BUGFIX] Update broccoli-caching-writer dependents to allow linking fallback (enables easier usage of ember-cli from within Vagrant). #1799
• [BUGFIX] Avoid issue where ember init stalls on fresh system due to bower install prompting for permission to use analytics. #1805
• [BUGFIX] Allow usage of standard Node.js functionality in config/environments.js (fixes a regression in 0.0.42). #1809
• [ENHANCEMENT] Make current environment available modules. #1820
• [BUGFIX] Ensures that AppNameENV and EmberENV are setup before the vendor files have been loaded (changes in 0.0.42 caused enabling Ember feature flags impossible from config/environments.js). #1825
• [ENHANCEMENT] Ensures that the <base> tag changes when the config file is updated. #1825
• [ENHANCEMENT] Injects the /tests/index.html with the test environment configuration (was previously whatever server was running). #1825
• [ENHANCEMENT] bower_components and vendor are kept separate for import purposes. When we moved to separate directories for
  bower_components/ and vendor/ in 0.0.41, to allow for users to upgrade easier we merged those two folders into one single vendor
  tree. This meant that you would still app.import('vendor/baz/foo.js') and import Foo from 'vendor'; even if the file actually resides in
  bower_components/. This lead to much confusion and forced users to understand the internals that are going on (merging the two directories into vendor/).
  Now you would import things from bower_components/ or vendor/ if that is where they were on disk. #1836
• [BUGFIX] Allow nested output path, if path does not previously exist. #1872
• [ENHANCEMENT] Update ember-cli-qunit to 0.1.0. To avoid vendoring files in the addon and prevent having to run bower install within the addon
  itself (in a postinstall hook) the addon now installs its required packages directly into the applications bower.json file.
  This speeds up the build and make addon development much easier. #1877

Blueprints

• [BUGFIX] ember g http-proxy does not truncate the base path on proxied requests. #1874
• [ENHANCEMENT] Add empty function to ember g resource generator. #1817
• [ENHANCEMENT] Add {{outlet}} by default when generating a route template. #1819
• [ENHANCEMENT] Remove use of deprecated view.state property. #1826
• [BUGFIX] Allow blueprints without files. #1829
• [ENHANCEMENT] Make ember g adapter extend from application adapter if present. #1831
• [ENHANCEMENT] Add --base-class options to ember g adapter. #1831
• [BUGFIX] Quote module name in object literal for ember g http-mock. #1823
• [ENHANCEMENT] Add Blueprint.prototype.addBowerPackageToProject. #1830
• [ENHANCEMENT] Add Blueprint.prototype.insertIntoFile. #1857

Addons

• ember addon diff
• [ENHANCEMENT] Expose Addon.prototype.isDevelopingAddon function. #1785
• [ENHANCEMENT] Expose Addon.prototype.treeGenerator function, that automatically handles the
  returning an unwatchedTree vs the bare directory (therefore causing it to be watched). #1785
• [ENHANCEMENT] Add default Addon.prototype.blueprintsPath implementation. Now if an addon has a blueprints/ folder, it will be automatically used
  as the blueprintsPath. #1876