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

Idea: long-lived compiler server that keeps state in-memory, makes subsequent ts-node invocations faster with typechecking #1845

Open
cspotcode opened this issue Jul 22, 2022 · 0 comments
Labels
research Needs design work, investigation, or prototyping. Implementation uncertain.

Comments

@cspotcode
Copy link
Collaborator

I've had this idea kicking around for ts-node to launch its own long-lived server process, then multiple ts-node processes / threads / etc can request transpiled code and diagnostics from it.

For non-typechecking situations, swc is still simpler and faster. But if you really want typechecking and want to launch many ts-node processes, then we can auto-launch this server and connect many ts-node processes to it. So if no code has changed, then your ts-node process can start, log diagnostics, and start running code pretty quickly.

It's a wild idea, might never happen. I've labelled it "research" accordingly.

@cspotcode cspotcode added the research Needs design work, investigation, or prototyping. Implementation uncertain. label Jul 22, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
research Needs design work, investigation, or prototyping. Implementation uncertain.
Projects
None yet
Development

No branches or pull requests

1 participant