Hi Baodi, I'd suggest first getting the changes for pre-compiled binaries to be merged, tested, and expanded to support more combinations of os/cpu/nodejs. eg: mac-arm64, linux-alpine, etc..
Regarding the version number, 3.0 was adopted for C++ and Python because we had to detach from the main Pulsar release and we needed this number to be > 2.11 to avoid going back in time. pulsar-client-node already has its own release versioning and I don't think we necessarily need to match the C++ client version, especially since we're working on getting the user to not need to know which c++ client is actually underneath. -- Matteo Merli <matteo.me...@gmail.com> On Fri, Oct 14, 2022 at 1:47 AM Baodi Shi <wudixiaolong...@icloud.com.invalid> wrote: > > Hi, We're releasing C++ and python 3.0.0 client, Node.js Client is also built > on C++, and I'd like to discuss whether to start working on Node.js Client > 3.0.0 as well. > > In Node.js 3.0.0 Client, I mainly want to make the following changes: > > 1. Users no longer need to install the C++ client when using the Node Js > client. This PR has already done some work: > https://github.com/apache/pulsar-client-node/pull/235 > 2. Let the node client build based on C++ 3.0.0. > > > Maybe it can be iterated according to the current version number, but I think > the three clients of Python, Node, and C++ are closely related. Therefore, it > will be more unified for the Node.js client to start with 3.0.0. > > Thanks > Baodi Shi
