Kiryl Valkovich

@ragaur-tibco I completely agree and don't argue with that.

@ragaur-tibco the current behavior is correct. See my comment here: https://github.com/apache/pulsar/issues/22527#issuecomment-2067133567

@ragaur-tibco I fixed your code. > When using non-persistent delivery, killing a Pulsar [broker](https://pulsar.apache.org/docs/next/reference-terminology/#broker) or **disconnecting a subscriber to a topic means that all in-transit messages are lost** on that...

@ragaur-tibco please check and let me know if it resolves the issue.

Interesting. My observation is that after we create a pattern consumer, for an **existing** non-persistent topic it doesn't "immediately" create the underlying subscription and consumers if there are no connected...

Here is the reason. Before adding a topic to the topics list, it checks that the topic `isActive()`, which checks for `!subscriptions.isEmpty() || hasLocalProducers();`. https://github.com/apache/pulsar/blob/21647a1fc69ff46e65b6eaa37dd6d435e9f8eaef/pulsar-broker/src/main/java/org/apache/pulsar/broker/namespace/NamespaceService.java#L1519 https://github.com/apache/pulsar/blob/21647a1fc69ff46e65b6eaa37dd6d435e9f8eaef/pulsar-broker/src/main/java/org/apache/pulsar/broker/service/nonpersistent/NonPersistentTopic.java#L993

As I see, initially there is should be a way to bundle modules and upload them to the browser page. Two days ago I implemented a script for my personal...

I updated README, added tests and published my lib for component testing to npmjs. Here is how React component test looks now: [link](https://github.com/visortelle/playwright-module-loader/blob/191ebf08fe8d10f50428b942e4514228ad07cd56/packages/test-react-ts/src/Button/Button.spec.ts)

In newer Next.js versions you can use built-in `transpilePackages` instead of `next-transpile-modules`: ```js const nextConfig = { transpilePackages: ["verbum"], }; module.exports = nextConfig; ```

Related: https://github.com/apache/pulsar/issues/22277#issuecomment-2002553745