rslint VS esbuild

Author here. A few other Rust projects to note that I didn't mention in the original post I've since found:

- Boa (JS engine in Rust) – https://github.com/boa-dev/boa

- RSLint (JS/TS linter in Rust) – https://github.com/rslint/rslint

- Node version manager in Rust – https://github.com/Schniz/fnm

If you know of any other popular ones, let me know. I'm keeping a list :)

[4]: https://github.com/rslint/rslint

This reminded of ESBuild. The author started writing it in both Rust and Go, and one of the reasons he chose Go is because it does the cleanup in another thread:

First of all, let's start with what Vite does. Vite is responsible for building a development environment and building a production environment. The development environment is built using esbuild, which is developed in Go language(Go is very fast) On the other hand, the build command for the production environment uses Rollup. The reason why the tools used for building the development environment and the build command for the production environment are different is that although esbuild is super fast, some important functions required for bundling applications are still under development, so Rollup, which is the best solution at this point, is used. (See: https://vitejs.dev/guide/why.html#the-problems)

I also wanted to mention a couple other projects semi-related to this discussion: - swc is a typescript compiler written in rust - esbuild is a typescript compiler written in golang

Documentation page - https://esbuild.github.io/

Github repo - https://github.com/evanw/esbuild

Don't lie. Use the .ts etc extensions and use something like esbuild in a loader you write yourself, or an off-the-shelf loader like ts-node/esm to transpile the output. On top of being correct, this is also significantly more performant. This is Node.js’s recommended approach.

HMR doesn’t exist in esbuild: https://github.com/evanw/esbuild/issues/464

ESbuild