John Albin Wilkins

Turbopack isn't fully supported _by Next.js_ yet. From https://nextjs.org/docs/architecture/turbopack: > Turbopack currently only supports `next dev` and does not support `next build`. We are currently working on support for builds...

I randomly found this website today which shows whether turbopack-related tests are passing in Next.js v14: https://areweturboyet.com > Maybe can I add something to the documentation ? I'm reopening this...

The `context` object is what I'm struggling with at the moment as well. Let's walk through the old `pages/[...slug].tsx` flow so we all (including me) understand it. ### How the...

I've updated my comment above showing “`NodePage` calls `drupal.getResource(type, uuid, { params })`”. I figured that out when adding the `examples/example-router-migration` to the next-drupal repo. https://github.com/chapter-three/next-drupal/tree/main/examples/example-router-migration

From the error log: ``` 1) Drupal\Tests\next\Kernel\Renderer\MainContent\NextSiteEntityControllerTest::testEnvironmentVariables PHPUnit\Framework\Exception: Unavailable module: 'consumers'. If this module needs to be downloaded separately, annotate the test class with '@requires module consumers'. ```

I'm not sure the `engines` entry gains us anything. We want to support any supported version of Node.js, and, afaik, we don't have any specific supported Node.js versions that we...

We'll keep v16 support through 2.x. And drop it with 3.x.

This warning might go away without needing any fixes when we implement https://github.com/chapter-three/next-drupal/issues/534

I just swapped the src files with the build files in our Jest tests and the Jest tests still aren't catching the broken build. :\

The current tests.nextdrupal.org instance is running Drupal 9.4.x and 99% of the test content is just the Umami demo content. That's good news since it means it might be possible...