Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

bump to latest node-abi (Node 12/Electron 5) #102

Closed
wants to merge 1 commit into from
Closed

bump to latest node-abi (Node 12/Electron 5) #102

wants to merge 1 commit into from

Conversation

shiftkey
Copy link
Contributor

@shiftkey shiftkey commented Apr 25, 2019

electron/node-abi#62 adds support for detecting Electron 5 and Node 12

@vweevers
Copy link
Member

Is this change (and prebuild/prebuild#248) intended to prevent npm dedupe?

@shiftkey
Copy link
Contributor Author

If this is only needed in one of the projects, feel free to close the other. I wasn't aware that it wasn't unnecessary to update both here...

@shiftkey shiftkey changed the title bump to latest node-abi bump to latest node-abi (Node 12/Electron 5) Apr 25, 2019
@vweevers
Copy link
Member

Both use ^2 so the node-abi update should float in automatically, unless you have some other module that depends on node-abi with a more restrictive semver range?

@shiftkey
Copy link
Contributor Author

@vweevers let me test out a PR on a downstream project and see if I encounter an issue 🤘

@shiftkey
Copy link
Contributor Author

Looks like these PRs are unnecessary: atom/node-keytar#181

Thanks for the extra insight @vweevers and apologies for the noise!

@shiftkey shiftkey closed this Apr 25, 2019
@shiftkey shiftkey deleted the bump-for-node-12-electron-5 branch April 25, 2019 18:56
@vweevers
Copy link
Member

No worries! Glad it works out.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants