Blitz: `blitz start` is significantly slower to start than `next dev`

Created on 13 Sep 2020  路  1Comment  路  Source: blitz-js/blitz

What is the problem?

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.

Steps to Reproduce

  1. Run blitz start several times and notice the start time.
  2. Run yarn next .blitz/caches/dev several times and notice the much faster start time

Versions

0.22.0

cc @ryardley

kinbug statudone

Most helpful comment

Be happy jump on this - I have had a plan for this for a while.

>All comments

Be happy jump on this - I have had a plan for this for a while.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

netheril96 picture netheril96  路  4Comments

LoriKarikari picture LoriKarikari  路  4Comments

ganeshmani picture ganeshmani  路  4Comments

yhoiseth picture yhoiseth  路  3Comments

eorenstein1 picture eorenstein1  路  3Comments