-
-
Notifications
You must be signed in to change notification settings - Fork 6
Rewrite in N-API for Electron 30+ compatibility #18
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
base: master
Are you sure you want to change the base?
Rewrite in N-API for Electron 30+ compatibility #18
Conversation
…by eliminating static references to constructors. Technique outright stolen from `tree-sitter/node-tree-sitter`.
…to something that can actually run on my system without complaining about random number generation.
(On my machine, a call to `pcre2_jit_compile` is causing test failures; not sure where the fault lies there. Commenting out the call fixed it, but is probably not a great idea as a permanent fix.)
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.
I'm willing to more or less rubber-stamp approve this on the basis it's already been in use on the ElectronNext / Pulsar Next branch of Pulsar for a while, right?
Ideally we would have a subject-matter expert sift through hundreds of C++ files and such, but... I don't see that happening. So I think we will use this and have the proof of the pudding be in the eating, so to speak.
In that sense, Looks Good To Me.
This is the upgrade to
superstring
we need for PulsarNext.Here's what this does:
superstring
so that it usesnode-addon-api
instead ofnan
, gaining context-awareness in the process.Now that we've published our existing
superstring
version (relied on for mainline Pulsar) to NPM as@pulsar-edit/superstring
version2.5.0
, we can land this tomaster
and bump the major version, publishing it as version3.0.0
.