-
-
Notifications
You must be signed in to change notification settings - Fork 670
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
Very slow tsserver #3945
Comments
It's super slow for me too, sveltekit + hono monorepo |
This may be related to #3869 |
This is a known issue and difficult to resolve immediately, but we should do it. Can you share a small project to reproduce it, if possible? I can investigate it. |
@yusukebe This is the project I am currently working on https://github.com/Malin88/next-hono it's quite small for now, but in hono there are 6 routes added. With one everything works +- ok, but when I add more then TS has problems. |
@Malin88 Thanks. I'll take a look. |
This related to #3869 |
I tried to use your code for a while. I think the routes to passing the https://hono.dev/docs/guides/rpc#compile-your-code-before-using-it-recommended The completion performance will be improved: code.mp4This is a big problem with our RPC feature. We can discuss it at #3869. |
I have a monorepo with two applications, the first one is a honoJS API and the second one is a nextJS application.
If I add a reference to hono in tsconfig.json to use RPC and have nice typing in the nextJS application, tsserver needs 5-10 seconds to check for errors with each change.
Based on the tsserver logs, the most time is spent on "semanticDiag". Has anyone encountered this problem?
my nextJS tsconfig.json:
and for hono:
The text was updated successfully, but these errors were encountered: