Matt-Esch

@Raynos published builds are considered ready for production, correct? This is why npm doesn't install dev dependencies. So why would you want to include test files in your production builds?...

> When you install a dependency you want to see the source code of that library. Every dependency you install is one you effectively maintain. I want to see the...

Can confirm this is an issue, occurs when upgrading to pulsar > 2.6.0

I am attempting an upgrade to node 16 which means fast-forwarding the version of pulsar-client-node we are using from 1.2.0 to 1.4.1, which comes with the minimum pulsar version requirement...

Trying with v2.9.1 as per @Sraleik suggestion ``` [2021-12-24T13:39:43.164Z] 2021-12-24 13:39:42.898 INFO [139633915127552] ClientImpl:491 | Closing Pulsar client with 0 producers and 0 consumers [2021-12-24T13:39:43.164Z] 2021-12-24 13:39:42.898 INFO [139633681757952] ClientConnection:181...

Segfault issue tracked here: https://github.com/apache/pulsar-client-node/issues/191

I would have made it return a promise if the underlying c api had an async callback, but it doesn't.

It doesn't appear to be exposed in the c api which is used by this module https://github.com/apache/pulsar/blob/master/pulsar-client-cpp/lib/c/c_ClientConfiguration.cc - I would expect something like `pulsar_client_configuration_set_listener_name` I think we would do a...

I'm not sure what your full use case is but you might want to look at https://github.com/ayeo-flex-org/pulsar-flex - I haven't looked at it properly yet because it doesn't seem complete...

I suspect this overlaps with pulsar-client-cpp, I didn't find docs for that (I think it's provided in the header files) but there is an equivalent overlap with the java client...