kdy1/repro-next-66918 — explained in plain English
Analysis updated 2026-07-18 · repo last pushed 2024-06-15
Clone the repo and follow the steps to confirm you're hitting the same PUT-request 405 bug in your own Next.js project.
Use this minimal reproduction to test whether a proposed Next.js patch actually fixes the production API route bug.
Reference the exact setup to file or comment on the related Next.js GitHub issue with a clear, reproducible example.
Study the difference between Next.js dev-mode and production-build API route handling using this as a concrete case.
| kdy1/repro-next-66918 | 0verflowme/alarm-clock | 0verflowme/seclists | |
|---|---|---|---|
| Language | — | CSS | — |
| Last pushed | 2024-06-15 | 2022-10-03 | 2020-05-03 |
| Maintenance | Dormant | Dormant | Dormant |
| Setup difficulty | easy | easy | easy |
| Complexity | 2/5 | 2/5 | 1/5 |
| Audience | developer | vibe coder | ops devops |
Figures from each repo's GitHub metadata at analysis time.
The bug only appears after running a production build, not in the development server.
This is a bug report and demonstration project for Next.js, a popular framework for building web applications. The issue shows that API endpoints behave differently depending on whether you're developing the app locally or running it in production mode. Here's the concrete problem: if you create an API endpoint that only handles two types of requests, GET (to fetch data) and PUT (to update data), it works fine when you're testing during development. But once you build and deploy the same code for production, the PUT requests stop working and return a "405 Method Not Allowed" error. The GET requests still work fine, but PUT requests are suddenly rejected. This shouldn't happen, the code is identical in both environments, so the behavior should be the same. The repository is essentially a minimal example that reproduces this bug so developers can see it happen themselves. Someone working on the Next.js framework would use this to understand and fix the underlying problem. A developer using Next.js might find it helpful to know about this issue if they're encountering the same problem in their own projects. The README walks through exactly how to trigger the bug: create a new Next.js app, add an API route with GET and PUT handlers, run it in development mode (where it works), then build it for production (where it breaks). This step-by-step approach makes it easy for others to verify they're experiencing the same issue or to test whether a fix actually resolves it.
A minimal Next.js reproduction showing that an API route's PUT handler works in development but returns a 405 error in production, helping the Next.js team debug the issue.
Dormant — no commits in 2+ years (last push 2024-06-15).
Setup difficulty is rated easy, with roughly 5min to a first successful run.
Mainly developer.
This repo across BitVibe Labs
double-check against the repo, no cap.