Upgrading to Node 10 early Nightly 75 (week of February 10th)

[Ed Lee]

dmose is planning to upgrade [1] from Node 8 to Node 10 in build and
test environments next week. This should fix / avoid a number of test
failures as various dependencies rely on newer features, e.g., for
await...of.

For some additional history, the build system already supports [1]
both Node 8 and Node 10, and the previous Node version change [2]
bumped the minor version to 8.17 back in December. Both seem to have
landed quite smoothly, although here we're changing the major version,
so please respond if you have concerns.

[0] https://bugzilla.mozilla.org/show_bug.cgi?id=1547823
[1] https://bugzilla.mozilla.org/show_bug.cgi?id=1611201
[2] https://bugzilla.mozilla.org/show_bug.cgi?id=1604295

Ed Lee

[Dan Mosedale]

As Ed Lee posted last week [1], we’re about to start requiring NodeJS version 10 for our builds for Firefox 75 and later [2].

In the next small number of days, I plan to land this change via Lando. After the patch from [2] merges to mozilla-central and you’ve updated your copy of m-c, in order for your builds to continue to work:

for downstream OS distributions:
* Ensure that a copy of NodeJS 10.* (or newer?) is the first copy in the PATH when the build is done.

for individual developers:
* Run `mach bootstrap` to update the copy of Node used by the build system.

If you have any questions or issues, feel free to ask here, ping me directly, or ask in #NodeJS on Slack.

I’ll post again after the changes have landed, so that folks have this info at hand when they need it.

[1] https://groups.google.com/d/msg/mozilla.dev.platform/YMzkiE29BK0/hcEgWMzOAwAJ
[2] https://bugzilla.mozilla.org/show_bug.cgi?id=1547823#c28

[Dan Mosedale]

Node 10 support has now merged to mozilla-central, see below for more details:

On Tue, 11 Feb 2020 at 12:49, Dan Mosedale <dmos...@mozilla.com> wrote:
> After the patch from [1] merges to mozilla-central and you’ve

> updated your copy of m-c, in order for your builds to continue to
> work:
>
> for downstream OS distributions:
> * Ensure that a copy of NodeJS 10.* (or newer?) is the first copy in
> the PATH when the build is done.
>
> for individual developers:
> * Run `mach bootstrap` to update the copy of Node used by the build system.
>
> If you have any questions or issues, feel free to ask here, ping me
> directly, or ask in #NodeJS on Slack.
>

> [1] https://bugzilla.mozilla.org/show_bug.cgi?id=1547823#c28