News for hackers. Stuff that matters.
Re:Deno 1.0 by bgdam on Wednesday May 13, 2020 @09:08PM (#23173957)
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.
Re:Deno 1.0 by lioeters on Wednesday May 13, 2020 @10:59PM (#23174790)
Well, 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).

Re:Deno 1.0 by dgellow on Thursday May 14, 2020 @02:50AM (#23176240)
You had 5 minutes startup time?!
Re:Deno 1.0 by z3t4 on Thursday May 14, 2020 @03:46PM (#23184420)
More 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?