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

[renovate]

This PR contains the following updates:

Package	Type	Update	Change	References
source-map	dependencies	minor	^0.6.1 -> ^0.7.0	source

---

Release Notes

mozilla/source-map

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.

---

Renovate configuration

📅 Schedule: At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻️ Rebasing: Whenever PR becomes conflicted, or if you modify the PR title to begin with "rebase!".

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Renovate Bot. View repository job log here.

[renovate]

PR has been edited

👷 This PR has received other commits, so Renovate will stop updating it to avoid conflicts or other problems. If you wish to abandon your changes and have Renovate start over then you can add the label rebase to this PR and Renovate will reset/recreate it.

[nolanmar511]

This version of source-map dropped support for Node 6 (cloud-debug-nodejs also uses source map, some discussion on why that module didn't switch to 0.7.0 here)

Closing this, since we want to support Node 6.

[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.

[JustinBeckwith]

Only a few months left 😄

[aalexand]

A few months till Node 6 EOL? Can we just drop Node 6 support then? @nolanmar511 perhaps take a look at whether we get any Node 6 traffic?

[aalexand]

Re-opening as I'd like to understand the Node.js 6 plan better. Not being able to update dependencies is not exciting.

[ofrobots]

This is the standard way the community operates. Around this time every year, we expect the ecosystem to start dropping support for imminently EoL versions of Node.

Here's some thoughts on the fact some modules drop support early that I have left in chat elsewhere, but copying here:

1. Semver still works. Continue using the previous major. That code still works. Dropping support in a semver major is fine as long as the maintainer is still willing to fix important bugs, security issues on the previous major.
2. There are only 2 months during which you care about this. Dominoes always start falling around this time.
3. Google Cloud modules shouldn't be the set of modules that surprise everyone when they are the first to drop support for Node 6. With the dominoes starting to fall now, by the time we drop support for Node 6, users and ecosystem would be much more ready for.