Deno: Supports TypeScript while also browser compatible?
"Supports TypeScript out of the box."
and
"Aims to be browser compatible."
seem mutually exclusive, or am I missing something? How can deno support TypeScript out of the box, but also be browser compatible? Or is the compatibility in one direction (i.e. it supports everything the browser does but not the other way 'round)?
It might be worth clarifying this in the docs maybe?
davidbarratt
All 3 comments
Browser compatible means that where we overlap in functionality with the browser, EG fetch() that we use the browser APIs. There are many things you can do in deno that will not run in the web browser - typescript is one of them - starting a TCP server is another. But if you use javascript and don't import the built-in "deno" module, the script should be browser compatible.
ry
on 18 Jan 2019
Thanks for the clarification!
davidbarratt
on 18 Jan 2019
@davidbarratt There are projects like:
that allow you to use TS directly in <script> tags in the browser.
(Not that it's efficient but it's possible.)
rsp
on 18 Nov 2019
Related issues
ry
路
3Comments
ry
路
3Comments
JosephAkayesi
路
3Comments
benjamingr
路
3Comments
kitsonk
路
3Comments
Most helpful comment
Browser compatible means that where we overlap in functionality with the browser, EG
fetch()that we use the browser APIs. There are many things you can do in deno that will not run in the web browser - typescript is one of them - starting a TCP server is another. But if you use javascript and don't import the built-in "deno" module, the script should be browser compatible.