-
Notifications
You must be signed in to change notification settings - Fork 512
Fix version guard for ScriptOrigin
constructors
#989
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
Conversation
The current version guard for Isolate-less ScriptOrigin constructors checks both V8_MAJOR_VERSION > 11 and V8_MINOR_VERSION > 7. Newer V8s with a minor version not greater than 7, such as V8 v13.2.152.36 of Electron v34.2.0, still fall back to deprecated constructors removed since V8 v12.7.23 and fail to compile. Fix the preprocessor logic to properly detect V8 v11.7+.
Also, where did the v11.7 cutoff come from? |
The cutoff looks like a simple oversight. Thank you for fixing it. I will release a new version. |
It fails testing on Node 21 https://github.com/nodejs/nan/actions/runs/13538593063/job/37854108934?pr=989 |
21.7.3 has
|
Isolate-taking constructors were deprecate_soon'd in 2282b3d (12.1.140), deprecated in 0b52081 (12.6.175) and removed in 7cd2b0c (12.7.23). Corrected the version cutoff to 12.6.175 when the constructors in question were officially deprecated.
Corrected it to 12.6.175. Tested locally on Node 21 and all CI tests are passing as well. |
LGTM. I will get this out now. |
The current version guard for
Isolate
-less ScriptOrigin constructors checks bothV8_MAJOR_VERSION > 11
andV8_MINOR_VERSION > 7
. Newer V8s with a minor version not greater than 7, such as V8 v13.2.152.36 of Electron v34.2.0, still fall back to deprecated constructors removed since V8 v12.7.23 and fail to compile.Fix the preprocessor logic to properly detect V8 v11.7+.