-
Notifications
You must be signed in to change notification settings - Fork 378
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug?]: with-trpc is breaking - seroval issue #1092
Comments
"type": "module",
"devDependencies": {
"@types/node": "^20.8.10",
"csstype": "3.1.2",
"esbuild": "^0.19.5",
"postcss": "^8.4.31",
"rollup": "^4.2.0",
"solid-start-node": "^0.3.9",
"typescript": "^5.2.2",
"vite": "^4.5.0"
},
"dependencies": {
"@solidjs/meta": "^0.29.1",
"@solidjs/router": "^0.8.3",
"drizzle-orm": "^0.28.6",
"mysql2": "^3.6.3",
"solid-js": "^1.8.5",
"solid-start": "^0.3.9"
},
"engines": {
"node": ">=18"
}
|
any progress? |
this totally stopper |
@OrJDev - do you think this can be solved by updating to mediakit, or is there an issue with seroval still? |
This has killed progress on one of my apps, this should be an urgent issue |
I remade the TRPC example in the new Beta and didn't face this issue. In general though I stopped using Tanstack Query for the example and that might be where the issue lies. Something with how hydration/serialization is working. In setting up for SolidStart's next Beta Phase built on Nitro and Vinxi we are closing all PRs/Issues that will not be merged due to the system changing. If you feel your issue was closed by mistake. Feel free to re-open it after updating/testing against 0.4.x release. Thank you for your patience. See #1139 for more details. |
Duplicates
Latest version
Current behavior 😯
When starting the example, with Node 18, this is the result:
Also note, the example uses an archived solid-trpc package.
Expected behavior 🤔
that the server starts
Steps to reproduce 🕹
Steps:
pnpm i
pnpm run dev
Context 🔦
Might be related to other recent seroval issues:
Your environment 🌎
No response
The text was updated successfully, but these errors were encountered: