Deno is coming

[DefinitelyMaybe]

Howdy!

throwing around ideas here, I was wondering your thoughts on use-of or moving-to Deno.

They're also currently on track to releasing a 1.0. heres a link to the issue

[mainrs]

@DefinitelyMaybe Shouldn't it just be fire-and-forget in the best case? Seems like it's just another runtime (which does natively run Typescript). So as long as the application is written in TS and would compile without errors, deno should be able to run it.

Maybe I'm just missing something here though

[jeanlescure]

I'd suggest adding tests to make sure Deno can run your code. In my experience this makes for much more resilient code as Deno uses very strict and secure standards.

Just to give an example, up to recently one of my libs was importing a JSON file, this is not good practice and sure enough Deno did not like it when I imported the url to the TS file with the mentioned JSON import, and thus I refactored the lib to use a different approach.

Deno + TSLint are a match made in heaven for truly safe and well formatted TypeScript 👌