We’ve upgraded to the latest version of @plasmicapp/loader-nextjs (^1.0.407), however, we’re still getting the above issue:
Error: Failed to collect configuration for /[locale]/[[...page]]
at <unknown> (/Users/casper/Developer/work/stampix/webshop/node_modules/.pnpm/next@15.0.3_@babel+core@7.26.0_@opentelemetry+api@1.9.0_@playwright+test@1.49.0_react-dom@19._2kx6z4kmkiodnzrs3be42byaru/node_modules/next/dist/build/utils.js:1131:23)
at async Span.traceAsyncFn (/Users/casper/Developer/work/stampix/webshop/node_modules/.pnpm/next@15.0.3_@babel+core@7.26.0_@opentelemetry+api@1.9.0_@playwright+test@1.49.0_react-dom@19._2kx6z4kmkiodnzrs3be42byaru/node_modules/next/dist/trace/trace.js:153:20) {
[cause]: TypeError: Cannot read properties of undefined (reading 'ReactCurrentDispatcher')
at 703 (/Users/casper/Developer/work/stampix/webshop/apps/storefront/.next/server/app/[locale]/(marketing)/[[...page]]/page.js:9:15715)
at t (/Users/casper/Developer/work/stampix/webshop/apps/storefront/.next/server/webpack-runtime.js:1:485)
at 12819 (/Users/casper/Developer/work/stampix/webshop/apps/storefront/.next/server/app/[locale]/(marketing)/[[...page]]/page.js:8:43563)
at t (/Users/casper/Developer/work/stampix/webshop/apps/storefront/.next/server/webpack-runtime.js:1:485)
at 36673 (/Users/casper/Developer/work/stampix/webshop/apps/storefront/.next/server/app/[locale]/(marketing)/[[...page]]/page.js:1:3242)
at Function.t (/Users/casper/Developer/work/stampix/webshop/apps/storefront/.next/server/webpack-runtime.js:1:485)
at async getLayoutOrPageModule (/Users/casper/Developer/work/stampix/webshop/node_modules/.pnpm/next@15.0.3_@babel+core@7.26.0_@opentelemetry+api@1.9.0_@playwright+test@1.49.0_react-dom@19._2kx6z4kmkiodnzrs3be42byaru/node_modules/next/dist/server/lib/app-dir-module.js:37:15)
at async collectAppPageSegments (/Users/casper/Developer/work/stampix/webshop/node_modules/.pnpm/next@15.0.3_@babel+core@7.26.0_@opentelemetry+api@1.9.0_@playwright+test@1.49.0_react-dom@19._2kx6z4kmkiodnzrs3be42byaru/node_modules/next/dist/build/segment-config/app/app-segments.js:50:45)
at async (/Users/casper/Developer/work/stampix/webshop/node_modules/.pnpm/next@15.0.3_@babel+core@7.26.0_@opentelemetry+api@1.9.0_@playwright+test@1.49.0_react-dom@19._2kx6z4kmkiodnzrs3be42byaru/node_modules/next/dist/build/utils.js:1129:28)
}
More specifically, Plasmic is using React’s SECRET_INTERNALS_DO_NOT_USE_OR_YOU_WILL_BE_FIRED?:
Are there any drawbacks to using this experimental solution? We can’t easily switch back to Pages Router at the moment
Edit: seems like this solution won’t work since we’d like to have these pages be static instead of SSR. We don’t have access to searchParams on static pages
The drawbacks are mostly related to UX/DX, limitations of what you can do in Plasmic + RSC and some hacky lines of code to be able to make it work (as you saw, it’s necessary to access some internals of React).
Thanks! I’ve upgraded to .408 and it works with the Pages Router solution in App Router. Will continue using that for now unless you see issues with that performance/compat wise?