Comments (1)
We could not detect a valid reproduction link. Make sure to follow the bug report template carefully.
Why was this issue closed?
To be able to investigate, we need access to a reproduction to identify what triggered the issue. We need a link to a public GitHub repository (template for App Router, template for Pages Router), but you can also use these templates: CodeSandbox: App Router or CodeSandbox: Pages Router.
The bug template that you filled out has a section called "Link to the code that reproduces this issue", which is where you should provide the link to the reproduction.
- If you did not provide a link or the link you provided is not valid, we will close the issue.
- If you provide a link to a private repository, we will close the issue.
- If you provide a link to a repository but not in the correct section, we will close the issue.
What should I do?
Depending on the reason the issue was closed, you can do the following:
- If you did not provide a link, please open a new issue with a link to a reproduction.
- If you provided a link to a private repository, please open a new issue with a link to a public repository.
- If you provided a link to a repository but not in the correct section, please open a new issue with a link to a reproduction in the correct section.
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.
My repository is private and cannot make it public
In most cases, a private repo will not be a sufficient minimal reproduction, as this codebase might contain a lot of unrelated parts that would make our investigation take longer. Please do not make it public. Instead, create a new repository using the templates above, adding the relevant code to reproduce the issue. Common things to look out for:
- Remove any code that is not related to the issue. (pages, API routes, components, etc.)
- Remove any dependencies that are not related to the issue.
- Remove any third-party service that would require us to sign up for an account to reproduce the issue.
- Remove any environment variables that are not related to the issue.
- Remove private packages that we do not have access to.
- If the issue is not related to a monorepo specifically, try to reproduce the issue without a complex monorepo setup
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 by opening a new issue.
I think my reproduction is good enough, why aren't you looking into it quickly?
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.
Upvoting issues to show your interest will help us prioritize and address them as quickly as possible. 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.
Related Issues (20)
- Not able to add Videos Tag in Sitemap.xml using app router
- Third-party script synchronous loading Hydration problem
- hydrate not finished until the whole content is loaded at Stream SSR mode
- Draft mode cookie no being set on edge runtime
- Image optimizer rejects requests for remote images with _next/image in the URL (v14.2.7)
- ScrollAndFocusHandler incompatibility with AG Grid
- Docs: On Firefox, with dom.enable_performance_observer set to false, https://nextjs.org/ crashes
- Docs: location of cached images is wrong
- Third-party script synchronous loading Hydration problem
- Inconsistent handling of notFound() from server action
- Importing Next.js Link component in Route Handler results in "Could not parse module"
- Critical bug in NextJS v14.2.7 - renders page source code instead of components HOT 1
- Next v14 Double Render HOT 1
- Turbopack: `resourceQuery` from import isn't passed to loaders HOT 1
- Docs: Documentation incorrectly says database calls will opt in to server side rendering by default
- Docs: geolocation is confusing (w/vercel) - why is req.geo only available on middlewere
- Error: headers was called outside a request scope, when using Authjs v5.0.0-beta.19 and next dev --turbo
- Import .ts files in Instrumentation HOT 1
- Duplicate className in deploy-button.tsx causing Tailwind CSS error in with-supabase example
- [SWC] [Webpack] [Tree Shaking] combines exports of modules and constants across pages HOT 1
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.