fix: restore full pattern + fix Next.js 16 Turbopack warnings #401
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR restores the original full pattern
**/*.{jsx,tsx,js,ts,mjs,mts}for code-inspector and fixes Next.js 16 Turbopack configuration warnings.Background
The original pattern was restricted in two previous PRs due to a Turbopack middleware crash bug:
**/app/**/*.{jsx,tsx,js,ts,mjs,mts}(missed components/, lib/, hooks/, etc.)**/*.{jsx,tsx}+ specific routing files (excluded .js, .ts, .mjs, .mts files)The Turbopack crash bug was fixed in Next.js 15.6.0-canary.22, but 15.6.0 was never released as stable. Next.js jumped from 15.5.6 directly to 16.0.0 (Oct 22, 2025).
What This PR Does
**/*.{jsx,tsx,js,ts,mjs,mts}to properly cover all project filesenforcekeys that cause config warnings in Next.js 16turbopack-next15→turbopack-nextto avoid version number maintenanceTesting
Tested with Next.js 16.0.1 - no warnings, full file coverage restored.