tRPC or Hono RPC - Can't import types from Deno folder (server) to Node folder (client)

[ds315]

Describe the bug

Can't import types from Deno folder (server) to Node folder (client).

To Reproduce

1. I made Deno + Hono server, export type of router from server and enable Deno Language Server for whole project (client and server). Types successfully import's in client, but alot of errors appears.
   
   
   
   

2. I enable Deno Language Server only for server folder. Types to router disappear's in client folder.
   
   

3. I tried to put import to separate file and enable Deno Language Server to it. It doesn't helps.
   
   
   

Expected behavior

Is that possible to Deno Language Server can work with Node projects ?

When enable Deno Language Server, it disables VS Codes Language Server. (it's clear)

As I understand, it's like - [Feature Request] Support multiple types of projects in the same repository #488 in Q4 roadmap ?

Versions

vscode: 1.87.0, deno: 1.40.5, extension: 3.33.3

[nayeemrmn]

Try removing deno.enablePaths and having a top-level deno.json with the following:

{
  "compilerOptions": {
    "target": "esnext",
    "lib": ["dom", "dom.iterable", "dom.asynciterable", "deno.ns"]
  }
}

[ds315]

Thank's much ! But now i have a problem:

How to solve it ?

[nayeemrmn]

Try adding the following to your deno.json and then restarting the language server:

"unstable": ["byonm"]

[ds315]

Doesn't helps

Situation same as before, - some types are 'any' - Hono<any, any, any> and deno-ts(2344)

I can publish test projects (Hono RPC and tRPC), if it helps

[nayeemrmn]

@ds315 You'll have to push to a repo or create a smaller reproduction that I can pull so I can figure out what's wrong.

[ds315]

I'd published both Hono RPC and tRPC - https://github.com/ds315/trpc and https://github.com/ds315/hono

Both works good, only problem with types in Client in VS Code

[nayeemrmn]

I believe this was the same issue as denoland/deno#24293. Ensure the part of your program using hono doesn't include or import any code importing react, and have them in different deno.json scopes. You can now move your deno.json into server/deno.json to achieve this. Closing for now, please update here if this works.