Skip to content
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

How much work is required to become a drop in replacement for tsc and the typescript language server? #2

Open
bryanrideshark opened this issue Oct 18, 2022 · 2 comments

Comments

@bryanrideshark
Copy link

I recognize this is out of scope and would require funding. But how much work would you be looking at to get it to tsc dropping drop in status?

Is there a road map for onboarding less experienced contributors? For large typescript projects, the performance of tsc is becoming unsustainable.

@marcj
Copy link
Owner

marcj commented Oct 18, 2022

Becoming a drop-in replacement is not the goal since I don't want to copy the design limitations, bugs, and legacy decisions of tsc.

Is there a road map for onboarding less experienced contributors?

No, not yet

@bryanrideshark
Copy link
Author

bryanrideshark commented Oct 18, 2022

If we were to only target the language server for VS Code, so that type checking errors and default import suggestions would work, is that possible?

For a project with more than 100 projects, it just grinds to a halt. Been trying to find a solution for years. Is this something we can develop using the existing code base you have?

Repository owner deleted a comment from hinell Mar 10, 2024
Repository owner deleted a comment from hinell Mar 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants