2020-07-16
2175
#babel
David Else
21728
Jul 16, 2020 ⋅ 7 min read

Why you don’t need Babel

David Else TypeScript/JavaScript software developer | elsewebdevelopment.com

Recent posts:

Hooks vs. Signals: The great reactivity convergence explained

React Hooks and SolidJS Signals solve reactivity differently. Learn how each manages state and updates, and when to choose one approach over the other.

Isaac Okoro
Oct 10, 2025 ⋅ 4 min read

Exploring the new Chakra UI MCP Server

Discover how the Chakra UI MCP server integrates AI into your editor, reducing context switching and accelerating development by fetching real-time documentation, component data, and code insights directly in-app.

Emmanuel John
Oct 9, 2025 ⋅ 6 min read
Build AI Agent Without Langchain JS

LangChain.js is overrated; Build your AI agent with a simple fetch call

Skip the LangChain.js overhead: How to build a Retrieval-Augmented Generation (RAG) AI agent from scratch using just the native `fetch()` API.

Ikeh Akinyemi
Oct 9, 2025 ⋅ 3 min read
the replay october 8

The Replay (10/8/25): Data enrichment, CSS is back, TypeScript 5.9

Discover what’s new in The Replay, LogRocket’s newsletter for dev and engineering leaders, in the October 8th issue.

Matt MacCormack
Oct 8, 2025 ⋅ 30 sec read
View all posts

2 Replies to "Why you don’t need Babel"

  1. Nice article, thnx!
    I’d suggest also an option: use TypeScript with target=ES5. It adds a lot of benefits.

  2. Hm, wouldn’t it be better to live-transpile while coding? I mean clone the file into separate folder while working on it via filewatcher or similar.
    I’d personally perefer live-transpiling my code while working on it instead of polyfilling every missing function. e.g.:
    “npx babel –watch src –out-dir . –presets react-app/prod”

Leave a Reply