Next.js users see errors when building projects
11 posts since Dec 2021, all from GitHub.
“Link to the code that reproduces this issue https://codesandbox.io/p/devbox/determined shaw nz95jm To Reproduce 1. Create a new Next.js application with a custom server, or use yours if you already have one. 2. Try to bundle the server using the following approaches: Standalone…”
“Link to the code that reproduces this issue https://github.com/nategarrow/nextjs third parties issue To Reproduce 1. Fork Repo and Deploy to Vercel 2. Enter a valid GTM ID in app/layout.tsx 3. Attempt to verify on GSC. Personal attempts have failed (See screenshot) image Current…”
“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) No response Link to the code that reproduces this issue or a replay of the bug To…”
Several Next.js users are encountering build and runtime errors, including issues with sourcemaps, TypeScript project references, bundle sizes, server actions, and image resizing. These problems often arise in specific environments or configurations, hindering development and deployment workflows.
SOURCES (11)
“Link to the code that reproduces this issue https://codesandbox.io/p/devbox/determined shaw nz95jm To Reproduce 1. Create a new Next.js application with a custom server, or use yours if you already have one. 2. Try to bundle the server using the following approaches: Standalone Build: While the…”
“Link to the code that reproduces this issue https://github.com/nategarrow/nextjs third parties issue To Reproduce 1. Fork Repo and Deploy to Vercel 2. Enter a valid GTM ID in app/layout.tsx 3. Attempt to verify on GSC. Personal attempts have failed (See screenshot) image Current vs. Expected behavior Current Behavior: Google Search Console verification failed. Note: I noticed that the gtm.js file gets loaded at the end of the <body via next/script with the "afterInteractive" strategy. However, i”
“Link to the code that reproduces this issue https://github.com/remcohaszing/recma nextjs static props/tree/3944549ef8923e91bb3a8ee2542fbc4e67a69e9b To Reproduce 1. Clone the project, checkout the broken commit, and install. 2. Validate the project with TypeScript. 3. Great! That works. Now clean up. 4. Build the project with Next.js. 5. Observe the type error. Current vs. Expected behavior If tsc build works, I expect next build to not throw type errors. The likely culprit is that next build doe”
“Link to the code that reproduces this issue https://github.com/sergiolamorda/nextjs issue revalidatePath multitenant To Reproduce First, add two domains to your local hostname, for example: hen, execute the build and start commands: Next, open two different tabs and navigate to http://test1.local:3000/test and http://test2.local:3000/test respectively. Now, make a POST request to http://localhost:3000/api/revalidate, which will execute revalidatePath('/test2.local/test'). If you reload the previ”
“Link to the code that reproduces this issue https://codesandbox.io/p/devbox/vercel next js reproduction template pages 2cz5ks To Reproduce <img width="950" alt="image" src="https://github.com/vercel/next.js/assets/26209122/aaeb7577 3d4d 485e 9868 c33b83f9e9a1" La propiedad "[INTERNALS]" falta en el tipo "import("/Users/nicolas/Desktop/testing/carvuk monorepo clients/node modules/.pnpm/next@13.4.12 react dom@18.2.0 react@18.2.0/node modules/next/dist/server/web/spec extension/request").NextReques”
“Link to the code that reproduces this issue https://github.com/CJEnright/nextjs source map To Reproduce 1. Start dev server 2. Go to http://localhost:3000/api/test pages 3. Look for logged stack trace in console 4. Stack trace will mention irrelevant lines, for example: (The exception is created on line 4, not line 8) Note that this also occurs in app dir, that same repro has a route demonstrating that: http://localhost:3000/test app Current vs. Expected behavior Currently the line number pointe”
“Link to the code that reproduces this issue https://github.com/carlo salinari/debug nextjs To Reproduce 1. Start the application with npm run dev 2. In vscode, set a breakpoint at line 6 of page.tsx 3. Start a debugging session 4. Refresh page Current vs. Expected behavior Current behaviour: breakpoint goes gray (ignored) debug console say some source maps file are missing (see attachment) dbconsole.txt Expected: hit the breakpoint and let you debug the app Verify canary release [X] I verified t”
“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) No response Link to the code that reproduces this issue or a replay of the bug To Reproduce 1. create a suspended component 2. throw new Error('this component only works on client'); Describe the Bug https://react.dev/reference/react/Suspense providing a fallback for server errors and client only content I w”
“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) No response Link to the code that reproduces this issue or a replay of the bug https://github.com/IoanStoianov/limited virtual memory nextjs/tree/main To Reproduce Clone the limited virtual memory nextjs and follow the Readme Local: 1. Limit the virtual memory of your environment. I tried it on docker image”
“Verify canary release [X] I verified that the issue exists in the latest Next.js canary release Provide environment information MacBook Pro 2021 Apple M1 Max (macOS Ventura 13.2 (22D49)) Operating System: Platform: darwin Arch: arm64 Version: Darwin Kernel Version 22.3.0: Thu Jan 5 20:48:54 PST 2023; root:xnu 8792.81.2 2/RELEASE ARM64 T6000 Binaries: Node: 16.17.0 npm: 8.15.0 Yarn: 1.22.19 pnpm: N/A Relevant packages: next: 13.1.7 canary.6 eslint config next: 13.1.6 react: 18.2.0 react dom: 18.2”
“What version of Next.js are you using? 12.0.4 What version of Node.js are you using? v16.13.0 What browser are you using? Chrome What operating system are you using? macOS How are you deploying your application? none Describe the Bug Hi! After a while searching through nextjs documentation and google I still have trouble configuring sourcemap with stacktraces in typescript. Here is a video, as you can see I can dive into a console.log entry and the sourcemap are used, however with stacktrace thi”