Comments (5)
We cannot recreate the issue with the provided information. Please add a reproduction in order for us to be able to investigate.
Why was this issue marked with the please add a complete reproduction
label?
To be able to investigate, we need access to a reproduction to identify what triggered the issue. We prefer 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.
To make sure the issue is resolved as quickly as possible, please make sure that the reproduction is as minimal as possible. This means that you should remove unnecessary code, files, and dependencies that do not contribute to the issue. Ensure your reproduction does not depend on secrets, 3rd party registries, private dependencies, or any other data that cannot be made public. Avoid a reproduction including a whole monorepo (unless relevant to the issue). The easier it is to reproduce the issue, the quicker we can help.
Please test your reproduction against the latest version of Next.js (next@canary
) to make sure your issue has not already been fixed.
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>
.
I added a link, why was it still marked?
Ensure the link is pointing to a codebase that is accessible (e.g. not a private repository). "example.com", "n/a", "will add later", etc. are not acceptable links -- we need to see a public codebase. See the above section for accepted links.
What happens if I don't provide a sufficient minimal reproduction?
Issues with the please add a complete reproduction
label that receives no meaningful activity (e.g. new comments with a 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. Furthermore, you can upvote the issue using the 👍 reaction on the topmost comment (please do not comment "I have the same issue" without reproduction steps). Then, we can sort issues by votes to prioritize.
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.
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.
Could you make a minimal reproduction? Thanks!
Minimal reproductions should be created from our bug report template with
npx create-next-app -e reproduction-template
and should include only changes that contribute to the issue.
from next.js.
Could you make a minimal reproduction? Thanks!
Minimal reproductions should be created from our bug report template with
npx create-next-app -e reproduction-template
and should include only changes that contribute to the issue.
I tried to reproduce the template but failed to do so
Can you check on this linked issue? #58576
This happens when we build the application on Docker. example aws-amplify
Edited:
Repo Link: https://github.com/saitharunsai/nextjs-test
from next.js.
@saitharunsai the linked repo https://github.com/saitharunsai/nextjs-test seems to have no docker build step added, could you add one to correctly represent your described issue? It seems a bit too complex still for the described issue, but my initial guess is that react-use
here: https://github.com/saitharunsai/nextjs-test/blob/master/src/hooks/use-window-scroll.ts
have this block: https://github.com/streamich/react-use/blob/master/src/useWindowScroll.ts#L13-L14
which might throw off our compilation. WDYT @shuding? Either case, we need a better reproduction to be able to investigate further.
from next.js.
@saitharunsai the linked repo https://github.com/saitharunsai/nextjs-test seems to have no docker build step added, could you add one to correctly represent your described issue? It seems a bit too complex still for the described issue, but my initial guess is that
react-use
here: https://github.com/saitharunsai/nextjs-test/blob/master/src/hooks/use-window-scroll.tshave this block: https://github.com/streamich/react-use/blob/master/src/useWindowScroll.ts#L13-L14
which might throw off our compilation. WDYT @shuding? Either case, we need a better reproduction to be able to investigate further.
I was able to recreate with aws amplify. For reference, I can connect this issue here: #58576.
from next.js.
Related Issues (20)
- ReferenceError: userland is not defined from punicode (deprecated)
- Error connecting to database: Route / needs to bail out of prerendering at this point because it used revalidate: 0.
- Dynamic import in useEffect in client component works during dev but yields incorrect data after static export
- tsconfig generation doesn't recognize ts5.4 improvements HOT 1
- `require-in-the-middle` is resolved to `import-in-the-middle` and crashing with turbopack HOT 3
- ImageError: "url" parameter is valid but upstream response is invalid
- ERR_TOO_MANY_REDIRECTS when change headers and uncheck disable cache HOT 2
- Missing webpack dependency when using output standalone + custom server HOT 4
- Nonce doesn't applied to all scripts using turbopack
- pg does not work on edge runtime HOT 2
- Cannot deploy nextjs-with-supabase HOT 3
- Unable to do server-side `react-dom` rendering inside Next API route HOT 1
- `fetch(Request)` inside the server actions does not send the request body.
- App router: Content flickering with React.createContext and next/dynamic for SSG/SSR HOT 5
- PORT 3000 Already in use HOT 1
- window.history.replaceState causes re-render in any component using useParams even if path parameters haven't changed. HOT 1
- Next.Js 14.1.0 Facing Build Error With Too Many Open Files In export-detail.json HOT 1
- Uncaught TypeError: Cannot read property 'isInputPending' of null HOT 1
- #50377 @Ottapettavan HOT 1
- Image is not processed by nextjs when using large dimensions
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.