[GH-ISSUE #237] Only plain objects, and a few built-ins, can be passed to Client Components from Server Components #58

New issue

Open

opened 2026-05-06 12:36:54 +02:00 by BreizhHardware · 2 comments

BreizhHardware commented

2026-05-06 12:36:54 +02:00

Owner

Originally created by @Specy on GitHub (Mar 3, 2026).
Original GitHub issue: https://github.com/cloudflare/vinext/issues/237

Hello, i'm trying to use vinext to replace next 16.1.6, my current next project works without giving me the error, but as soon as i use vinext this issue pops up

Only plain objects, and a few built-ins, can be passed to Client Components from Server Components. Classes or null prototypes are not supported.
  [..., Module, Null, ..., ..., [], 1]
        ^^^^^^
    at resolveErrorDev (C:\Users\specy\Desktop\progetti\discerns\client\node_modules\.vite\deps_ssr\react-server-dom-webpack_client__edge.js:4022:148)
    at processFullBinaryRow (C:\Users\specy\Desktop\progetti\discerns\client\node_modules\.vite\deps_ssr\react-server-dom-webpack_client__edge.js:4813:29)
    at progress (C:\Users\specy\Desktop\progetti\discerns\client\node_modules\.vite\deps_ssr\react-server-dom-webpack_client__edge.js:5009:20)
    at process.processTicksAndRejections (node:internal/process/task_queues:105:5)

I'm aware that i cannot pass Class instances etc to the server-client boundary, but i don't seem to be passing any (as i recall at least). I cannot debug further as the application is quite large and the error does not give any context of what file might be causing it.

Using next 16.1.6 i don't have this error

Originally created by @Specy on GitHub (Mar 3, 2026). Original GitHub issue: https://github.com/cloudflare/vinext/issues/237 Hello, i'm trying to use vinext to replace next 16.1.6, my current next project works without giving me the error, but as soon as i use vinext this issue pops up ```js Only plain objects, and a few built-ins, can be passed to Client Components from Server Components. Classes or null prototypes are not supported. [..., Module, Null, ..., ..., [], 1] ^^^^^^ at resolveErrorDev (C:\Users\specy\Desktop\progetti\discerns\client\node_modules\.vite\deps_ssr\react-server-dom-webpack_client__edge.js:4022:148) at processFullBinaryRow (C:\Users\specy\Desktop\progetti\discerns\client\node_modules\.vite\deps_ssr\react-server-dom-webpack_client__edge.js:4813:29) at progress (C:\Users\specy\Desktop\progetti\discerns\client\node_modules\.vite\deps_ssr\react-server-dom-webpack_client__edge.js:5009:20) at process.processTicksAndRejections (node:internal/process/task_queues:105:5) ``` I'm aware that i cannot pass Class instances etc to the server-client boundary, but i don't seem to be passing any (as i recall at least). I cannot debug further as the application is quite large and the error does not give any context of what file might be causing it. Using next 16.1.6 i don't have this error

BreizhHardware commented

2026-05-06 12:36:55 +02:00

Author

Owner

@Specy commented on GitHub (Mar 7, 2026):

@southpolesteve the PR does not solve the issue, it just makes the error clearer. I still don't know where the error originated from. It would be nice to have a hint of which boundary crossing generated the error

@Specy commented on GitHub (Mar 7, 2026): @southpolesteve the PR does not solve the issue, it just makes the error clearer. I still don't know where the error originated from. It would be nice to have a hint of which boundary crossing generated the error

BreizhHardware commented

2026-05-06 12:36:55 +02:00

Author

Owner

@Specy commented on GitHub (Mar 7, 2026):

For anyone with similar issues, if you are using next-runtime-env, the error seems to be originating from there as when i remove it from the head the error disappears.

@Specy commented on GitHub (Mar 7, 2026): For anyone with similar issues, if you are using [next-runtime-env](https://github.com/expatfile/next-runtime-env), the error seems to be originating from there as when i remove it from the head the error disappears.