Replaced by the milestone - https://github.com/cloudflare/vinext/milestone/1.
Vinext runs the Next.js Adapter API test suite nightly, and surfaces the results through https://vinext.dev/compatibility
This test suite represents a baseline of what the framework should expect to pass. There are certain tests that may not necessarily be applicable to Vinext due to the nature of it being a framework rather than an adapter, but nevertheless, a large portion of them are crucial for us to support.
The core focus is on addressing the parity gaps surfaced by the test suite, and this issue is a parent for various problems that are identified by agents analysing the logs from test suite failures in the nightly CI runs.
Replaced by the milestone - https://github.com/cloudflare/vinext/milestone/1.
Vinext runs the Next.js Adapter API test suite nightly, and surfaces the results through https://vinext.dev/compatibility
This test suite represents a baseline of what the framework should expect to pass. There are certain tests that may not necessarily be applicable to Vinext due to the nature of it being a framework rather than an adapter, but nevertheless, a large portion of them are crucial for us to support.
The core focus is on addressing the parity gaps surfaced by the test suite, and this issue is a parent for various problems that are identified by agents analysing the logs from test suite failures in the nightly CI runs.