-
Notifications
You must be signed in to change notification settings - Fork 263
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
node 18 support #647
Comments
Not sure what the exact issue is but we use |
Good to know. Let me see if I can learn something for your runs. Here are steps to reproduce in our case (
|
The error is due to the use of the The target flag is for "special cases" (see: https://github.com/mapbox/node-pre-gyp/blob/master/lib/util/versioning.js#L105) so I'd check to see if you really need those flags for the workflows. In any case - updating the json is part of the release process (see: https://github.com/mapbox/node-pre-gyp/blob/master/contributing.md). Not sure when this is planned for. |
Looking at this code, it means while waiting for the crosswalk file to catch up with node 18, I could achieve the same effect as
by running
on an x64 machine with node 18.0.0 active. Is my understanding correct? |
The Is there a path to getting #649 submitted, or should we plan to change how we build pre-built binaries if we'd like to add support for Node 18? |
@nolanmar511 you are aware of #657 right? |
I am having issues with Node 18 as well. Getting errors when installing |
For support of Node.js > v17, see the workaround: |
Are there any plans and/or timeline to support node 18? Thank you!
The text was updated successfully, but these errors were encountered: