Turbopack build: Skip typedRoutes tests (experimental feature) (#67891)

This feature is not supported yet in Turbopack and since it's
experimental it will be implemented after stable 👍
<!-- Thanks for opening a PR! Your contribution is much appreciated.
To make sure your PR is handled as smoothly as possible we request that
you follow the checklist sections below.
Choose the right checklist for the change(s) that you're making:

## For Contributors

### Improving Documentation

- Run `pnpm prettier-fix` to fix formatting issues before opening the
PR.
- Read the Docs Contribution Guide to ensure your contribution follows
the docs guidelines:
https://nextjs.org/docs/community/contribution-guide

### Adding or Updating Examples

- The "examples guidelines" are followed from our contributing doc
https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md
- Make sure the linting passes by running `pnpm build && pnpm lint`. See
https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md

### Fixing a bug

- Related issues linked using `fixes #number`
- Tests added. See:
https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs
- Errors have a helpful link attached, see
https://github.com/vercel/next.js/blob/canary/contributing.md

### Adding a feature

- Implements an existing feature request or RFC. Make sure the feature
request has been accepted for implementation before opening a PR. (A
discussion must be opened, see
https://github.com/vercel/next.js/discussions/new?category=ideas)
- Related issues/discussions are linked using `fixes #number`
- e2e tests added
(https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs)
- Documentation added
- Telemetry added. In case of a feature if it's used or not.
- Errors have a helpful link attached, see
https://github.com/vercel/next.js/blob/canary/contributing.md


## For Maintainers

- Minimal description (aim for explaining to someone not on the team to
understand the PR)
- When linking to a Slack thread, you might want to share details of the
conclusion
- Link both the Linear (Fixes NEXT-xxx) and the GitHub issues
- Add review comments if necessary to explain to the reviewer the logic
behind a change

### What?

### Why?

### How?

Closes NEXT-
Fixes #

-->

Author: timneutkens

docs/04-architecture/turbopack.mdx

@@ -46,6 +46,8 @@ These features are currently not supported:
   - We are planning to implement this in the future.
 - [Relay transforms](/docs/architecture/nextjs-compiler#relay)
   - We are planning to implement this in the future.
+- [`experimental.typedRoutes](https://nextjs.org/docs/app/api-reference/next-config-js/typedRoutes)
+  - We are planning to implement this in the future.
 - `experimental.nextScriptWorkers`
   - We are planning to implement this in the future.
 - `experimental.sri.algorithm`

test/integration/app-types/app-types.test.js

@@ -6,7 +6,8 @@ import { nextBuild } from 'next-test-utils'
 
 const appDir = __dirname
 
-describe('app type checking', () => {
+// Turbopack doesn't support additional experimental features in the first version
+;(process.env.TURBOPACK ? describe.skip : describe)('app type checking', () => {
   ;(process.env.TURBOPACK_DEV ? describe.skip : describe)(
     'production mode',
     () => {

test/production/app-dir/typed-routes-with-webpack-worker/typed-routes-with-webpack-worker.test.ts

@@ -1,40 +1,44 @@
 import { nextBuild } from 'next-test-utils'
 import path from 'path'
+;(process.env.TURBOPACK ? describe.skip : describe)(
+  'app dir - typed-routes-with-webpack-worker',
+  () => {
+    it('builds successfully without errors', async () => {
+      const output = await nextBuild(
+        path.join(__dirname, 'good-routes'),
+        undefined,
+        {
+          stdout: true,
+          stderr: true,
+        }
+      )
 
-describe('app dir - typed-routes-with-webpack-worker', () => {
-  it('builds successfully without errors', async () => {
-    const output = await nextBuild(
-      path.join(__dirname, 'good-routes'),
-      undefined,
-      {
-        stdout: true,
-        stderr: true,
-      }
-    )
+      // check for the experimental flag warning
+      expect(output.stdout).toContain('webpackBuildWorker')
+      // should have a successful build
+      expect(output.code).toBe(0)
+      // with no errors
+      expect(output.stderr).not.toContain(`"/" is not an existing route.`)
+    })
 
-    // check for the experimental flag warning
-    expect(output.stdout).toContain('webpackBuildWorker')
-    // should have a successful build
-    expect(output.code).toBe(0)
-    // with no errors
-    expect(output.stderr).not.toContain(`"/" is not an existing route.`)
-  })
+    it('builds with valid errors', async () => {
+      const output = await nextBuild(
+        path.join(__dirname, 'bad-routes'),
+        undefined,
+        {
+          stdout: true,
+          stderr: true,
+        }
+      )
 
-  it('builds with valid errors', async () => {
-    const output = await nextBuild(
-      path.join(__dirname, 'bad-routes'),
-      undefined,
-      {
-        stdout: true,
-        stderr: true,
-      }
-    )
-
-    // check for the experimental flag warning
-    expect(output.stdout).toContain('webpackBuildWorker')
-    // should have a failed build
-    expect(output.code).toBe(1)
-    // with correct error
-    expect(output.stderr).toContain(`"/asdfasdfasdf" is not an existing route.`)
-  })
-})
+      // check for the experimental flag warning
+      expect(output.stdout).toContain('webpackBuildWorker')
+      // should have a failed build
+      expect(output.code).toBe(1)
+      // with correct error
+      expect(output.stderr).toContain(
+        `"/asdfasdfasdf" is not an existing route.`
+      )
+    })
+  }
+)

test/turbopack-build-tests-manifest.json

@@ -6890,12 +6890,12 @@
     },
     "test/integration/app-types/app-types.test.js": {
       "passed": [],
-      "failed": [
+      "failed": [],
+      "pending": [
         "app type checking production mode should generate route types correctly and report link error",
         "app type checking production mode should generate route types correctly and report router API errors",
         "app type checking production mode should type check invalid entry exports"
       ],
-      "pending": [],
       "flakey": [],
       "runtimeError": false
     },
@@ -15548,11 +15548,11 @@
     },
     "test/production/app-dir/typed-routes-with-webpack-worker/typed-routes-with-webpack-worker.test.ts": {
       "passed": [],
-      "failed": [
+      "failed": [],
+      "pending": [
         "app dir - typed-routes-with-webpack-worker builds successfully without errors",
         "app dir - typed-routes-with-webpack-worker builds with valid errors"
       ],
-      "pending": [],
       "flakey": [],
       "runtimeError": false
     },