-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
Vue purported vnode error in CodeSandbox #8451
Comments
This is such a weird bug, I've seen it pop up before. Deleting node_modules and reinstalling fixes it, but that's of course not desired. I'm going to see why Vue gets a wrong version the second time the VM starts 馃 |
It's the same issue discussed on #8298. It's quite annoying because it can reappear at any time, for example, I just updated the dependencies of our sandbox (which was working fine), and boom, there it was 馃槥 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
馃悰 bug report
Preflight Checklist
adheres to.
to file, without success.
Description of the problem
I had my Vue 3 app working fine. I did not make any changes and opened the Codesandbox to copy a link to the working app. All of sudden I saw the below error.
My app does not have any
vnode
elements (verified through a search). It couldn't have had anyvnode
elements since this is a brand-new app created with latest copy of Vue and Vite two days ago. Below is an excerpt from the error message:I pulled the branch from Codesanbox through GitHub into an offline VS Code instance. From there, I was able to run it without issues. When I duplicated the branch and pulled it into Codesanbox, it had the same error.
After a lot of trial and error, what solved it was deleting the
node_modules
folder andpackage-lock
file and then runningnpm install
again.I am reporting it because the above behavior seems like a bug peculiar to Codesandbox, since it wasn't present offline.
Also, I saw the same error message two days ago when I tried to start a new Vue project in Codesandbox. At that time I went around it by initializing the project offline and pulling it in though GitHub.
How has this issue affected you? What are you trying to accomplish?
I had to send a link to a working app for review and I couldn't send it on time :(
To Reproduce
Open:
https://codesandbox.io/p/github/divensky/commandbar-example/test-env-2
(this is a brunch where I haven't done the above fix with reinstalling
node_modules
; it still shows the error).Link to sandbox: link (optional)
Here are two screenshots of the error message:
Your Environment
The text was updated successfully, but these errors were encountered: