Browserified version

[ansd]

Hello,

thank you very much for developing this client library!

I wonder how I can create a browserified version of this client.

In rhea itself, I can run

npm install
make browserify

which will create a file rhea.js which I can then use from within my browser to communicate to RabbitMQ over AMQP 1.0 over WebSocket as explained in https://www.rabbitmq.com/blog/2025/04/16/amqp-websocket#example

How can I create such a browserified version of abbitmq-amqp-js-client?

[l4mby]

Hello @ansd thank you for opening the issue, right now we only offer the client as an esm or commonjs package and we haven't yet integrated the websocket connection. We can open an issue for this request, also feel free to open a PR.
Thanks again

[apietroni51]

Since this PR: #63 (comment)
we grant support for use with websockets, so we can close this question.

[ansd]

Yes, this library supports now AMQP over WebSocket, thank you!
However, in #63 (comment) the client runs in a JavaScript runtime environment outside the web browser.

This issue is about running AMQP over WebSocket where the client runs inside a browser.

[l4mby]

Hi @ansd, i pushed some changes in the branch wip/browserified, where the build command generates an umd bundle for the browser, could you please test this with the websocket_example.html on the browser? If the example goes ok we will open the pr.
To run the example, like you did previously, simply clone or pull the repo, switch into the branch, run

npm install
npm run build
cd examples
npm i

and then run the websocket_example.html on the browser, i used the live server extension on vscode.
Thank you again in advance.

[ansd]

Thank you very much @l4mby.

When I open websocket_example.html, RabbitMQ logs the following:

2025-07-29 12:03:12.299528+02:00 [info] <0.1043.0> accepting Web AMQP connection 127.0.0.1:50705 -> 127.0.0.1:15678
2025-07-29 12:03:12.308658+02:00 [debug] <0.1043.0> User 'guest' authenticated successfully by backend rabbit_auth_backend_internal
2025-07-29 12:03:12.309182+02:00 [info] <0.1043.0> Connection from AMQP 1.0 container '199adf84-bd08-194c-9aaf-c62cc10edba4': user 'guest' authenticated using SASL mechanism PLAIN and granted access to vhost '/'
2025-07-29 12:03:12.309270+02:00 [debug] <0.1043.0> AMQP 1.0 connection.open frame: hostname = undefined, extracted vhost = /, idle-time-out = undefined
2025-07-29 12:03:12.310599+02:00 [debug] <0.1043.0> AMQP 1.0 created session process <0.1049.0> for channel number 0
2025-07-29 12:03:12.313395+02:00 [warning] <0.1049.0> Closing session for connection <0.1043.0>: {'v1_0.error',
2025-07-29 12:03:12.313395+02:00 [warning] <0.1049.0>                                             {symbol,
2025-07-29 12:03:12.313395+02:00 [warning] <0.1049.0>                                              <<"amqp:precondition-failed">>},
2025-07-29 12:03:12.313395+02:00 [warning] <0.1049.0>                                             {utf8,
2025-07-29 12:03:12.313395+02:00 [warning] <0.1049.0>                                              <<"insufficient credit (0) for management link from RabbitMQ to client">>},
2025-07-29 12:03:12.313395+02:00 [warning] <0.1049.0>                                             undefined}
2025-07-29 12:03:12.313491+02:00 [debug] <0.1043.0> AMQP 1.0 closed session process <0.1049.0> with channel number 0

It seems the connection succeeds, which is great news. But then, the client doesn't seem to grant (sufficient) link credit to RabbitMQ on the management link in order to receive the HTTP over AMQP reply from RabbitMQ?

[ansd]

After adding some debug logs to RabbitMQ, I can see that the client first sends the transfer frame to RabbiMQ on one management link before granting 1000 link credit on the other management link.
This order should be reversed: The client should first grant link credit before sending an HTTP over AMQP transfer to RabbitMQ.

The order should be as for example done in the RabbitMQ AMQP 1.0 Erlang client in https://github.com/rabbitmq/rabbitmq-server/blob/5c26be69857eb9310d44062fc47779e015c417c1/deps/rabbitmq_amqp_client/src/rabbitmq_amqp_client.erl#L407-L408

[l4mby]

Thank you @ansd, for credit management we actually let rhea handle it, using its defaults. We simply call the rhea api open_receiver and open_sender to create the management. What we noted is that if we change the script part to use .then instead of async/await and remove type=module from the tag, something seems to work. But we are still investigating, we will update you soon.

[l4mby]

Hello @ansd when you have time, can you try to run the websocket_example.html example from the branch 56-browserified-version? Simply build using npm run build:browser after npm i and then you can try, if it works. Thank you in advance

[ansd]

Hi @l4mby, I face the same issue as above.

--- a/examples/websocket_example.html
+++ b/examples/websocket_example.html
@@ -16,9 +16,9 @@
       console.log("Creating the environment through a websocket...")
       const environment = RabbitmqAmqpClient.createEnvironment({
         host: "localhost",
-        port: 3000,
-        username: "rabbit",
-        password: "rabbit",
+        port: 15678,
+        username: "guest",
+        password: "guest",
         webSocket: { implementation: WebSocket },
       })

When I open websocket_example.html, RabbitMQ logs output:

2025-09-25 15:36:32.730512+02:00 [info] <0.585.0> accepting Web AMQP connection 127.0.0.1:64773 -> 127.0.0.1:15678
2025-09-25 15:36:32.732456+02:00 [debug] <0.585.0> User 'guest' authenticated successfully by backend rabbit_auth_backend_internal
2025-09-25 15:36:32.732884+02:00 [info] <0.585.0> Connection from AMQP 1.0 container '2467db51-5932-1649-a22f-45e323e9fe67': user 'guest' authenticated using SASL mechanism PLAIN and granted access to vhost '/'
2025-09-25 15:36:32.732980+02:00 [debug] <0.585.0> AMQP 1.0 connection.open frame: hostname = undefined, extracted vhost = /, idle-time-out = undefined
2025-09-25 15:36:32.734332+02:00 [debug] <0.585.0> AMQP 1.0 created session process <0.591.0> for channel number 0
2025-09-25 15:36:32.735883+02:00 [warning] <0.591.0> Closing session for connection <0.585.0>: {'v1_0.error',
2025-09-25 15:36:32.735883+02:00 [warning] <0.591.0>                                            {symbol,
2025-09-25 15:36:32.735883+02:00 [warning] <0.591.0>                                             <<"amqp:precondition-failed">>},
2025-09-25 15:36:32.735883+02:00 [warning] <0.591.0>                                            {utf8,
2025-09-25 15:36:32.735883+02:00 [warning] <0.591.0>                                             <<"insufficient credit (0) for management link from RabbitMQ to client">>},
2025-09-25 15:36:32.735883+02:00 [warning] <0.591.0>                                            undefined}
2025-09-25 15:36:32.735993+02:00 [debug] <0.585.0> AMQP 1.0 closed session process <0.591.0> with channel number 0

[l4mby]

Hello @ansd thank you for the answer. Is there a way we can have access to the tanzu image for direct testing? Or maybe open like a port where we can connect. Because i tried locally in the browser using websocketify as proxy which connects to my docker rabbitmq image and it works.
Thanks again

[l4mby]

Hello @ansd thanks to the online tanzu env and @Gsantomaggio, we added a little wait time after the management links creation. If you have time could you retry? (Now it should work, fingers crossed)
Thank you in advance.