How to trace why various node.js modules were "externalized" leading to large bundle sizes?
So my app does use serverFn and those functions access node.js modules, prisma and jwts, etc and I include those serverFunctions within my various page.tsx routes, but I am careful to not use jwts, prisma, node.js functions within my client side or even just SSR components/route functions.
But even so I see a bunch of node.js stuff being "externalized". See image. Thus I must have made a mistake somewhere. How can I easily trace this to figure out where my mistakes are? Being able to trace this would make it super simple to fix. But with the current error messages I am totally lost.

3 Replies
cloudy-cyan•6mo ago
not sure but I think those messages are false positives
are there any runtime issues?
eastern-cyanOP•6mo ago
There are no run-time issues that I am aware of. So these are just to be expected? That is why I struggled to identify my mistake?
Thanks !
cloudy-cyan•6mo ago
let's see if those are still present once we are migrated off vinxi