Skip to content

Conversation

lars-hagen
Copy link
Contributor

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):

These 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

  1. Reverts to original full pattern: **/*.{jsx,tsx,js,ts,mjs,mts}

    • Restores coverage for all file types across the entire codebase
    • No longer restricted by directory or file extension
    • Works everywhere: components/, lib/, hooks/, app/, etc.
  2. Removes enforce property: Not supported in Next.js 15.6+

  3. Updates demo to Next.js 15.6.0-canary.38: Proves the fix works

Status

⚠️ This is a placeholder PR for consideration ⚠️

  • Currently uses canary version 15.6.0-canary.38
  • Should be merged once 15.6.0 is released as stable
  • Demonstrates that the original full pattern now works without crashes

Testing

  • ✅ Middleware file present (previously caused crash)
  • ✅ Code inspector works across entire codebase
  • ✅ No Turbopack errors with full pattern
  • ✅ Demo runs successfully with pnpm dev

@lars-hagen lars-hagen marked this pull request as ready for review October 1, 2025 11:17
@zh-lx
Copy link
Owner

zh-lx commented Oct 2, 2025

Thank you for your PR, I believe this PR can be merged after the official release of NextJS 15.6.0.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants