🐛 BUG: Dev Server not resetting automatically

[Eloi-Perez]

What version of astro are you using?

1.0.0-beta.20

Are you using an SSR adapter? If so, which one?

None

What package manager are you using?

npm

What operating system are you using?

Windows 10 21H2 - PowerShell 7.2.3

Describe the Bug

Using the development server astro dev, when I do a mistake on my code giving me as a result a "500: Internal Error", once I fix the error the server is suppose to reset and show me the website if everything is fine with my code, but every time, I have to reset the server manually.

Link to Minimal Reproducible Example

Can't reproduce it online

Participation

• I am willing to submit a pull request for this issue.

[Eloi-Perez]

I also just tried the Dev Server with WSL2 (Ubuntu) and I have exactly the same problem.

[Jutanium]

See #3228 and others, this is important

[Jutanium]

Related issues - I'm not sure which of these have the same root cause, but in all cases we can improve the end-user situation with error boundaries
#3196
#3180
#2921

Panic mode - here there are two problems at hand: one is that there is a bug, and the other is that the compiler shifts into a very unfriendly panic mode:
withastro/compiler#390
#3253

We've actually had that named slot issue open for more than two weeks: withastro/compiler#388

[matthewp]

Upstream PR needs merging before we can fix this one: vitejs/vite#8052

[matthewp]

Upstream was merged, waiting on a release.

[matthewp]

After Vite 2.9.9 is merged we can fix this. We need to update the Astro plugin to set import.meta.hot here:

astro/packages/astro/src/vite-plugin-astro/index.ts

Line 185 in 1acbcab

// // import.meta.hot.accept(["${id}", "${Array.from(deps).join('","')}"], (...mods) => mods);

. Doing so will cause it to correctly invalidate .astro modules when dependencies go from broken to fixed.

[Jutanium]

Thanks! Will this also fix the issue with Astro.glob (i.e., when you put an invalid string in there, and then fix it, the dev server should be good to go)

[Eloi-Perez]

It seems to be fixed now. Thank you!