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

[Bug?]:Error: Hydration Mismatch. Unable to find DOM nodes for hydration key: 0-0-0-0-0-0-0-0-1-0-0-0-1-0-0-0-0-0-1 #1473

Closed
2 tasks done
KunalSin9h opened this issue May 10, 2024 · 12 comments
Labels
bug Something isn't working

Comments

@KunalSin9h
Copy link

Duplicates

  • I have searched the existing issues

Latest version

  • I have tested the latest version

Current behavior 😯

Whenever i create a route with folders like routes/admin/dash.tsx this error happens when accessing that page.

Expected behavior 🤔

The page should render as normal.

Steps to reproduce 🕹

Steps:

  1. Create a route with folder

Context 🔦

No response

Your environment 🌎

No response

@KunalSin9h KunalSin9h added the bug Something isn't working label May 10, 2024
@KunalSin9h
Copy link
Author

image

@ryansolid
Copy link
Member

Does this happen after restarting the dev server. There is a known bug: #1286

@KunalSin9h
Copy link
Author

@ryansolid tested also with v1, when adding new route this error happens, but after shutting down vite and restart is working.

@FlatMapIO
Copy link

Based on my experience, encountering such issues is usually due to:

  • Adding/removing routes
  • A component that might be a client-only component not being wrapped with the clientOnly wrapper, which might require an elimination process to identify it 😭

Generally, restarting the development server resolves the issue. Sometimes, it's also necessary to delete the node_modules/.vinxi directory.

@KunalSin9h
Copy link
Author

working only when removing node_modules/.vinxi package.

@ghost
Copy link

ghost commented May 27, 2024

same issue happened to me when creating routes/product/[id].tsx, even after restarting the dev server, the problem persists, but deleting node_modules/.vinxi resolves it.

@anurag-roy
Copy link

A hard reload on the browser (Ctrl+Shift+R) seems to solve it for me

@klequis
Copy link

klequis commented Jun 1, 2024

I have had this problem as well. The problem goes away when I disable the browser cache.

@juanUrdaneta
Copy link

juanUrdaneta commented Jun 7, 2024

removing node_modules/.vinxi or doing a hard reload cmd + shift + R solves the issue as well.

@cs-clarence
Copy link

same problem

@Suman196pokhrel
Copy link

Suman196pokhrel commented Jul 13, 2024

I am facing the same issue.

Temporary Solution:
Rather than deleting the .vixin from node_modules, disable caching from the developer tools -> Network tab. But it is pretty offputting when trying out a new framework.

@mdynnl
Copy link

mdynnl commented Jul 16, 2024

This can be closed after vixi minor version is released.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

9 participants