Next.js Discord

Discord Forum

the module factory is not available. It might have been deleted in an HMR update

Unanswered
Jersey Wooly posted this in #help-forum
Open in Discord
Jersey WoolyOP
I'm getting intermittent errors possibly due to turbo +clerkjs +sentryjs +app router, and I'm wondering if anyone else has seen the issue before and can point me either to a fix, or a bug report because I can't seem to find one. Sometimes when I save a file and there's a HMR I get the following error, which only seems to be cleared if I restart the dev server:
Module [project]/node_modules/next/dist/esm/client/components/error-boundary.js [app-ssr] (ecmascript) 
    was instantiated because it was required from module [project]/node_modules/next/dist/esm/build/templates/app-page.js?page=/(admin)/admin/invitations/page { 
      COMPONENT_0 => "[project]/app/layout.tsx [app-rsc] (ecmascript, Next.js server component)", 
      COMPONENT_1 => "[project]/node_modules/next/dist/client/components/not-found-error.js [app-rsc] (ecmascript, Next.js server component)", 
      COMPONENT_2 => "[project]/app/(admin)/layout.tsx [app-rsc] (ecmascript, Next.js server component)", 
      COMPONENT_3 => "[project]/node_modules/next/dist/client/components/not-found-error.js [app-rsc] (ecmascript, Next.js server component)", 
      COMPONENT_4 => "[project]/app/(admin)/admin/invitations/page.tsx [app-rsc] (ecmascript, Next.js server component)" 
    } [app-rsc] (ecmascript) <locals>, but the module factory is not available. It might have been deleted in an HMR update.


full traceback at https://pastebin.com/dLHj0qvf

6 Replies

Jersey WoolyOP
bump: I also can reproduce this on next@rc and next@canary, and it seems to be limited to using the --turbo flag as I can't reproduce it when not using turbo
Acacia-ants
This is happening to me too 🤦‍♂️ Did you make any progress in the last few weeks?
Masai Lion
Hi!
We're having the exact same error with --turbo. Did you manage to solve it or identify the root cause?
Jersey WoolyOP
No I haven't. I'm reluctantly putting up with the slower dev experience. I think when I was looking into it, I suspected it might be clerkjs having a vendored version of react or next that was not the same version that I was using, but I wasn't able to verify that to be true.
Maine Coon
Same here
American
Getting this in 15.1.7