-
-
Notifications
You must be signed in to change notification settings - Fork 815
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
Add support for Node 13 (node-v79-linux-x64) #1246
Comments
Please wait for #1248, we need to release a new version if you want to use prebuilt v13.
We will be providing compiled binaries for v13 in the next release. |
I'd like to +1 this! |
Please re-install sqlite3 to v4.1.1, they have been added, thanks. |
Just tested it with bitbucket pipelines, it works as expected, thank you for the follow-up! |
Works for me too! |
As a developer, I want to be able to support latest Node.js version (13.x) in order to use the latest engine features and to make sure all internal CLI users will be able to use my applications.
I work on internal business projects that are being used by developers, mostly through local CLI and distant Web interfaces. Some of them are on Node 12, some upgraded on 13 (we kept our servers on Node 12). Currently, the CI fails tests when on Node 13, not able to find the proper binding, which is supposed to be
node-v79-linux-x64
. However, the binding I get when on Bitbucket pipeline imagenode:latest
isnode-v72-linux-x64
. All my CI tests are failing on the latest Node.js version because of this, but are successful on Node 12, on which binding resolves tonode-v72-linux-x64
. I use your package throughknex
.Would it be something that you can fix in the next few weeks?
The text was updated successfully, but these errors were encountered: