TypeScript and JSX in Deno

[@arhum1224]

Unbelievable how simplified the workflow is now!

[@Kavya.Naidu.911]

Keep it up!

[@Kavya.Naidu.911]

You are awesome!

[@Kavya.Naidu.911]

Thanks for watching!

[@Kavya.Naidu.911]

I am so happy for you!

[@Kavya.Naidu.911]

I am so happy for you!

[@benjidaniel5595]

Great narration 👌

[@Micha-cc8hf]

is there any benchmark that shows the time results between `deno check` and `tsc --no-emit`?

[@codingraph]

It looks so much easier

[@pokefreak2112]

can we do custom jsx transforms/arbitrary AST transforms or do you still need babel for that?

[@Zmeu213]

Is it possible to use things like `import './styles.css'` with plain deno?

[@deno_land]

Not currently, but when it becomes part of the specification, we will add it.

[@codernerd7076]

That voice sounds so familiar

[@Kabir.Desai.641]

Thank you for watching!

[@xtinctspecies]

Which version of Typescript does it use? How would the codebase keep up with language enhancements in TS?

[@deno_land]

you can see the version of TypeScript used in Deno by running `deno --version`: the most updated version of deno uses typescript 5.6.2: deno --version deno 2.0.3 (stable, release, aarch64-apple-darwin) v8 12.9.202.13-rusty typescript 5.6.2 Deno's version of TypeScript is updated when new TypeScript versions come out.

[@xtinctspecies]

This is awesome!

[@eurochild]

what vscode theme?

[@diegooooperez]

night owl

[@mattjensen3092]

7th viewer

[@Kavya.Naidu.911]

Thank you for watching!

[@daishokomiyama]

man jsx got nothing to do with react

[@pookiepats]

You were lied to

[@hamm8934]

Its giving: react is a library, not a framework