Disconnect is not expose in Modal for Vanilla JS

[SerhiiKirik]

Describe the bug

There seems to be an error in the documentation in the Actions section for JavaScript (wagmi).
Link: DOC

Specifically in the Disconnect section:

modal.disconnect()

The issue is that modal does not have a disconnect method. Previously, disconnect was implemented using wagmi as follows:

import { disconnect } from '@wagmi/core';

I might be mistaken, and I would be happy to hear your response.
Thank you!

[SerhiiKirik]

Additional Comment:

I found the ConnectionController which contains a disconnect method. Therefore, we can do something like this:

await ConnectionController.disconnect();

Would this be the correct approach? Or is there a better way to handle the disconnect?

Also, the documentation lacks methods for tracking connection status, loading states, and the account. It would be helpful to add these.

[rtomas]

Error already know an reported . thanks
https://linear.app/reown/issue/APKT-1045/[bug]-disconnect-is-not-expose

[rtomas]

meanwhile you can use
modal.adapter?.connectionControllerClient?.disconnect()

[SerhiiKirik]

Thanks for the suggestion, @rtomas.

Here’s my current setup, maybe it will be useful to someone:

import { WagmiAdapter } from '@reown/appkit-adapter-wagmi';
import { createAppKit } from '@reown/appkit';
import { disconnect } from 'wagmi/actions';

....
const wagmiAdapter = new WagmiAdapter({
  projectId,
  networks,
});

const config = wagmiAdapter.wagmiConfig;

const modal = createAppKit({
  adapters: [wagmiAdapter],
  networks,
  metadata,
  projectId,
  features: { /* ... */ },
});
....

// Using wagmi’s built-in action:
await disconnect(config);

In a Svelte project, I can easily pass config around via context or a store, making it straightforward to trigger wagmiDisconnect from anywhere. However, I acknowledge that in a vanilla JS environment (or with frameworks that lack a context system), this approach might be less convenient.