fix(deps): update dependency source-map to ^0.7.0

[renovate]

This Pull Request updates dependency source-map from ^0.6.1 to ^0.7.0

Release Notes

v0.7.3

Compare Source

• Fix a bug where nested uses of SourceMapConsumer could result in a
  TypeError. #​338
  #​330
  #​319

---

v0.7.2

Compare Source

• Another 3x speed up in SourceMapConsumer. Read about it here:
  http://fitzgeraldnick.com/2018/02/26/speed-without-wizardry.html

---

v0.7.1

Compare Source

• Updated TypeScript typings. #​321

---

v0.7.0

Compare Source

• SourceMapConsumer now uses WebAssembly, and is much faster! Read about
  it here:
  https://hacks.mozilla.org/2018/01/oxidizing-source-maps-with-rust-and-webassembly/

• Breaking change: new SourceMapConsumer now returns a Promise object
  that resolves to the newly constructed SourceMapConsumer instance, rather
  than returning the new instance immediately.

• Breaking change: when you're done using a SourceMapConsumer instance,
  you must call SourceMapConsumer.prototype.destroy on it. After calling
  destroy, you must not use the instance again.

• Breaking change: SourceMapConsumer used to be able to handle lines,
  columns numbers and source and name indices up to 2^53 - 1 (aka
  Number.MAX_SAFE_INTEGER). It can now only handle them up to 2^32 - 1.

• Breaking change: The source-map library now uses modern ECMAScript-isms:
  let, arrow functions, async, etc. Use Babel to compile it down to
  ECMAScript 5 if you need to support older JavaScript environments.

• Breaking change: Drop support for Node < 8. If you want to support older
  versions of node, please use v0.6 or below.

---

---

This PR has been generated by Renovate Bot.

[ofrobots]

This fails on travis, but I cannot reproduce the failure locally. Nor does it make sense why a change to this module would cause the failure seen on Travis 🤨.

[JustinBeckwith]

This may be a dramatic measure, but what do you think about moving this to CircleCI? At least then we could rule out Travis as the problem 😆

[JustinBeckwith]

FWIW I can reproduce this locally. I just checked out the branch, deleted node_modules and build, ran npm install, and npm test. The test failures do not happen on master.

[ofrobots]

After cleaning out local node_modules, I can reproduce the failure too. Intrestingly, running an individual failing test makes it pass.

Current smallish repo: npx mocha -r source-map-support/register build/test/test-debuglet.js -g "projectId".

[ofrobots]

Shoulda have read the release notes 😂. Commit coming up.

[renovate]

PR has been edited

As this PR has been edited, Renovate will stop updating it in order to not cause any conflicts or other problems. If you wish to abandon your edits and have Renovate recreate this PR then you should rename this PR and then close it.

[ofrobots]

Reading the release notes further:

Breaking change: Drop support for Node < 8. If you want to support older
versions of node, please use v0.6 or below.

We still need to support Node 6. I'm going to close this.

[renovate]

Renovate Ignore Notification

As this PR has been closed unmerged, Renovate will now ignore this update (^0.7.0). You will still receive a PR once a newer version is released, so if you wish to permanently ignore this dependency, please add it to the ignoreDeps array of your renovate config.

If this PR was closed by mistake or you changed your mind, you can simply rename this PR and you will soon get a fresh replacement PR opened.