new Deno works well with the npm packages that I tested
its been a looooong time coming but this could mark a reason to evaluate switching our backend for real
@brianleroux Real Q: if #Deno interops with #Node.js, what's the main reason to switch?
I'm assuming execution with npm packages enabled, disables the main security features of Deno.
Is the advantage mainly newer #ECMAScript and URL imports? Is there a perf difference?
I'm not opposed, just wanting to understand the main reasons.
@tbeseda @brianleroux say I wanted to swap out Node for Deno and do a comparison, is it really as simple as just getting the latest copy of Deno and switching out the runtime (`deno start` instead of `yarn start`)?
@mcneely the interop is lower level than that; you import node modules from npm by a special prefix and they just work. Or seems so far! But imagine porting a whole build chain thing would be a lot more involved. Big benefit of Deno is not needing third party tooling. Its pretty nice!
@brianleroux I know Deno natively handles TypeScript but does it now handle JSX too?
@brianleroux hey that's great! Apparently it's been longer than I realized since I last checked in on Deno 😅
@mcneely @brianleroux Deno has always supported JSX. There's no built-in Vue or Svelte support, however.