Andrew Bulat

Done in https://github.com/ably/ably-js/pull/1676

I'm not sure about [this place](https://github.com/ably/ably-js/blob/d0e9fbe4797ebb8520286592ba7b5d82a139eb39/README.md?plain=1#L37) in README: ``` Ably-js has fallback mechanisms in order to be able to support older browsers; specifically it supports comet-based connections for browsers that...

> The other is that there are potential network conditions (firewalls or proxies are the ones I’ve seen talked about) that might block WebSocket connections (see [the documentation for WebSocketTransport](https://github.com/ably/ably-js/blob/ec95b59e8b50cb78cf783dfec960619b09c31203/modules.d.ts#L143))....

Removed fallback transport paragraph from this PR. Reworded it and added to another section in https://github.com/ably/ably-js/pull/1664. Also applied other changes.

Done in https://github.com/ably/ably-js/pull/1633

Done in https://github.com/ably/ably-js/pull/1656

Closing this as issue has been resolved, and ably-js v2 project version fully supports and can be built using Node 18+

Update: Use `serverComponentsExternalPackages` option in `next.config.js` (read more about the option [here](https://nextjs.org/docs/app/api-reference/next-config-js/serverComponentsExternalPackages)): ```javascript const nextConfig = { // ... experimental: { serverComponentsExternalPackages: ['ably'], }, }; ``` This fixes the warning...

Still failed after 100+ minutes unfortunately. Hope you will be able to load some logs, there are a lot. Quickly looked at previous PRs: seems like it started happening with...

in ably-js v2 in https://github.com/ably/ably-js/pull/1645 PR we decided to go with another approach: we removed `XHRStreaming` transport, and replaced upgrade mechanism with a websocket + base fallback transport mechanism whereby...