git404hub

what is repro-next-66918 fr?

kdy1/repro-next-66918 — explained in plain English

Analysis updated 2026-07-18 · repo last pushed 2024-06-15

Audience · developerComplexity · 2/5DormantSetup · easy

tl;dr

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.

vibe map

mindmap
  root((repo))
    What it does
      Reproduces a bug
      Shows dev vs prod diff
      API route example
    Tech stack
      Next.js
      Node.js
    Use cases
      Verify the bug
      Test a proposed fix
      Report to maintainers
    Audience
      Next.js developers
      Framework maintainers
    Steps
      Add GET and PUT route
      Run dev mode
      Build for production

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

what do people make with this?

VIBE 1

Clone the repo and follow the steps to confirm you're hitting the same PUT-request 405 bug in your own Next.js project.

VIBE 2

Use this minimal reproduction to test whether a proposed Next.js patch actually fixes the production API route bug.

VIBE 3

Reference the exact setup to file or comment on the related Next.js GitHub issue with a clear, reproducible example.

VIBE 4

Study the difference between Next.js dev-mode and production-build API route handling using this as a concrete case.

what's the stack?

Next.jsJavaScriptNode.js

how it stacks up fr

kdy1/repro-next-669180verflowme/alarm-clock0verflowme/seclists
LanguageCSS
Last pushed2024-06-152022-10-032020-05-03
MaintenanceDormantDormantDormant
Setup difficultyeasyeasyeasy
Complexity2/52/51/5
Audiencedevelopervibe coderops devops

Figures from each repo's GitHub metadata at analysis time.

how do i run it?

Difficulty · easy time til it works · 5min

The bug only appears after running a production build, not in the development server.

in plain english

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.

prompts (copy fr)

prompt 1
Clone this repro-next-66918 project and walk me through building it for production so I can see the PUT request 405 error myself.
prompt 2
Explain why a Next.js API route with GET and PUT handlers might behave differently in development versus a production build.
prompt 3
Using this repro as a reference, write a minimal Next.js API route with GET and PUT handlers and show me how to test both locally.
prompt 4
Help me adapt this reproduction case into a bug report comment with clear reproduction steps for the Next.js GitHub issue.

Frequently asked questions

what is repro-next-66918 fr?

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.

Is repro-next-66918 actively maintained?

Dormant — no commits in 2+ years (last push 2024-06-15).

How hard is repro-next-66918 to set up?

Setup difficulty is rated easy, with roughly 5min to a first successful run.

Who is repro-next-66918 for?

Mainly developer.

peek the repo → explain another one

This repo across BitVibe Labs

double-check against the repo, no cap.