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:

react 19.2 what is new and what to expect

React 19.2 is here: Activity API, useEffectEvent and more

Discover what’s new in React 19.2, which features long-awaited features like the Activity API and the useEffectEvent Hook.

David Omotayo
Oct 13, 2025 ⋅ 7 min read
ai dev tool power rankings

AI dev tool power rankings & comparison [Oct 2025]

Compare the top AI development tools and models of October September 2025. View updated rankings, feature breakdowns, and find the best fit for you.

Chizaram Ken
Oct 13, 2025 ⋅ 9 min read

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
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