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:

Using CRDTs To Build Collaborative Rust Web Applications

Using CRDTs to build collaborative Rust web applications

CRDTs, or conflict-free replicated data types, is a concept that underlies applications facing the issue of data replication across a […]

Mario Zupan
Feb 23, 2024 ⋅ 15 min read
Guide to Using TensorFlow in Rust

Guide to using TensorFlow in Rust

We explore the fusion of TensorFlow and Rust, delving into how we can integrate these two technologies to build and train a neural network.

Rosario De Chiara
Feb 22, 2024 ⋅ 8 min read
Using Signaldb With React

Using SignalDB with React: A complete guide

SignalDB enables automatic data synchronization between your components and a local in-memory or persistent database.

Antonello Zanini
Feb 20, 2024 ⋅ 6 min read
Guide To Next Js Layouts And Nested Layouts

A guide to Next.js layouts and nested layouts

Understanding how layouts, nested layouts, and custom layouts work in Next.js is crucial for building complex, user-friendly projects.

Ibadehin Mojeed
Feb 19, 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