eslint-plugin-compat VS deno

eslint-plugin-compat [0] and stylelint-no-unsupported-browser-features [1] can help you know when you're using an unsupported browser feature.

[0] https://github.com/amilajack/eslint-plugin-compat

For now I'm trying to set up [eslint-plugin-compat](https://github.com/amilajack/eslint-plugin-compat) to check it for me, but I'm not sure it works — get 0 errors and 3 polyfills for a test snippet.

Why not just use https://deno.land/

Fast iterating thanks to Deno, for built in Typescript debugging and bundling

I usually look at https://github.com/denoland/deno for the releases.

Or you can see the latest release on GitHub Releases page. https://github.com/denoland/deno/releases

I'd run an API using Deno (https://deno.land), and consume that API with an SSR/SSG site built using Astro (https://astro.build). SCSS for styling, and probably just Vanilla JS (written in Typescript and compiled via Deno) — I increasingly find that unless my site is massively interactive, plain old Vanilla JS is totally sufficient.

First, you would need to obtain the source code for the Deno runtime and its dependencies, which you can find on the Deno GitHub repository (https://github.com/denoland/deno).

Reading Deno source code dependcies to build appear to be Rust and V8. listenTls: https://github.com/denoland/deno/blob/f0c79a676cc36a5e8f6f5af86d93186d41974518/ext/net/01_net.js, https://github.com/denoland/deno/blob/f0c79a676cc36a5e8f6f5af86d93186d41974518/ext/net/02_tls.js.

When you look at the current web ecosystem, you'll see players like Deno, Bun, Qwik all pushing the frontier on performance in their own domain.

Site oficial do Deno, em inglês