Update 3 dependencies from npm

[dependencies]

Overview

The following dependencies have been updated:

• babel-loader in /packages/generator/app/templates from "7.1.3" to "7.1.4"
• electron in /packages/generator/app/templates from "1.8.2" to "1.8.3"
• mocha in /packages/generator/app/templates from "5.0.1" to "5.0.2"

Details

Dependencies.io has updated babel-loader (a npm dependency in /packages/generator/app/templates) from "7.1.3" to "7.1.4".

7.1.4

🐛 Bug Fix

• Update code to read filename

---

Dependencies.io has updated electron (a npm dependency in /packages/generator/app/templates) from "1.8.2" to "1.8.3".

1.8.3

Bug Fixes

• Added Offscreen rendering improvements. #11729
• Fixed downloading from custom protocols using WebContents.downloadURL. #12100
• Fixed net::ERR_INSECURE_RESPONSE on https error. #12117
• [SECURITY] Fixed Integer overflow with PropertyArray issue. #12117

Linux

• [SECURITY] Disabled executable stack. #11955

Windows

• Fixed titlebar displaying for frameless and transparent windows. #11910
• Fixed desktopCapturer to capture the correct screen. #11677
• Fixed support for precision trackpad / mouse scrolling. #12117

---

Dependencies.io has updated mocha (a npm dependency in /packages/generator/app/templates) from "5.0.1" to "5.0.2".

5.0.2

This release fixes a class of tests which report as false positives. Certain tests will now break, though they would have previously been reported as passing. Details below. Sorry for the inconvenience!

🐛 Fixes

• #3226: Do not swallow errors that are thrown asynchronously from passing tests (boneskull). Example:

  it('should actually fail, sorry!', function (done) {
    // passing assertion
    assert(true === true);
  
    // test complete & is marked as passing
    done();
  
    // ...but something evil lurks within
    setTimeout(() => {
      throw new Error('chaos!');
    }, 100);
  });

  Previously to this version, Mocha would have silently swallowed the chaos! exception, and you wouldn't know. Well, now you know. Mocha cannot recover from this gracefully, so it will exit with a nonzero code.

  Maintainers of external reporters: If a test of this class is encountered, the Runner instance will emit the end event twice; you may need to change your reporter to use runner.once('end') intead of runner.on('end').

• #3093: Fix stack trace reformatting problem (outsideris)

:nut_and_bolt Other

• #3248: Update browser-stdout to v1.3.1 (honzajavorek)