Node upgrade landing on autoland
Mark Banner
I have just landed an upgrade to Node onto autoland. You may need to update Node via `./mach bootstrap`, but for most of you this will be automatic, or have already happened.
We are upgrading the installed Node version from v12 to v16. This
version is used for most builds.
We are upgrading the minimum Node version requirement from v10 to
v12. This version is used for "base-toolchain"
builds.
More details are in the bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1762571
What if I _do_ run into build breakage when I upgrade Node?
One possible cause is this: a small number of developers (you
probably already all know who you are) both:
- Develop/maintain code that has its own node_modules sub-directory
- (ie not the top-level node_modules in mozilla-central)
- Have platform-native-binaries in that local node_modules
- (like browser/components/newtab/node_modules does)
In that case, you may need to remove that local `node_modules`,
and re-execute `mach npm install` to force the binaries to be
recompiled for the new Node version, like so:
rm -fr
browser/components/newtab/node_modules
mach npm install --prefix=browser/components/newtab
If you have any questions, concerns or issues, feel free to ask
here, in #NodeJS on Slack, or in #build on Element.
Mark
You received this message because you are subscribed to the Google Groups "firef...@mozilla.org" group.
To unsubscribe from this group and stop receiving emails from it, send an email to firefox-dev...@mozilla.org.
To view this discussion on the web visit https://groups.google.com/a/mozilla.org/d/msgid/firefox-dev/3416b05c-6067-5b72-47f9-7a55fd4015c5%40mozilla.com.