Node and Browser versions of the `iot.AwsIotMqttConnectionConfigBuilder` do not provide the same API about aws-crt-nodejs HOT 8 CLOSED

For the intellisense issue, one solution is to explicitly import the specific library, in case I know that the code is for the browser or node respectively. Eg:

import { mqtt, iot } from "aws-crt/dist.browser/browser";

provides the right intellisense suggestions.

from aws-crt-nodejs.

As the browser and the node library have different features/functionalities, it is impossible to make them the same. There will always be some gap between the two APIs. However, we will try our best to unify them.
We've added the task on our road map. Thank you to bring this up!

from aws-crt-nodejs.

Thank you for sharing the intellisense solution!

from aws-crt-nodejs.

Hi @massi-ang,
after reviewing the difference in the APIs. We figured there some missing API we can fix. As an example: new_websocket_builder was missing in browser library. Other than that, there is little we can do because of the difference behind browser and node connection.
Is there any specific interface you would like us to improve?
Let me know if you have any suggestions.

from aws-crt-nodejs.

Hi,
I understand that the native implementation supports some configurations that are not available in the browser implementation, but the common subset of the methods between the two implementations should have the same signatures.

from aws-crt-nodejs.

The main difference between Node library and Browser library is the way they setup the websocket. To satisfied the async design on browser side, we have to change how the websocket setup, which causes the API difference.

Besides the websocket configurations, there is also some mismatch on parameters. For example, with_socket_options will take different SocketOptions as they are implemented differently on Node side and browser side. We do not have a way to unify them for now.

As for now, we will add new_builder_for_websocket for API compatibility with the native version.
Here is a table of the current mismatched APIs:

from aws-crt-nodejs.

Thank you.

from aws-crt-nodejs.

Closing issue here. Feel free to reopen it if you have further consideration related to the API.

from aws-crt-nodejs.