Next.js Discord

Discord Forum

Upgrade from 15.0.2 to 15.0.3 broke some runtime stuff in our prod build.

Unanswered
Pink salmon posted this in #help-forum
Open in Discord
Pink salmonOP
I can confirm upgrade to 15.0.3 is the reason for this because manually going back to 15.0.2 fixes the issue.

⨯ TypeError: a is not a constructor
    at t.createPool (/Users/jerico/Code/project1/.next/standalone/.next/server/chunks/8012.js:1:307844)
    at eR (/Users/jerico/Code/project1/.next/standalone/.next/server/chunks/8012.js:28:32353)
    at 731957 (/Users/jerico/Code/project1/.next/standalone/.next/server/chunks/9584.js:1:29610)
    at t (/Users/jerico/Code/project1/.next/standalone/.next/server/webpack-runtime.js:1:485)
    at 857155 (/Users/jerico/Code/project1/.next/standalone/.next/server/chunks/1036.js:26:29835)
    at t (/Users/jerico/Code/project1/.next/standalone/.next/server/webpack-runtime.js:1:485)
    at 347360 (/Users/jerico/Code/project1/.next/standalone/.next/server/app/[domain]/[locale]/(main)/(ordering)/ecards/[id]/page.js:1:22306)
    at Object.t [as require] (/Users/jerico/Code/project1/.next/standalone/.next/server/webpack-runtime.js:1:485)
    at <unknown> (/Users/jerico/Code/project1/.next/standalone/node_modules/next/dist/compiled/next-server/app-page.runtime.prod.js:127:1282) {
  digest: '1997576513'
}

4 Replies

Pink salmonOP
It happens on all server actions
Pink salmonOP
Anyone have any idea what might be the issue here? A minor update should not cause any issues, but I can confirm that 15.0.2 works properly while 15.0.3 doesn't work, so the minor update is the cause. However, there is no helpful error message to debug it.
Asian black bear
Chances are this is better suited for a GitHub issue report as it's a possible regression. If you can share a minimal reproduction with the team it'd surely help the team a lot to look into it.
Pink salmonOP
Upon looking further, I've found that the cause is the Sentry integration.

Specifically, it is related to a specific option.

  reactComponentAnnotation: {
    enabled: true,
  }