-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
Not easy to debug error only in dev mode #1395
Comments
Finally got a reproduction 😅. (This is same as #1374 BTW. ) |
Fixed in vitejs/vite#10207 |
@brc-dd I am still having the same error,
"vite": "^3.1.2",
"vitepress": "^1.0.0-alpha.16",
"vue": "^3.2.39" is there something missing, or wrong I am doing? |
@yaman3bd it has not been published yet.. |
@brc-dd I'm still getting the same error. |
I haven't released a new version yet. |
Weird, not working on alpha-18 too :/ |
Ah, this will be fixed in next version of @vitejs/plugin-vue |
Describe the bug
The build and serve commands works but the dev doesn't.
Reproduction
clone the repo
The error thrown is misleading in my opinion..
Uncaught TypeError: Cannot read properties of undefined (reading 'accept')
at VPSkipLink.vue:37:3
Expected behavior
the error should point to the correct file?
I'm sure is not a problem in VPSkipLink file.
Is hard to debug without knowledge of vitepress internal logic
System Info
Additional context
I'm convincing the mermaidjs team to update their documentation to use vitepress 😁.
I created a repo from scratch first and it works without problem but in the mermaid repo this error may be a combination of the setting done in packaeg.json and tsconfig but!
I think we really want anyone to be able to use vitepress to update any library out there (mission inspiration?? 😅)
Validations
The text was updated successfully, but these errors were encountered: