osbornm commented on issue #122: URL: https://github.com/apache/pulsar-client-node/issues/122#issuecomment-924998580
@gaoran10 I can and have got the node client to build local after pulling down the c++ library building and setting the ENV. This is tangential to the problem I have though. I want to be able to go into my own node project, say an API I am building, install the node client via npm ([`npm install pulsar-client`](https://pulsar.apache.org/docs/en/next/client-libraries-node/#installation-using-npm)), make some changes to the API to produce messages, commit to my project, and then be able to have another developer pull down that project on a windows machine and simply run `npm install` to restore packages and not have to jump through a bunch of hoops (cloning repositories and building c++ projects). IMHO, the solution is to have this project publish the c++ binaries. You can see from the following output that npm/node-gyp is trying to fetch the prebuilt. ``` node-pre-gyp WARN Using request for node-pre-gyp https download node-pre-gyp WARN Tried to download(404): https://pulsar.apache.org/docs/en/client-libraries-cpp/libpulsar-v1.3.1-node-v83-win32-x64.tar.gz node-pre-gyp WARN Pre-built binaries not found for pulsar-client@1.3.1 and node@14.17.3 (node-v83 ABI, unknown) (falling back to source compile with node-gyp) ``` -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@pulsar.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
