0

Trying to use the GridDB Node.js client on WSL (Ubuntu 22.04) with Node.js v18, but the installation fails.

Steps I followed:

sudo apt install -y nodejs build-essential  
node -v  # 18.20.8  
npm -v   # 10.8.2  
  
mkdir \~/gridDB-node  
cd \~/gridDB-node  
npm init -y  
npm install griddb-node-api  

Error:

npm error gyp: binding.gyp not found (cwd: /home/eagle04/gridDB-node/node_modules/griddb-node-api)  
npm error gyp ERR! configure error  
npm error gyp ERR! stack Error: gyp failed with exit code: 1  

I also tried Node.js v20, but the error persisted. I checked the GridDB repo (griddb_nosql), but the expected Node.js client folder (client/nodejs) does not exist in the repo.

Environment:

  • WSL Ubuntu 22.04
  • Node.js v18.20.8
  • NPM v10.8.2
  • GridDB server v5.8

I have seen related questions and found this similar one:

Issue installing griddb-node-api on Ubuntu with GridDB v5.5 and Node.js v20.11

However, in that case, they used GridDB v5.5, I am using v5.8. I’ve tried multiple Node.js versions (v18 and v20). The environment in the other post was likely Ubuntu, but I am on WSL. I also cloned the GitHub repo and the folder structure (client/nodejs, client/javascript, etc.) seems missing or changed.

What I want to know:

A working way to install the GridDB Node.js client on WSL. Guidance on whether a specific Node.js version is required, or if additional libraries/environment variables need to be set.

1 Answer 1

0

Used Node.js v16 (via nvm use 16), then ran npm install griddb-node-api — Node 18/20 failed because the package still depends on legacy native bindings.
After switching to v16, the install completes even with engine warnings, and the client works normally on WSL.

Sign up to request clarification or add additional context in comments.

Comments

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.