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:

Wasm 3 Before GTA 6 LogRocket Article

We got Wasm 3.0 before GTA 6: Meet the web’s new engine

Discover how WebAssembly 3.0’s garbage collector, exception handling, and Memory64 transform Wasm into a true mainstream web platform.

Ikeh Akinyemi
Oct 3, 2025 ⋅ 2 min read

How to use AI to build accurate ShadCN components

AI agents often break shadcn/ui components with outdated docs or made-up props. The MCP server fixes this by giving live access to registries. In this tutorial, we’ll set it up and build a Kanban board to show it in action.

Chizaram Ken
Oct 3, 2025 ⋅ 5 min read
Rust Project for Web Services LogRocket Article

The best way to structure Rust web services

Learn how to structure Rust web services with clean architecture, Cargo workspaces, and modular crates for scalable, maintainable backends.

Jude Miracle
Oct 2, 2025 ⋅ 2 min read
andrew evans headshot

A spec-first workflow for building with agentic AI

Andrew Evans gives his take on agentic AI and walks through a step-by-step method to build a spec-first workflow using Claude Code.

Andrew Evans
Oct 1, 2025 ⋅ 18 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