Hi there! Thank you for providing this awesome project!
Context
I want to preface this bug report (whilst im a little unsure whether its rooted in vike or vite) that Vike got us quite far moving from a purely pre built and client rendered react application to a SSR (capable) approach with our own node server, a great routing system etc.
We did also make the move to a nx powered, not eagerly compiled mono repo fwiw, so packages contain source code that is installed into node modules and only then gets compiled.
Problem
The problem we are seeing is some huge spikes in initial render times as compared to a minimal viable examples. Read: 1 minute to render the initial page – I pinned this down to the await renderPage(ctx) specifically so this comes from either vike or vite behaving unexpectedly slow in our environment. I would like to understand why and to ship a fix!
Have you encountered this before / any clues what may cause this? I could imagine it being unable for you to reproduce due to the close coupling with our concrete repository.
[vike][Warning] Crawling your + files took an unexpected long time (3.3 seconds). If you consistently get this warning, then consider reaching out on GitHub.
Description
Hi there! Thank you for providing this awesome project!
Context
I want to preface this bug report (whilst im a little unsure whether its rooted in vike or vite) that Vike got us quite far moving from a purely pre built and client rendered react application to a SSR (capable) approach with our own node server, a great routing system etc.
We did also make the move to a nx powered, not eagerly compiled mono repo fwiw, so packages contain source code that is installed into node modules and only then gets compiled.
Problem
The problem we are seeing is some huge spikes in initial render times as compared to a minimal viable examples. Read: 1 minute to render the initial page – I pinned this down to the
await renderPage(ctx)
specifically so this comes from either vike or vite behaving unexpectedly slow in our environment. I would like to understand why and to ship a fix!Have you encountered this before / any clues what may cause this? I could imagine it being unable for you to reproduce due to the close coupling with our concrete repository.
Vite Config / Version
Version(s):
vite.config.ts
Vike Config
Version(s):
pages/+config.ts
: