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:

Decoupling Monoliths Into Microservices With Feature Flags

Decoupling monoliths into microservices with feature flags

Explore how to effectively break down a monolithic application into microservices using feature flags and Flagsmith.

Kayode Adeniyi
Jul 25, 2024 ⋅ 10 min read
Lots of multi-colored blue and purplish rectangles.

Animating dialog and popover elements with CSS @starting-style

Native dialog and popover elements have their own well-defined roles in modern-day frontend web development. Dialog elements are known to […]

Rahul Chhodde
Jul 24, 2024 ⋅ 10 min read
Using Llama Index To Add Personal Data To Large Language Models

Using LlamaIndex to add personal data to LLMs

LlamaIndex provides tools for ingesting, processing, and implementing complex query workflows that combine data access with LLM prompting.

Ukeje Goodness
Jul 23, 2024 ⋅ 5 min read
JavaScript logo on top of violet background

Exploring essential DOM methods for frontend development

Learn four groups of DOM methods and their uses to create responsive and dynamic webpages. A helpful DOM reference table is also included.

Chimezie Innocent
Jul 23, 2024 ⋅ 12 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