Vue version

3.2.38

Link to minimal reproduction

https://github.com/brandonapol/birchwood/tree/master/frontend/birchwood

Steps to reproduce

"[Vue warn]: Unhandled error during execution of scheduler flush. This is likely a Vue internals bug. Please open an issue at https://new-issue.vuejs.org/?repo=vuejs/core at at "

I'm not even sure what I did to get this. I'm brand new to Vue, having worked in React for a year or two. I'll attach my GitHub.

What is expected?

Just trying to run an app and make a new component on my own - I watched a lot of the Vue Mastery content, felt good about it, went off on my own and have been duly punished for my audacity 🙂 Which is normal. But the console told me the issue I'd found was a Vue internal error. There are a couple eslint errors but I don't think they're the problem. All I'm doing is trying to create and implement a minimal new component with Tailwind, babel, and Typescript.

ERROR in [eslint] /Users/brandonapol/Documents/portfolio/birchwood/frontend/birchwood/src/components/NavbarView.vue 2:3 error Delete ·· prettier/prettier 12:1 error Delete ⏎ prettier/prettier

/Users/brandonapol/Documents/portfolio/birchwood/frontend/birchwood/src/views/MainView.vue 4:16 error Insert · prettier/prettier

✖ 3 problems (3 errors, 0 warnings) 3 errors and 0 warnings potentially fixable with the --fix option.

What is actually happening?

At this point, even running the HelloWorld.vue component from the default app creation isn't working - the navbar with Home | About is displaying, and trying to access the other components is repeatedly throwing the error above.

There are likely actual issues with my code as well, ordinarily I wouldn't do this, but the console specifically told me to bring this issue up with you as a potential internal Vue bug.

System Info

System:
    OS: macOS 11.6
    CPU: (8) arm64 Apple M1
    Memory: 147.28 MB / 8.00 GB
    Shell: 5.8 - /bin/zsh
  Binaries:
    Node: 18.6.0 - /opt/homebrew/bin/node
    npm: 8.13.2 - /opt/homebrew/bin/npm
  Browsers:
    Chrome: 104.0.5112.101
    Safari: 15.0
  npmPackages:
    vue: ^3.2.13 => 3.2.37

Any additional comments?

No response

the eslint errors are just that - eslint errors that can be fixed by running npm run lint.

Can't reproduce the original error message though by running this repo. Might be because there was not list of steps provided to actually reproduce it.

Figured it out this morning. I believe it has to do with the web sockets and running the app locally, I accidentally re-created the issue this morning when I opened my macbook again after leaving it closed overnight. Whatever happens when I close my laptop and open it up again means I have to re-start the Vue app to make it work. Obviously this is not an issue in a data center so not an issue and also I can fix it by simply turning it off and back on again.