Issue Station
Sign In
Tools hereToolbox

nextjs - ✅(Solved) Fix Exclude test files from TypeScript type checking [1 pull requests, 1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
vercel/next.js#92408•Fetched 2026-04-08 03:00:00
View on GitHub
Comments
0
Participants
1
Timeline
2
Reactions
0
Author
donkeyotedonkeyote
Participants
donkeyotedonkeyote
Timeline (top)
cross-referenced ×1issue_type_added ×1

Fix Action

Fixed

PR fix notes

PR #92409: fix: ensure test files are ignored when type checking

Description (problem / solution / changelog)

Fixes #92408 Move test file exclusion filter to run before the TypeScript program is created, rather than filtering diagnostics after the emit.

Previously, test and mock files (tests, mocks, .spec., .test.) were still compiled as part of the program — their errors were just suppressed. Now they are excluded from rootNames upfront, so they are never type-checked at all.

<!-- 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 ### 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 # -->

Changed files

  • packages/next/src/lib/typescript/runTypeCheck.ts (modified, +12/-11)

Code Example

Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 25.4.0: Thu Mar 19 19:31:09 PDT 2026; root:xnu-12377.101.15~1/RELEASE_ARM64_T8132
  Available memory (MB): 24576
  Available CPU cores: 10
Binaries:
  Node: 22.16.0
  npm: 10.9.2
  Yarn: 1.22.22
  pnpm: 10.28.1
Relevant Packages:
  next: 16.2.2 // Latest available version is detected (16.2.2).
  eslint-config-next: N/A
  react: 19.2.4
  react-dom: 19.2.4
  typescript: 5.9.3
Next.js Config:
  output: N/A
RAW_BUFFERClick to expand / collapse

Link to the code that reproduces this issue

https://github.com/donkeyote/next-tests-typecheck

To Reproduce

  1. run pnpm build
  2. check inside .next/cache/.tsbuildinfo and the page.test.tsx file will be included.

Current vs. Expected behavior

page.test.tsx should not be found in the tsbuildinfo as it should be excluded from the type checking

Provide environment information

Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 25.4.0: Thu Mar 19 19:31:09 PDT 2026; root:xnu-12377.101.15~1/RELEASE_ARM64_T8132
  Available memory (MB): 24576
  Available CPU cores: 10
Binaries:
  Node: 22.16.0
  npm: 10.9.2
  Yarn: 1.22.22
  pnpm: 10.28.1
Relevant Packages:
  next: 16.2.2 // Latest available version is detected (16.2.2).
  eslint-config-next: N/A
  react: 19.2.4
  react-dom: 19.2.4
  typescript: 5.9.3
Next.js Config:
  output: N/A

Which area(s) are affected? (Select all that apply)

Not sure

Which stage(s) are affected? (Select all that apply)

next build (local)

Additional context

No response

extent analysis

TL;DR

Exclude the page.test.tsx file from type checking by configuring the next build process to ignore test files.

Guidance

  • Review the next.config.js file to ensure that test files are excluded from the build process.
  • Check the tsconfig.json file to verify that the exclude option is configured to ignore test files.
  • Use the --exclude flag with the pnpm build command to exclude specific files or directories from the build process.
  • Verify that the page.test.tsx file is not being imported or required by any other files that are included in the build process.

Example

// next.config.js
module.exports = {
  //... other configurations ...
  exclude: ['**/*.test.tsx'],
}

Notes

The solution assumes that the page.test.tsx file is not intended to be part of the production build. If the file is required for testing purposes, an alternative approach may be needed.

Recommendation

Apply workaround: exclude test files from the build process using the exclude option in next.config.js or tsconfig.json. This approach ensures that test files are not included in the type checking process.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#index setup#retrieval issue#search optimization#API routing#API middleware

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

nextjs - ✅(Solved) Fix Exclude test files from TypeScript type checking [1 pull requests, 1 participants]