-
Notifications
You must be signed in to change notification settings - Fork 17.4k
fix: require .node files directly to detect incompatible native modules #21927
fix: require .node files directly to detect incompatible native modules #21927
Conversation
de30f5e
to
ec3f95e
Compare
ec3f95e
to
afaceb3
Compare
- This fixes the incompatible native module detection for the packages that require their .node files lazily - Speeds up the performance of detection by directly require .node files instead of requiring the package
afaceb3
to
ad2aaa8
Compare
@sadick254 @darangi This addresses one of the biggest headaches when Atom ships a new Electron. Traditionally, people had to manually go and rebuild the |
The support burden of each electron upgrade breaking current installs would be greatly alleviated by this PR, so thx at @aminya for these efforts. |
Thanks for the effort 🎉 @aminya |
You're welcome! |
Congrats on merge, if this is backported into 1.56beta we may have some joy out of this sooner rater than later. |
So apparently atom 1.56.0 doesn't include this fix see https://github.com/bus-stop/terminus/issues/219 could it be backported to next 1.56 release? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
White
T |
Description of the change
fix: require .node files directly to detect incompatible native modules
.node
files lazilyFixed Issues
This bug is one of the reasons that all the terminal packages break whenever an Electron upgrade happens or when you don't use
apm rebuild
An example of the packages that get fixed by this fix:
All the terminal packages that use
node-pty-prebuilt-multiarch
. Among them:There are many other issues. I need time to list all of them
Verification
The CI passes.
A test you can do:
npm rebuild
in its directory under.atom/packages/x-terminal