Skip to content

docs: add Base Account compatibility guide#1411

Open
dieutx wants to merge 1 commit into
base:masterfrom
dieutx:docs/base-account-compatibility-guide
Open

docs: add Base Account compatibility guide#1411
dieutx wants to merge 1 commit into
base:masterfrom
dieutx:docs/base-account-compatibility-guide

Conversation

@dieutx
Copy link
Copy Markdown

@dieutx dieutx commented May 11, 2026

Summary

  • add a new Base Account compatibility guide that explains which docs and dependency stacks go together
  • add a direct link to that guide from the Base Account overview page

Problem

Issue #1404 asks for clearer compatibility guidance between major components such as the SDK, wallet-framework integrations, and supporting packages.

Today the docs explain each integration in isolation, but there is no central page that helps builders answer questions like:

  • should I use the plain HTML quickstart or the React / Next.js quickstart?
  • when do I need Wagmi + Viem + React Query together?
  • why does the Privy setup require an @base-org/account override?

Solution

This PR adds a new Compatibility guide page under the Base Account overview section and keeps the guidance grounded in the existing docs:

  • maps app architectures to the right starting guide
  • summarizes the package families used by each integration pattern
  • calls out the Next.js ssr: true requirement for Wagmi-based setups
  • calls out the Privy @base-org/account override / resolution requirement

Notes

The guide intentionally stays scoped to combinations already documented in this repo instead of inventing a broader support matrix.

Closes #1404

@cb-heimdall
Copy link
Copy Markdown
Collaborator

🟡 Heimdall Review Status

Requirement Status More Info
Reviews 🟡 0/2
Denominator calculation
Show calculation
1 if user is bot 0
1 if user is external 0
2 if repo is sensitive 0
From .codeflow.yml 1
Additional review requirements
Show calculation
Max 0
0
From CODEOWNERS 0
Global minimum 0
Max 1
1
1 if commit is unverified 1
Sum 2

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Clarify version compatibility between components

2 participants