-
Notifications
You must be signed in to change notification settings - Fork 32
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] next 15.2.0 breaks non static routes #432
Comments
+1 getting this too |
+1 I am also getting this error |
Also receiving this issue, I'm trying to use dynamic routes. This page works at /app/static/page.tsx: export default function StaticPage() {
return <h1>This is a static page</h1>;
} This page never works regardless of whether I make it client side, here's an example of client side at /app/static/[id]/page.tsx: 'use client';
import { useParams } from 'next/navigation';
export default function StaticIdPage() {
const params = useParams<{ id: string }>();
return <h1>Static Page: {params.id}</h1>;
}
I've tried adding various exports to the top of pages like the following which make no difference: export const dynamic = 'force-dynamic';
export const runtime = 'nodejs'; I've tried figuring out where the request is dying by running build worker and then updating worker.js to have the following: console.log('Worker started.');
addEventListener('fetch', (event) => {
console.log('🔥 Incoming request:', event.request.url);
// Respond immediately so we can see if the worker is running
event.respondWith(
new Response('Worker is handling this request.', {
headers: { 'Content-Type': 'text/plain' }
})
);
}); Only "Worker started" is ever logged to the console so I don't even think it got to my page's code. I've tried completely removing the I added a middleware.ts file with the following just to log requests, the middleware did log the request hit for the dynamic route but the request seems to die somewhere after the middleware. import { NextResponse } from 'next/server';
export function middleware(request: Request) {
console.log('Middleware hit:', request.url);
return NextResponse.next();
} |
Same thing happens with the recently released |
I took a quick look at this issue. One problem is that |
Downgrading to 15.1.7 fixed this |
Confirm. It works after downgrading to 15.1.7 |
What other versions were you using? I tried deleting my node_modules, .next, and .open-next folder and changing package references to 15.1.7 and was still having the same issue. I'm guessing I'm either doing something different in my project it doesn't like or there's a version of wrangler or open-next that needs to coincide with it. |
Describe the bug
I've upgraded my app to next 15.2.0 and now i'm getting a 500 on some routes.
From a quick check it seems to only happen on the routes that don't use
generateStaticParams
Versions of opennext/next/vercel:
Steps to reproduce
generateStaticParams
opennextjs-cloudflare && wrangler dev
Expected behavior
@opennextjs/cloudflare version
0.5.7
Wrangler version
3.111.0
next info output
Operating System: Platform: linux Arch: x64 Version: #1 SMP PREEMPT_DYNAMIC Thu, 27 Feb 2025 18:09:44 +0000 Available memory (MB): 31302 Available CPU cores: 16 Binaries: Node: 20.18.2 npm: 10.8.2 Yarn: 1.22.19 pnpm: 10.1.0 Relevant Packages: next: 15.2.0 // Latest available version is detected (15.2.0). eslint-config-next: 15.2.0 react: 19.0.0 react-dom: 19.0.0 typescript: 5.8.2 Next.js Config: output: N/A
Additional context
No response
The text was updated successfully, but these errors were encountered: