Type error

[vafanassieff]

Describe the bug
Using trpc-uwebsockets 11.4.1 with @trpc/server 11.4.3 leads to this error

Type 'Lazy<AnyRouter>' is not assignable to type '{ [lazySymbol]: true; }'.ts(2322)
unstable-core-do-not-import.d-CSxj_rbP.d.cts(806, 3): The expected type comes from property 'router' which is declared here on type 'WebsocketsHandlerOptions<AnyRouter>'

For the router, using the example in the doc.

[romanzy313]

Hi! The readme states that you must ensure versions of trpc-uwebsockets and @trpc/server match. As you can see from the error, this adapter has to import from unstable-core-do-not-import, so even patch changes can break compatibility. I have published 11.4.3 on npm. Give it a try and let me know if it works.

[yovanoc]

I guess there is something deeper than that. even with the same version I got the same error as him.

'LazyLoader<import("/Users/yovanoc/Projects/project/node_modules/.pnpm/@trpc+server@11.4.3_typescript@5.8.3/node_modules/@trpc/server/dist/unstable-core-do-not-import.d-ClFRzVsT").AnyRouter>' is not assignable to type 'LazyLoader<import("/Users/yovanoc/Projects/project/node_modules/.pnpm/@trpc+server@11.4.3_typescript@5.8.3/node_modules/@trpc/server/dist/unstable-core-do-not-import.d-C6mFWtNG").AnyRouter>'.

I don't get why this unstable-core-do-not-import is created 2 times

[romanzy313]

I was able to reproduce the issue. You can find the example repo here. This issue only happens when using react... Running with vite works just fine, but building with tsc creates these issues...

[romanzy313]

This seems to be the issue in trpc for versions 11.4.0+.

[yovanoc]

oh you right im building with tsc in a monorepo

[romanzy313]

I could not build with tsc; however, vite seems to work. The issue was introduced in version 11.4.0, something changed in the build of trpc. The issue you are having is that the client imports trpc module (.mjs), while the server imports commonjs (.cjs).

Also, make sure that the same options are used in tsconfig.json for frontend and backend. However, since we are using the JavaScript ecosystem, changing the config in one place breaks something else :)

If you find any success, please post it here. For now, I suggest rolling back to 11.3.1

[yovanoc]

seems fixed in this PR: trpc/trpc#6879, and publish in v11.4.4

[romanzy313]

I have tested 11.4.4 when it came out and it made no difference. Please try 11.5.0 and let me know