You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I believe there is something going on with vite not cancelling in progress transpilations when there are many changes in the latest vite release 4.1.1. This is reproducible by starting the vite server and then spamming restart in 1-2s intervals (to mimic a large codebase) until the server eventually crashes.
Observations
sometimes it exits with code 1 or 129 or SEGV or terminal just freezes completely
once vite starts crashing and hanging it becomes easier to crash afterwards
npm install
npm run dev
# open firefox 110# open devtools# disable cache# keep hitting r in 1s intervals before the page fully loads# wait for page to turn blank# terminal becomes unresponsive to hitting r
Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to vuejs/core instead.
@benatshippabo would you re-test your issue with vite@4.3.0-beta.4? There have been several changes to the way we handle server restarts and cancellations.
@patak-dev yes this fixes it. I do get this error if I turn https on and use the ssl plugin:
error when starting dev server:
Error: ENAMETOOLONG: name too long, open '/Users/btea/git/react-vite-realworld-example-app/-----BEGIN RSA PRIVATE KEY-----
Describe the bug
I believe there is something going on with vite not cancelling in progress transpilations when there are many changes in the latest vite release 4.1.1. This is reproducible by starting the vite server and then spamming restart in 1-2s intervals (to mimic a large codebase) until the server eventually crashes.
Observations
Reproduction
https://github.com/benatshippabo/react-vite-realworld-example-app
Steps to reproduce
System Info
Used Package Manager
npm
Logs
Last 3000 lines of log
Validations
The text was updated successfully, but these errors were encountered: