Enable ASAR when building

[sindresorhus]

Right now, Kap, is not built with ASAR. ASAR can considerably improve the startup time of the app by putting all JS files into one file. @matheuss disabled it initally as it caused some problems with Aperture.js. ASAR should in theory handle child processes, but if we can't work it out, we can use the electron-builder asarUnpack option.

This should happen after Kap 1.0.

---

Alternatively, we could switch from execa (it uses .spawn underneath) to .execFile: http://electron.atom.io/docs/tutorial/application-packaging/#executing-binaries-inside-asar-archive

[sindresorhus]

I look into this today and opened an Electron issue about it: electron/electron#9459

We also need to set this in the "build" config of package.json:

"asarUnpack": [
   "vendor/ffmpeg"
]

Unless electron-builder can detect it somehow. I'll test when it's fixed in Electron.

[albinekb]

@sindresorhus should we just enable asar and asarUnpack the aperture (and ffmpeg) binary? Wouldn't that work 🤔

[sindresorhus]

@albinekb I've tried before but got stuck on a problem. Maybe you could give it a try too?

Here's a start: bb5749e

I can't seem to find the Aperture binary.