Morgan :)

Now done/released.

@amrgetment Thanks, but caching is not relevant to this issue: it just hides the problem.

> > * `mockito` is about 2x as fast as `freezed`, I believe that is because mockito adds a part file to the test where it does not become a...

> > notice the incremental build time for 500 libraries and 1000 libraries: it increases from 35s to 119s, an increase of x3.4. For double the number of libraries the...

@esDotDev yes, for sure. You get quite a lot faster small incremental builds if you use `watch` mode; I'm not sure yet how much people are forced to use `build`...

> For that reason, I feel like there's a missed opportunity by not investigating better cache invalidation strategies. There's an arc of work happening over in the analyzer to support...

> I haven't been using `watch` mode for `build_runner` for several years. It used to delete generated files (it was looking it, at least), so my code analysis constantly was...

> [@davidmorgan](https://github.com/davidmorgan) I filed an [issue](https://github.com/dart-lang/build/issues/4025#issue-3119339795) I've experienced with `watch` mode today. Though I don't experience any constant breakages with analyzer anymore, it still happens occasionally: a syntax error in...

> Excuse me, could you tell where or when this will be available? I couldn't find this information Do you mean the release of the refactor for performance? Soon, hoping...

This specific scalability issue is resolved, and released as `build_runner 2.5.0` so I'll close the issue. I have a pile of further performance improvements that I'll be working on next....