Comments (2)
The error most likely stems from api route limits on vercel. Will definitely create a better code example next time.
from next.js.
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.
Related Issues (20)
- The combination of `basePath` and Middleware makes page props empty object in Next.js v14+ HOT 5
- Docs: Update documentation for `redirect` function
- Localization doesn't redirect to fallback when missing locale HOT 1
- Inconsistent CSS resolution order HOT 10
- cancel headers() caching
- Trailing slash appended to home page links when i18 and skipTrailingSlashRedirect - true
- Update to `HotReload` triggers ‘bad `setState()`’ warning when server/client disagree on the initial value of `useSyncExternalStore()` and application throws HOT 1
- Bug reports with repro cases from stackblitz.com should not be auto-closed HOT 1
- Update to `HotReload` triggers ‘bad `setState()`’ warning when server/client disagree on the initial value of `useSyncExternalStore()` and application throws
- The Error balloon/toast overlay is broken in 14.2
- The behaviour of encoded special characters in path params is not consistent between page.tsx and route.ts
- Request is being cached despite passing next: { revalidate: 0 } HOT 5
- Clarification Needed: Using `axes` Property with Variable Fonts in `next/font/google` HOT 1
- Next JS app built using output: 'export' not rendered properly
- This issue has been automatically closed because it received no activity for a month and had no reproduction to investigate. If you think it was closed by accident, please leave a comment. If you are running into a similar issue, please open a new issue with a reproduction. Thank you. HOT 1
- redirects in next config different from version before and produce endless redirect loops HOT 1
- Server component won't re-render when deleting all search params HOT 1
- Server component won't re-render when deleting all search params HOT 1
- Server component won't re-render when deleting all search params HOT 4
- VERCEL_URL doesn't get injected for metadataBase by default (canonical links) 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.