-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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.js: npm install takes c.7mins (Mac M1) #5159
Comments
Which version of NodeJS are you using? And on which architecture? |
$ node -v |
Adding a bit of colour: This issue seems to persist on other MacOS version with an M1 chip. MacOS 12.6.1 seems to have the same issue with M1. However the install time on an older MacOS machine is about 4s. |
We may be missing a binary distribution here |
I'm not sure if we're actually building NodeJS binaries for M1 at all? |
Very excited for this! Just tried to test the new prebuilt binaries. It still seemed to kick into building from source? I was using duckdb@0.5.2-dev1809.0. Relevant logs lines:
Full trace:
|
It looks like the master build failed yeah, I'll look into it today |
Not totally sure and might be off-track here, but I'm not sure that |
Ah see you have already PRed a fix, ignore |
I don't think the GitHub actions runners would have 3.11 by default yet, given it was only released a couple of weeks ago? It looks more like our version of node-gyp was pretty outdated, and I have a PR up (#5221) to fix that, which will hopefully solve these build issues |
It looks like the MacOS node builds are being skipped? I don't see either x64 or arm64 builds for darwin in the CDN at the moment? |
The OSX node builds on the master seem to be failing at the moment, we are looking into fixing it |
My PR above should fix that issue |
I'm not entirely sure if I have been finding the right action, but the builds still seem to be failing for Node v>15. When I try It seems to not be finding a
|
@archiewood yep, there ended up being another issue I had to fix in #5284, and the bindings are now uploaded - https://duckdb-node.s3.amazonaws.com/duckdb-v0.5.2-dev2131.0-node-v108-darwin-arm64.tar.gz If you could test this out before the release of 0.6, that would be very much appreciated |
It's working! Installs in 5s!
|
What happens?
When I try to install duckdb from npm, the process takes 7 minutes on a high spec computer.
We'd like to include DuckDB in our package, but this extends our current install time from around 30s to 7 minutes.
To Reproduce
you can replace the last line with
time npm install duckdb
Which gives you the install time:
real 6m44.266s
OS:
MacOS Ventura - Version 13.0 (22A380)
DuckDB Version:
[Any] / NPM version: 0.5.1
DuckDB Client:
Node.js API
Full Name:
Archie Wood
Affiliation:
Evidence
Have you tried this on the latest
master
branch?Have you tried the steps to reproduce? Do they include all relevant data and configuration? Does the issue you report still appear there?
The text was updated successfully, but these errors were encountered: