Comments (2)
We cannot easily recreate the issue with the provided information. Please add a minimal reproduction in order for us to be able to help more efficiently.
Why was this issue marked with the please simplify reproduction
label?
There was a reproduction provided, but due to its complexity, we cannot easily reproduce the issue.
An ideal minimal reproduction (unless relevant):
- is not part of a monorepo
- does not require secrets to run
- does not reference private registry dependencies
- has as few dependencies as possible
- excludes unrelated pages/routes
- does not require a database/third-party service to run
- only includes the code necessary to reproduce the issue
- is tested against
next@canary
to make sure your issue has not already been fixed
In general, assume that we should not go through a lengthy onboarding process at your company code only to be able to verify an issue.
If you cannot create a clean reproduction, another way you can help the maintainers' job is to pinpoint the canary
version of next
that introduced the issue. Check out our releases, and try to find the first canary
release that introduced the issue. This will help us narrow down the scope of the issue, and possibly point to the PR/code change that introduced it. You can install a specific version of next
by running npm install next@<version>
.
What happens if I don't provide a sufficient minimal reproduction?
Issues with the please simplify reproduction
label that receive no meaningful activity (e.g. new comments with a simplified reproduction link) are automatically closed and locked after 30 days.
If your issue has not been resolved in that time and it has been closed/locked, please open a new issue with the required reproduction.
I did not open this issue, but it is relevant to me, what can I do to help?
Anyone experiencing the same issue is welcome to provide a minimal reproduction following the above steps.
I think my reproduction is good enough, why aren't you looking into it quicker?
We look into every Next.js issue and constantly monitor open issues for new comments.
However, sometimes we might miss one or two due to the popularity/high traffic of the repository. We apologize, and kindly ask you to refrain from tagging core maintainers, as that will usually not result in increased priority.
Providing a minimal reproduction from the start without asking helps us look into issues much more quickly, as we can easily verify if the reported bug is related to Next.js. That said, every issue is important to us, and if an issue gets closed by accident, we encourage you to open a new one linking to the old issue and we will look into it.
Useful Resources
- How to Contribute to Open Source (Next.js)
- How to create a Minimal, Complete, and Verifiable example
- Reporting a Next.js bug
- Next.js Triaging issues
from next.js.
Hi @ztanner I've updated description. I've added new, clean repository and link to staging env of that repository and information about one thing I noticed in the network tab.
from next.js.
Related Issues (20)
- bug: Next has been hot updated continuously since it started HOT 4
- Unsupported Node.js version! Your version: undefined HOT 2
- SWR and @here/maps-api-for-javascript prod build HOT 2
- Debugging with NODE_OPTIONS='--inspect=0.0.0.0' return error: /usr/bin/node: must be 0 or in range 1024 to 65535.
- CSS pseudo-class `:is` is not compiled correctly in dev mode on 14.2 using turbopack HOT 2
- Docs: Broken link in Docs Contribution Guide HOT 1
- Bug with server action redirect with layout using suspense HOT 1
- Server action redirect does not show content as it streams in if layout uses suspense HOT 1
- provide you with the best experience possible HOT 1
- `useEffect` no longer run twice in React strict mode HOT 2
- Unable to import exports from client component files in non-component files
- with just the click of a button, giving HOT 1
- 100% WORKING***The Ultimate V Bucks Codes Generator 2024-2025: A Complete Review HOT 1
- Dependency Resolution Issue when Installing Shadcn in Next.js 15 HOT 1
- [Local Build] API routes that use `revalidate`cannot be revalidated
- Next.js uses <script> tag to load css files in static export HOT 5
- When a page and layout exist, the page does not rise to the top unless the view height value of the page is greater than 100. HOT 2
- Error on npm run dev after updating to Next.js 15 RC: "Failed to patch lockfile" HOT 1
- TypeError: value.forEach is not a function when use server action on local HOT 1
- app/sitemap.ts is not served at /sitemap.xml on NextJS 15RC HOT 2
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from next.js.