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:

daisyUI 5 is here: What’s new and what to expect

Explore daisyUI 5’s new features, performance upgrades, and theming engine built for Tailwind CSS 4 developers.

Ikeh Akinyemi
Aug 25, 2025 â‹… 8 min read
Why Kimi K2 is a frontend game-changer

Agentic AI for 5x less: Why Kimi K2 is a frontend game-changer

Kimi K2 doesn’t just tell you what to write or how to solve a problem; it writes the code, executes the tasks, and gets stuff done.

Chizaram Ken
Aug 22, 2025 â‹… 8 min read
Gemini CLI vs Codex CLI: A Comparative Analysis

Does Gemini CLI fall short? Here’s how Codex compares

Compare Codex CLI vs Gemini CLI for real-world coding tasks. See strengths, weaknesses, and which AI CLI fits your developer workflow best.

Emmanuel John
Aug 20, 2025 â‹… 8 min read
Is Next.js Still Developer-Friendly?

Is Next.js still developer-friendly?

The question isn’t whether Next.js is good or bad; it’s whether the productivity gains are worth the complexity tax.

Chizaram Ken
Aug 20, 2025 â‹… 5 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