Next.js developers face OPTIONS request stuck in edge runtime
10 posts since Apr 2023, all from GitHub.
“Link to the code that reproduces this issue https://github.com/yuluyi/edge runtime stuck on options To Reproduce Current vs. Expected behavior It should work. Provide environment information Which area(s) are affected? (Select all that apply) Developer Experience, Navigation…”
“Verify canary release [X] I verified that the issue exists in the latest Next.js canary release Provide environment information Which area(s) of Next.js are affected? (leave empty if unsure) Metadata (metadata, generateMetadata, next/head, head.js) Link to the code that…”
Developers using Next.js's edge runtime are encountering issues where OPTIONS requests become stuck, preventing proper functionality and requiring debugging efforts to resolve the problem. This impacts developer experience and navigation within applications.
SOURCES (10)
“Link to the code that reproduces this issue https://github.com/yuluyi/edge runtime stuck on options To Reproduce Current vs. Expected behavior It should work. Provide environment information Which area(s) are affected? (Select all that apply) Developer Experience, Navigation, Pages Router, Parallel & Intercepting Routes, Partial Prerendering (PPR),…”
“Link to the code that reproduces this issue https://github.com/Rajesh Poojari Dmart/nextIssue To Reproduce Step 1 Add the following generateMetadata function in a couple of dynamic page files that are linked to each other using the Link component: Step 2 Suppose you visit from Homepage "/" to some dynamic url "/products/{productName}" using Link component, the above genareteMetadata function adds opengraph and canonical url as "http:localhost:3000/" in head tag of /product/{productName} page, bu”
“Link to the code that reproduces this issue https://github.com/mcintyre94/edge light test To Reproduce 1. Start the application in dev mode ( npm run dev ) 2. Call the API route: curl http://localhost:3000/api 3. Notice in the logs: hello from browser.mjs 4. Change package.json from "@callumtest/edge light test package": "0.0.1", to "@callumtest/edge light test package": "0.0.2", 5. Install updated dependency ( npm install ) 6. Start the application in dev mode ( npm run dev ) 7. Call the API ro”
Link to the code that reproduces this issue https://codesandbox.io/p/devbox/pedantic cherry k8f3cg?workspaceId=92e5b30e 1491 4cd6 9774 f032926ce2c4 To Reproduce 1. Start the application in development mode. 2. Open the myasset/test.txt URL 3. Notice that…
“Link to the code that reproduces this issue https://github.com/Intellyse/next js bug To Reproduce 1. clone project 2. npm install 3. npm run dev 4. open the page and you can see chrome console output: Uncaught SyntaxError: Invalid or unexpected token 5. same minutes you can see error:Uncaught ChunkLoadError: Loading chunk app/layout failed. image Current vs. Expected behavior 1. First time open the page is error but you refresh page is work! 2. I expected is work all the time Provide environment”
“Link to the code that reproduces this issue https://github.com/vercel/next.js/pull/65613/files To Reproduce The tests are already added but not all of them are enabled for webpack as webpack fails to parse them in the acorn parse that webpack does. You can search for TODO: here: https://github.com/vercel/next.js/pull/65613/files Current vs. Expected behavior These features should be supported when using webpack. Provide environment information Which area(s) are affected? (Select all that apply)”
“Link to the code that reproduces this issue https://github.com/hsucherng/nextjs genstaticparams output export issue To Reproduce 1. Run npm run dev . Current vs. Expected behavior Current behaviour: When I try to view http://localhost:3000/en , an error occurs: Error: Page "/[lang]/page" is missing exported function "generateStaticParams()", which is required with "output: export" config . Expected behaviour: I should be able to view http://localhost:3000/en without any errors. Provide environme”
“Verify canary release [X] I verified that the issue exists in the latest Next.js canary release Provide environment information Which area(s) of Next.js are affected? (leave empty if unsure) Metadata (metadata, generateMetadata, next/head, head.js) Link to the code that reproduces this issue or a replay of the bug https://github.com/vercel/next.js/blob/0d46361f8e83ce3607762483b55377a479cd7dbf/packages/next/src/client/head manager.ts L136 L143 To Reproduce This is a logic flaw in the code, not a”
“Verify canary release [X] I verified that the issue exists in the latest Next.js canary release Provide environment information Which area(s) of Next.js are affected? (leave empty if unsure) Data fetching (gS(S)P, getInitialProps) Link to the code that reproduces this issue N/A (no simple way to host replica since only affected via nextApp.render() calls within POST responses To Reproduce Set up a basic custom server to render next pages via a POST request Add a Next page to the pages dir that d”
“Verify canary release [X] I verified that the issue exists in the latest Next.js canary release Provide environment information Which area(s) of Next.js are affected? (leave empty if unsure) AppDir Link to the code that reproduces this issue https://github.com/knenkne/next generate static params bug example To Reproduce 1. Run npm run build 2. Check out console logs (each id is called twice) image Describe the Bug Pages with isr or ssg are rendering twice, lead to poor performance and side effec”