-
-
Notifications
You must be signed in to change notification settings - Fork 512
Nan::SetAccessor()
deprecation warning with V8 10.1 and nan 2.15.0
#936
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
Comments
Nan::SetAccessor()
warning with V8 10.1 and nan 2.15.0Nan::SetAccessor()
deprecation warning with V8 10.1 and nan 2.15.0
@mscdex Can you confirm that this is resolved in the main branch? |
There is now a similar problem with Electron >= 20 |
Electron29 / NodeJS 20 breakage:
|
Looks like this was fixed in 2.17.0. |
I am getting a fatal compiler error with NAN My current workaround is to comment out all the
|
PS: a while back somebody ended-up forking NAN to remove breaking function signatures: electron/electron#35193 (comment) I personally use the official NAN NPM package and I |
I can confirm this issue persists. It's not just a warning. It throws an error now, as @danielweck mentioned.
Run By the way: I took more than one day to figure out what is happening here. I am not pretty familar with all those dependency stuff. |
I can confirm, I have the same issue. Nan is not compatible with Electron 29 / Node 20. As a temporary workaround you can use following in your package.json:
Please note I just commented all the See #966 |
Could this be a breaking change in node-gyp's header file? In Electron 28.2.2's v8-template.h (you can find it at your_user_directory/.electron-gyp/Library/Caches/node-gyp/28.2.2/include/node)
In Electron 29.1.0's v8-template.h
It seems PropertyAttribute and AccessControl are not compatible given the error details:
Probably nan needs to adjust its signature to match the new signature. |
This is still happening and atm it is impossible to rebuild native addons on Electron v28 Edit: I was able to fix it by applying this patch: #982 |
The text was updated successfully, but these errors were encountered: