Next.js projects experience errors with module loading

“Link to the code that reproduces this issue https://github.com/robcaldecott/iframe nextjs To Reproduce Clone the repo and first build the app that will be hosted in an iframe (this part is build using Vite but that does not matter). This will start a little app on http://localhost:5173. Leave this running. Now, in a separate shell, run the NextJS app that exhibits the issue: Open http://localhost:3000 in your browser, and open the DevTools so you can see the console. Refresh the page and note th”

“Link to the code that reproduces this issue https://github.com/Janpot/next worker threads repro To Reproduce 1. Clone https://github.com/Janpot/next worker threads repro 1. Run pnpm install 1. Run pnpm build The Next.js config combines custom webpack with experimental.workerThreads . Current vs. Expected behavior It currently throws an error: Provide environment information Which area(s) are affected? (Select all that apply) Output (export/standalone) Which stage(s) are affected? (Select all tha”

“Link to the code that reproduces this issue https://github.com/jdoe802/pino pretty mongo minimal To Reproduce have been working on this for a few weeks now. I was getting errors like the following when trying to implement pino transport this originally seemed to be fixed with the following workaround being added to the next.config file: (the worker.js file, indexes file, and wait file were all copied from /node modules/thread stream/ folder) however after further inspection some logs were output”

“Link to the code that reproduces this issue https://github.com/hamlim/next mdx remote jsx runtime bug To Reproduce 1. Clone the repo 2. Install dependencies via bun install 3. cd apps/docs 4. Run bun run dev 5. visit http://localhost:3000/ 6. See the error Current vs. Expected behavior I see the following error: Ideally I wouldn't get any error! Provide environment information Which area(s) are affected? (Select all that apply) Runtime Which stage(s) are affected? (Select all that apply) next de”

“Link to the code that reproduces this issue https://codesandbox.io/p/devbox/stupefied visvesvaraya 64xkvr To Reproduce use "next": "^14.2.4" create pages/api handler make request in middleware using await fetch(${req.nextUrl.origin}/api/${handlerName} Current vs. Expected behavior Current behaviour: fetch throws error when deployed: { library: 'SSL routines', reason: 'wrong version number', code: 'ERR SSL WRONG VERSION NUMBER' } Expected behaviour: fetch makes requests successfully (as it was in”

“Link to the code that reproduces this issue https://codesandbox.io/p/devbox/hardcore keller xt5l7m?file=/app/TestImage.tsx:18,29 To Reproduce 1. Start the application 2. Reduce network speed to "Fast 3G" to better see the problem (but it's visible in not throttled, too). 3. Observe how the red background disappears when the image is loaded, but the image remains transparent for actually longer than the red background shows before the image goes fully opaque. Current vs. Expected behavior I expec”

“Link to the code that reproduces this issue https://github.com/gsaint12/afiaweb To Reproduce 1: Install latest app 2: Run dev 3: App crashes with error Current vs. Expected behavior It is expecte that the app runs the default template after installation but what happens is that it runs and then crashes with some errors, there are multiple modules with names that only differ in casing for default modules. affected modules: \node modules\next\dist\compiled\@next\react refresh utils\dist\loader.js”

“Link to the code that reproduces this issue https://codesandbox.io/p/devbox/hungry nova ssjf9r To Reproduce 1. Compile an application using NextRoute + app routing as export: 'static' 2. Access the site Current vs. Expected behavior .txt artifacts are created for what it seems to be a prefetching strategy and these files names are un versioned (or un hashed) into the root where the page can be found. Because of this, these files can't be cached or otherwise an update on the overall site will res”

“Link to the code that reproduces this issue https://github.com/fjrsaracho/investigate next 14 loop To Reproduce 1. Start application with yarn dev 2. Open website ( http://localhost:3000 ) Current vs. Expected behavior Current Once you open website it starts to loop refresh when it tries to load HMR. @investigate next 14 loop/gateway:dev: ⚠ Fast Refresh had to perform a full reload. Read more: https://nextjs.org/docs/messages/fast refresh reload I've generated a branch named as "next new app rou”

“Link to the code that reproduces this issue https://codesandbox.io/p/devbox/boring wright cf45dc To Reproduce 1. Start the application 2. Observe how the left gif (which has onError set) restarts every second, when there's a rerender due to a state change, while the right gif plays normally. 3. Comment out line 41 onError={() = {}} 4. The left gif no longer restarts every second Current vs. Expected behavior I expect the image to behave the same regardless of whether onError is set or not. Howev”