2019-08-28
1964
#babel#node
Joel Griffith
5106
Aug 28, 2019 â‹… 7 min read

You don’t need Babel with Node

Joel Griffith @browserless @elastic It only has to work.

Recent posts:

Why Go wasn’t the right choice for the TypeScript compiler

Why Go wasn’t the right choice for the TypeScript compiler

The switch to Go may be a pragmatic move in the short term, but it risks alienating the very developers who built the tools that made TypeScript indispensable in the first place.

Muhammed Ali
May 8, 2025 â‹… 4 min read
how and when to use type casting in TypeScript

How and when to use type casting in TypeScript

Discover the basics and advanced use cases of type casting, how and why to use it to fix type mismatches, and gain some clarity on casting vs. assertion.

Paul Akinyemi
May 8, 2025 â‹… 14 min read

How to format dates in JavaScript: Methods, libraries, and best practices

JavaScript date handling can be tough. Here are some native Date API tools and specialized libraries to tackle them with.

Nelson Michael
May 8, 2025 â‹… 8 min read
tailwind typography

How to use the Tailwind Typography plugin

Walk you through how to set up and use the Tailwind Typography plugin, also known as the @tailwindcss/typography or the prose plugin.

David Omotayo
May 7, 2025 â‹… 7 min read
View all posts

4 Replies to "You don’t need Babel with Node"

  1. Module support is no longer experimental!

    I’d love to completely get rid of Babel, but some nice features like optional chaining are still unimplemented in Node.

  2. “If you want to try TypeScript without having to change your entire build pipeline, then Babel can do that as well.”
    Can you please elaborate on this? I don’t see how Babel can be helpful for TypeScript.

Leave a Reply