Skip to content

[pull] master from atom:master#74

Merged
pull[bot] merged 7 commits intosmilers:masterfrom
atom:master
Sep 20, 2021
Merged

[pull] master from atom:master#74
pull[bot] merged 7 commits intosmilers:masterfrom
atom:master

Conversation

@pull
Copy link

@pull pull bot commented Sep 20, 2021

See Commits and Changes for more details.


Created by pull[bot]

Can you help keep this open source service alive? 💖 Please sponsor : )

DeeDeeG and others added 7 commits September 13, 2021 21:07
We don't actually support Node older than 10 for successfully
bootstrapping an Atom build, but we should support older Node in the
system requirements checker script so that we can print useful errors,
like ones to tell the user their system's copy of Node is too old!

(It was me that introduced this Node 10.0.0 or above-only syntax
about a year ago... My mistake. It's as good a time as any to fix it!)
The periods for return types are inconsistent
"Node 10.12 or newer" has been a hard requirement since this PR:
#20879,
due to newer versions of electron-chromedriver and electron-mksnapshot
relying on extract-zip@2 as an indirect dependency.

(extract-zip@2 requires Node 10.12 or newer for its recursive mkdir.
Using extract-zip@2 with Node older than 10.12 results in errors.

That leads to a lack of electron-vendored
chromedriver or mksnapshot binaries where they're supposed to be.
Which in turn causes startup blob creation (via mksnapshot) to fail
toward the end of the Atom build scripts.)
bootstrap: Update Node requirement to 10.12+ in system requirement checker
…cker-node

bootstrap: Use legacy-compatible `catch` syntax (support older Node)
Remove deprecated code strings
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants