Description

On main, pnpm test fails (sometimes intermittently, depending on cache scenarios, but all the time without cache). Why? Well..

Three of the examples had version 9 lockfiles checked in to git, when version 6 is what's required by their packageManager fields. This causes tests to fail quite frequently (example) in many PRs. This happens because when installing in these repos you get Lockfile not compatible with current pnpm errors, and it totally blows away the old lockfile and grabs a new one. Then, since our Next.js version is specified as ^4.1.1 in these package.jsons, it will resolve to 4.2.15 instead of the old 4.1.1. Then, it turns out that this minor update causes this diff in the next-env.d.ts file:

/// <reference types="next" />
/// <reference types="next/image-types/global" />

// NOTE: This file should not be edited
- // see https://nextjs.org/docs/basic-features/typescript for more information.
+ // see https://nextjs.org/docs/app/building-your-application/configuring/typescript for more information.

The fact of that diff happening causes turbo to not be "FULL TURBO", which the example tests checks for. That then causes the test suite to fail because there's a turbo cache miss.

Testing Instructions

pnpm test should now pass.