Please try bumping the vendored npm to 4.0.2 as well.

@ilovezfs The upstream said node 7.2.0 is bundled with npm 3.10.9, shall we track upstream dependencies and keep npm as 3.10.9?

Quoted from @DomT4

We track what Node bundles upstream, unless what Node bundles upstream has security or major usability problems resolved in a newer release.

If we change the policy on node/npm, it shall also reflects on the formula comments. Personally I agree with Dom.

We track major/minor from upstream Node releases.
We will accept important npm patch releases when necessary.
Homebrew/legacy-homebrew#46098 (comment)

Edited: add personal opinion.

I quit, so it's pretty much up to ILZ, but I think both Homebrew and Node upstream find more stability in tracking the Node version as much as possible. I've seen less complaints directed at Node/npm at least since we adopted that policy.

Sure 3.10.9 will be fine, though it's annoying since we don't have a separate npm formula and current stable npm is 4.0.2 not 3.10.9.

@BrewTestBot test this please

@JLHwung thanks for your contribution to Homebrew!

@ilovezfs You're very welcome.

@ilovezfs We might not see a npm@4 bundled release on v7 according to nodejs/node#9284 (comment). It is marked as semver-major and 8.0.0 milestone.