Have anyone encountered that sometimes vite dev server just stops working until restart?
Sometimes, after vite dev server works for a while, instead of proper responses I start receiving responses such as
[OMITTED]</style></head><body><!--frsh:key:-2--><!--/frsh:key--></body></html>
[OMITTED]</style></head><body><!--frsh:key:-19--><!--/frsh:key--></body></html>
With each request, frsh:key goes downwards, looks like some state is being preserved between requests.
This comment tag is located in place of <Component/> in _app.tsx:
<body>
<Component />
</body>
If I add anything before/after <Component/>, then I receive it in the responses, e.g
<body>
Before
<Component />
After
</body>
Results in
[OMITTED]</style></head><body>Before<!--frsh:key:-2--><!--/frsh:key-->After</body></html>
This happens with both server-rendered routes:
export default define.page(function Static() {
return (
<div>
Some static text
</div>
);
})And with routes with islands, no <script> for island initialization is present in this case
That continues until the dev server restart.
Right now I don't see anything which may help to debug this problem right now, there is no errors displayed anywhere.
Have anyone encountered that sometimes vite dev server just stops working until restart?
Sometimes, after vite dev server works for a while, instead of proper responses I start receiving responses such as
With each request, frsh:key goes downwards, looks like some state is being preserved between requests.
This comment tag is located in place of
<Component/>in _app.tsx:If I add anything before/after
<Component/>, then I receive it in the responses, e.gResults in
This happens with both server-rendered routes:
And with routes with islands, no
<script>for island initialization is present in this caseThat continues until the dev server restart.
Right now I don't see anything which may help to debug this problem right now, there is no errors displayed anywhere.