The Absolute Best JS Dev Tools in 2022
Tags: javascript, webdev, typescript, node
Published: 2022-04-11 19:09:14

> _A breakdown of the most important JS dev tools in 2022, including their most relevant tradeoffs, and some opinionated advice sprinkled on top._

In the world of software engineering, it’s important to have a firm understanding of the tools at your disposal.

But the landscape of JS tooling is always changing at such a rapid pace.

And 2022 is no different.

So I decided to break down the most important dev tools that you should be aware of in 2022.

We’ll start with the lowest-level tools and work our way up to higher-level tools from there. Let’s get started 💪

---

## Compilers

Compilers are responsible for transforming your input code into some target output format. For our purposes, we’re focusing on compilers which support transpiling modern JavaScript and TypeScript into specific versions of ECMAscript that are compatible with browsers and recent versions of Node.js.

![Compilers](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/hxh8kpwbrvd8ksv9u3lp.jpg)

The most important thing to understand about this space is that it’s in the middle of undergoing a massive shift from compilers like [tsc](https://www.typescriptlang.org/docs/handbook/compiler-options.html) and [babel](https://babeljs.io/), which are written in higher-level interpreted languages, to compilers like [swc](https://swc.rs/) and [esbuild](https://esbuild.github.io/), which are written in much faster, compiled languages.

This shift results in **10-100x faster compilation times** as shown in this esbuild demo.
 
![esbuild](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/uq7sevdtveo5orkw9i7j.png)

If you’re updating your devtools stack or starting a new project in 2022, then you’ll want to consider using one of these next-gen compilers under the hood. They may not be as mature as the official typescript compiler or babel, but the benefits of having 100x faster builds cannot be understated.

Note that neither swc nor esbuild perform type checking. They simply transpile code into the desired output format as quickly and efficiently as possible. For the time being, if you’re working with TypeScript, you’ll almost always need to have the official TypeScript compiler as part of your toolchain to guarantee that you’re getting the most out of TypeScript’s static type checking. It’s also worth mentioning that the author of swc, [kdy1dev](https://twitter.com/kdy1dev) is working on [porting tsc to Go](https://kdy1.dev/posts/2022/1/tsc-go) in order to remove the need for tsc in many cases, as it tends to be the bottleneck in most toolchains.

### SWC vs esbuild

`swc` and `esbuild` are both excellent, blazing fast, open source JS / TS compilers. They have [comparable performance](https://datastation.multiprocess.io/blog/2021-11-13-benchmarking-esbuild-swc-typescript-babel.html) and are both used regularly in production by some of the world’s largest companies.

It’s likely that your choice between the two will be dictated more by the higher-level tools built on top of these compilers as opposed to choosing between them directly.

Notable projects using `swc`:

- [Vercel and Next.js](https://nextjs.org/docs/advanced-features/compiler)
- [Deno’s linter, formatter, and docs](https://twitter.com/devongovett/status/1369033422002389000)
- [Parcel](https://parceljs.org)
- [nx](https://github.com/nrwl/nx)

Notable projects using `esbuild`:

- [Vite](https://vitejs.dev)
- [Nuxt.js](https://nuxtjs.org)
- [Remix](https://github.com/remix-run/remix)
- [SvelteKit](https://kit.svelte.dev/)
- [tsup](https://tsup.egoist.sh)


> 💡 In software engineering, convenient statements such as “technology A is better than technology B” rarely hold much value. Rather, you should try to always keep context in mind. In this case, there are many scenarios where you’d be better off using tsc or babel.
> 
> Becoming a better software engineer often boils down to thoroughly understanding the tradeoffs involved with these types of decisions, and balancing those tradeoffs against the particular constraints of your project, team, and business’ needs.

---

## Bundlers

![Webpack](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/0i2ibms7uttftb8j31s3.png)

Bundlers are responsible for taking all of your input source files and bundling them together into an easy-to-consume output format. The two most common use cases for bundlers are bundling libraries and bundling resources for web applications.

![Bundlers](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/sojvz023lfh9izvjahjv.jpg)

Bundlers like `webpack` and `rollup` are the swiss-army knives of modern JS toolchains. They are both extremely extensible, with well-maintained plugins covering major use cases. It’s relatively straightforward, for example, to use any of the popular compilers listed above to transpile TS code with either webpack or rollup.

[Parcel](https://parceljs.org), on the other hand, provides a mostly zero-config approach to bundling. It focuses on simplicity as opposed to extensibility and uses `swc` as a compiler under the hood.

Note that `swc` and `esbuild` both provide basic bundling capabilities as well, though compared with these alternatives, they’re not full-featured enough to be included on this list.

For a much more detailed comparison of these bundlers, check out [tooling.report](https://bundlers.tooling.report/).

---

## Package Managers

[Package managers](https://developer.mozilla.org/en-US/docs/Learn/Tools_and_testing/Understanding_client-side_tools/Package_management) are responsible for managing dependencies in the form of [NPM](https://npmjs.com) packages.

![Package managers](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/woljrw524yqqxox34vh6.jpg)

There’s a [lot of history](https://blog.logrocket.com/javascript-package-managers-compared/) here, but the TL;DR is:

- All of these package managers have similar features and perf nowadays, so don’t be too worried about which one you’re using.
- [pnpm](https://pnpm.io/) seems to be gaining a lot of traction very quickly. 💪
- The way yarn berry was rolled out and the subsequent deprecation of yarn v1 turned a lot of people off from using yarn, though yarn berry has come a long way in the past few years.
- [yarn plug’n’play](https://yarnpkg.com/features/pnp) is an interesting approach, but in practice, it has only seen adoption in cases with very large monorepos.
    - I can’t tell you the number of times I’ve wanted to inspect or add console.log statements to my `node_modules`, and not being able to do so is a real disadvantage.

### Adoption by popular projects
![Package manager adoption](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/2pyo8ma1yc3uymwl53zu.png)
^ A breakdown of the package managers chosen by popular projects. This image is from [Sebastian Weber](https://twitter.com/doppelmutzi)’s excellent [package manager deep dive](https://blog.logrocket.com/javascript-package-managers-compared/). Note that at the time of this writing, none of these projects are using Yarn PnP.

---

## Library Development

These tools are meant to help library authors bundle and publish modern NPM packages.

![Library development tools](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/rc8kuumw8p7zm6emr21w.jpg)

If you’re developing a new library in 2022, you’ll likely want to use one of these higher-level tools to simplify your workflow.

- If you have a TS package and want to take advantage of extremely fast build times courtesy of [esbuild](https://esbuild.github.io/), then [tsup](https://tsup.egoist.sh) is a great option.
- If you have a TS package and need some additional features, then [tsdx](https://tsdx.io) is a great option.
- If you have a TS or JS package, then [microbundle](https://github.com/developit/microbundle) is also a great option.
- [Vite](https://vitejs.dev/) is mainly a tool for building frontend web apps, but it also includes support for [outputting libraries](https://vitejs.dev/guide/build.html#library-mode) and is a very solid all-around option.
- For monorepos, [nx](https://github.com/nrwl/nx) looks really promising.

My personal preference will be to use [tsup](https://tsup.egoist.sh/) for TS packages, mainly because once you’ve experienced 100x faster builds, it’s really difficult to consider switching back to anything else.

### More Info

Most of these tools don’t currently provide great support for TS monorepos which take advantage of [composite project references](https://www.typescriptlang.org/docs/handbook/project-references.html). For the time being, my recommendation for this case is to use `tsc` for type checking and generating `.d.ts` typings (with `emitDeclarationOnly: true`) and `tsup` for compiling code in each of the sub-packages. For an example of this approach, check out the [react-notion-x](https://github.com/NotionX/react-notion-x) monorepo (one of my OSS projects).

Publishing modern NPM packages is a nuanced topic that goes well beyond the scope of this article. For more info on ESM, commonjs, dual-package publishing, exports, and more see:

- [What does it take to support Node.js ESM?](https://www.the-guild.dev/blog/support-nodejs-esm)
- Sindresorhus’ notes on [publishing](https://github.com/sindresorhus/meta/discussions/15) and [consuming](https://gist.github.com/sindresorhus/a39789f98801d908bbc7ff3ecc99d99c) ESM packages

---

## Web App Development

These higher-level tools and frameworks are intended to help developers build modern web applications without worrying about all the details.

![Web app development tools and frameworks](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/ie4g9qpckxdwnlvrpu59.jpg)

If you’re developing a new web app in 2022 using [React](https://reactjs.org), then I would highly recommend using [Next.js](https://nextjs.org/). It has the best support, the most active community, and close integration with [Vercel](https://vercel.com/), the world’s leading deployment platform for modern web apps.

[Remix](https://remix.run/blog/remix-vs-next) provides a really compelling alternative to Next.js. It’s from the makers of [react-router](https://github.com/remix-run/react-router), and though it’s relatively new, they’re definitely a framework to keep an eye on.

If you’re developing a new web app using [Vue](https://vuejs.org), then [Nuxt.js](https://nuxtjs.org/) and [Vite](https://vitejs.dev) are both great options.

And last, but certainly not least, if you want something more light-weight, then give [Parcel](https://parceljs.org) a try. 🤗


> 💡 There seems to be a roughly equal number of projects building on top of `swc` and `esbuild`. The same observation goes for `webpack` and `rollup`.

---

## Conclusion

Modern web development has evolved significantly over the past 10 years. Developers today are lucky to have such a wide range of amazing, well-maintained tools to choose from.

This is, however, by no means a comprehensive list of dev tools. If there’s something missing that you’d like to see added, let me know on [twitter](https://twitter.com/transitive_bs).

Hopefully this breakdown has helped you parse the most important aspects of the current JS / TS dev tools landscape, and hopefully it’ll help you to make more informed decisions going forwards.

---

If you found this article helpful, then consider following me on twitter for more [@transitive_bs](https://twitter.com/transitive_bs)