fix: restore full pattern after Next.js 15.6 Turbopack fix #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.
Summary
This PR proposes reverting the Turbopack pattern restrictions introduced in #398 and #399 once Next.js 15.6.0 is released as stable.
The underlying middleware crash bug has been fixed in Next.js 15.6.0-canary.22, allowing us to restore full code-inspector coverage across the entire codebase by returning to the original
**/*.{jsx,tsx,js,ts,mjs,mts}
pattern.Context
Previous workarounds (no longer needed):
**/app/**/*.{jsx,tsx,js,ts,mjs,mts}
components/
,lib/
,hooks/
, etc.**/*.{jsx,tsx}
+ specific Next.js routing files (layout.js, page.ts, etc.).js
,.ts
,.mjs
,.mts
files to avoid middlewareThese restrictions were necessary to avoid the Turbopack middleware crash documented in:
The fix:
The underlying Turbopack bug has been fixed in Next.js 15.6.0-canary.22 via vercel/next.js#83683
Changes
Reverts to original full pattern:
**/*.{jsx,tsx,js,ts,mjs,mts}
components/
,lib/
,hooks/
,app/
, etc.Removes
enforce
property: Not supported in Next.js 15.6+Updates demo to Next.js 15.6.0-canary.38: Proves the fix works
Status
15.6.0-canary.38
15.6.0
is released as stableTesting
pnpm dev