Prevent the development viewer, started with gulp server, from breaking completely in Private Browsing mode

[Snuffleupagus]

Since attempting to access IndexedDB in Private Browsing mode in Firefox will throw an error, see https://bugzilla.mozilla.org/show_bug.cgi?id=781982, the development viewer fails to load.

[timvandermeij]

Would it perhaps be more readable to add a catch handler at the end of the promise chain here so you don't have to repeat the binding and call below? It looks like the call itself succeeded, but the storeCache call didn't, so having the catch handler here might prevent a duplicate call to babel.translate.call if I'm reading the code correctly (but do correct me if I'm wrong here).

[Snuffleupagus]

I purposely added the catch at the very end, since this way it'll catch errors occurring at any point in the entire Promise chain. (Note also that the Private Browsing related error is thrown already in loadCache, so your suggestion wouldn't have have worked here).

The point of this patch was thus to not only fix the problem at hand, but to ensure that the code will always attempt to fallback no matter what (future) errors are encountered.
To avoid trying to re-parse the code when specifically babel.translate fails, which I gather you wanted to avoid, the patch now tracks that particular case separately.

[timvandermeij]

Looks good now. Thank you!