3.0.1

Make sure all <button> elements have a type="button" prop (see #8).

Thanks @anton-karlovskiy 🙏

3.0.0

This version removes the dynamic import strategy for wagmi, which was causing too many issues with Next.js.

As a result, the "addreth/no-wagmi" import path should be used by non-wagmi consumers:

import { Addreth } from "addreth/no-wagmi";

function App() {
  return (
    <main>
      <Addreth address="0x…" />
    </main>
  );
}

No changes are needed if your app was using wagmi already.

2.0.0

This version makes addreth compatible with Wagmi v2. No changes have been made to the addreth API itself compared to the previous version.

If your app was using Wagmi v1, you might want to follow the Wagmi v2 migration guide.

If your app was not using Wagmi, no action is needed.

1.2.0

This version enables both SSR¹ and RSC² compatibility by default.

Changes

• Both the component and its styles are now rendered by default (SSR¹).
• If <AddrethConfig /> is defined, the highest instance in the tree will handle the CSS rendering.
• A new export path has been provided for consumers to bundle the CSS themselves: "addreth/styles.css".
• The CSS injection can be disabled by setting the externalCss config option to true.
• A Next.js demo has been added.
• demo/ has been moved to examples/demo and migrated from Vite to Next.js.
• The documentation now includes a section about how to handle the styles.
• A building script has been created (build.js), replacing vite.config.ts.

1. Server Side Rendering. ↩ ↩²

2. React Server Components. ↩

1.1.0

This version adds a addreth/no-wagmi import path, which can help in certain situations where some bundlers (e.g. webpack / CRA / Next.js) attempt to statically resolve dynamic imports even when declared as optional dependencies, which is how addreth imports wagmi.

Importing Addreth from this path allows to solve these issues without requiring any extra configuration:

import { Addreth } from 'addreth/no-wagmi'

1.0.1

Disable SSR rendering

SSR rendering is disabled for now to avoid a FOUC. It will be added again in a future version, with a way to render the styles server side too.

Remove the focus ring on the popup

This is to fix an issue with some browsers (Safari iOS) that where displaying the popup focus ring even when interacting with touch. This shouldn’t be an issue for users, since the popup being opened is already an indicator that it has received the focus.

1.0.0

v1.0.0

1.0.0