-
Notifications
You must be signed in to change notification settings - Fork 55
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
Cut new release with new ABI 69 #107
Comments
Issue Label Bot is not confident enough to auto-label this issue. See dashboard for more details. |
Although adding those versions to the |
@Arcanemagus, yes, you are not wrong. However, as additional context, it should resolve this bug: rubyide/vscode-ruby#486 (Happened before and I believe the maintainer is wanting to switch to WASM to avoid in the future.) |
Moving to #108 |
Just for color here @Arcanemagus: This is used in an electron extension in VSCode. The way VSCode handles extensions + the fact it is being consumed via an extension and not in a traditional NPM workflow makes building a new binary on demand more problematic (like lack of build tooling being available). My long term solve will be to switch over to using the WASM build of |
My version of Node has
can you recompile and release for 67 (and preemptively for 69)?
The text was updated successfully, but these errors were encountered: