Which project is this feature idea for?

Turbopack

Describe the feature you'd like to request

Looking for some feedback,

At our company (like many others) we have a significant number of E2E tests that grow linearly as the project grows; Many frontend applications have monolithic style architecture which leads to build times and test times also growing linearly over time.

At a certain point people start to reach the maturity where they parallelize their E2E tests, but what I want to champion is a level of maturity after that where we allow developers access to the 'cache key' functionality of Turbopack.

https://turbo.build/pack/docs/core-concepts#how-does-it-help
See ("In the future, a persistent cache will open the door to much faster production builds")

What I would like to suggest is that in this future planning for exposing this cache invalidation functionality (I.E giving a list of the pages that have broken the cache)

If this functionality is exposed back then running E2E test suites "only on what's changed" will become easily possible, as well as obviously incremental builds and anything else plugin developers can imagine this being useful for.

This will run on the following (suggested) semantics

1: Any (package.json) dependency changes = Retest all pages.
2: Page changes = Test just that page.
4: Dependency of page(s) changes = Retest pages that had that dependency in their dependency tree (i.e if a component changes like Button or a utility)