Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Failed to generate static pages in next.js after npm update to v3.12.0 #4

Open
ipnq opened this issue May 5, 2024 · 5 comments
Open

Comments

@ipnq
Copy link

ipnq commented May 5, 2024

Clone the repo, npm install, and then npm run build. Works.

clone-install-build

After that, npm update, and then npm run build. Fails.

update-build

@ipnq
Copy link
Author

ipnq commented May 5, 2024

The content of package.json after npm update.

package-json

@ipnq
Copy link
Author

ipnq commented May 5, 2024

ClientOnlyPropertyError: account is only available on the client is probably thrown by getAccount or watchAccount in useAccount.

@ipnq ipnq changed the title Failed to generate static pages after npm update Failed to generate static pages in next.js after npm update to v3.12.0 May 5, 2024
@jrhite
Copy link

jrhite commented May 16, 2024

I'm facing the same problem: ClientOnlyPropertyError: account is only available on the client. This seems to occur from page.tsx.

It's not clear to me why this is happening yet.

I'm new to nextjs and might be misunderstanding, but both page.tsx and useAccount.ts are tagged with use client so page.tsx shouldn't be getting pre-rendered on the server.

@moldy530
Copy link
Collaborator

this should be fixed now in the latest versions of the SDK. are y'all still running into that?

@AungThuSoe24
Copy link

Withdraw to Trust Wallet

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

No branches or pull requests

4 participants