Next.js re-uses it's own build cache between next dev invocations so that subsequent runs of next dev start extremely fast.
But the problem is that we are deleting the entire .blitz cache folder, including the next.js cache. This means that blitz start is always slow to start.
blitz start several times and notice the start time.yarn next .blitz/caches/dev several times and notice the much faster start time0.22.0
cc @ryardley
Be happy jump on this - I have had a plan for this for a while.
Most helpful comment
Be happy jump on this - I have had a plan for this for a while.