4 ms·
Word of warning though - ts-node can be excruciatingly slow. We recently switched a project from using ts-node in our dev environment to compiling with tsc and
by bgdam 6y ago
Word of warning though - ts-node can be excruciatingly slow. We recently switched a project from using ts-node in our dev environment to compiling with tsc and running with node, and shaved around 5 minutes from our startup time.
- lioeters 6y agoWell, that answers something I was wondering about recently. I noticed in a couple of popular TypeScript (+React fullstack) boilerplates, that they were using ts-node to run the server in production. Unlike babel-node, there's no mention in the documentation to avoid using it in production - but I figured there'd be performance impact, since it's transpiling on the fly (I suppose just once per require).
- dgellow 6y agoYou had 5 minutes startup time?!
- z3t4 6y agoMore then one second and people will test their code less often. Five minutes and people start relying on the type-checker. Like with the chicken and egg problem, what came first, the type-checker or the need to have a type checker?