• Fixes an issue with fs-extra (https://github.com/felixrieseberg/ember-electron/pull/321)

• Upgrade to electron-forge 4.1.1 • Dead-simple ember-enginges support (thanks to https://github.com/XaserAcheron)

This release upgrades the version of electron-forge to 4.x, which in turn fixes a few bugs and upgrades electron-packager to 9.x.

This release contains a few crucial fixes:

• @ursm moved ember-electron's main file to the ember-electron folder to save it from Ember's babel, which doesn't really know what we in Node-land mean when we call require. (#285)
• @bendemboski fixed symlink issues (#274)
• @bendemboski also enabled main process debugging (#237)

This release comes shortly after the initial release of ember-electron v2 and contains two additions:

• @bendemboski spent some time reworking the build pipeline, making it more efficient and easier to inspect from the outside. This change also introduces a fancy new command (ember electron:assemble), which builds the Ember App as used by ember-electron.
• @pichfl updated the addon to Ember Cli to 2.12

:sparkles: Woah, a complete rewrite! This version is a major bump and contains many breaking changes - please make sure to read the upgrade guide before updating your version.

Why a rewrite

As the Electron community grew bigger, more and more modules emerged that cover parts of the same operations done by ember-electron - and over time it became clear that this module should depend on other, more popular utility modules than to take care of all possible operations itself.

ember-electron v2 is almost a complete rewrite, using electron-forge to build and package your desktop applications. It allows ember-electron to focus on the Ember parts of this module, while the whole Electron community can work together to polish the creation of installers, the compilation of small packages, and the developer experience around native modules. Fore more info, check out this blog post.

Upgrading

If you are upgrading to version 2.x from 1.x, you will need to make some updates to your application. The best way to do this is to re-run the blueprint after upgrading ember-electron:

ember generate ember-electron

Configuration Upgrade

The biggest change is where your configuration lives - in the past, ember-electron managed your configuration, passing it on to internal tools that would take care of the actual creation of binaries.

Now, ember electron:package and ember electron:make use electron-forge to join forces with the greater Electron community. All configuration is now done using an electron-forge-config.js file inside your ember-electron folder. For details, check out the documentation.

Example Upgrade

To see an upgrade in action, check out how Ghost Desktop moved from ember-electron v1 to v2.

Changelog

• Bugfix: There used to issues with spaces in the project path - that should be gone :wink:

Changelog

• Added missing use strict for Node 4 😢

Changelog

• Upgraded to Ember Inspector 2
• Added support for the package electron (previously known as electron-prebuilt, which is still supported)
• Added a few tests
• Moved internal code to Standard JS