-
-
Notifications
You must be signed in to change notification settings - Fork 0
feat: Support Node 24 #12
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 auto cancelled builds look due to #11. Not sure about the windows failure. I can try building on my windows machine if required! |
Ah yeah we should do a separate PR for #11 - let me open that up first after asking people about what we should do for libc. I don't think its a usage deal to constrain it (though honestly we should have gotten this done in v9) |
I think we also need to add an extra Node module abi level to each platform/arch so that pre-built binaries are loaded or bundled: sentry-javascript-profiling-node-binaries/src/index.ts Lines 51 to 62 in 7ac5dd2
The abi for v24 is 137: |
I thought these were still in the js repo - good catch! will fix up.
I thought these were related to C++ 20 but I think I'm wrong. If you could give it a try would be a big help! |
Node on Windows now builds with ClangCL so we need to also use that to build our native module. Bumping the |
Alright brought back the node-gyp upgrade I erased during the rebase |
I can reproduce the test failure on my local machine. Looks like Maybe this is a Node 24 bug 🤷♂️ |
If it works on Node 22 it def is a Node bug. We should try to reproduce it and open an issue with Node. @timfish could you help with that? |
When preparing for the tests we clear the yarn cache so that our local packed module gets used. Yarn v1 results in deprecation warnings in Node 24 which were polluting the output when we try and get the cache directory. |
ref getsentry/sentry-javascript#16058
resolves https://linear.app/getsentry/issue/FE-419