Failed to build aerospike-client-c dependency
See original GitHub issueI am running into an error on my new computer when trying to run npm i on a project of mine that utilizes aerospike. I have installed pre-reqs for windows and set execution policy.
Versions: OS: Windows 10 64bit Node: 12.18.3 Aerospike: 3.16.1 NPM: 6.14.17
Output of error log: https://pastebin.com/6JLLjtsS
Issue Analytics
- State:
- Created 3 years ago
- Comments:5 (2 by maintainers)
Top Results From Across the Web
Error while installing in Windows · Issue #318 - GitHub
D:\Temp\ttt\node_modules\aerospike\scripts\build-c-client.ps1 : Failed to build aerospike-client-c dependency At line:1 char:1 + .
Read more >Build Error within aerospike-client-c-src-4.6.8
I'm trying to put the Aerospike Node.js client into an alpine Docker container. This needs some building the client-c-src.
Read more >Aerospike NPM | npm.io
Aerospike Node.js Client travis codecov npm downloads ... The build step will resolve the Aerospike C client dependency as described in C Client...
Read more >npm aerospike install issue - node.js - Stack Overflow
You can circumvent this problem by installing the C client in your machine and using the locally installed version to install aerospike ......
Read more >aerospike - npm
Aerospike Client Library. Latest version: 5.0.3, last published: 3 months ago. Start using aerospike in your project by running `npm i ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

Just updating to let anyone who may face this issue that it was indeed caused by the space in the username. I am able to install now with no space in username.
Thanks for the follow-up. I’ll close this issue for now, since it seems there is nothing we can do to fix this issue in the client installation scripts. But feel free to reopen the issue if there’s something I missed and that needs to be addressed.