Joel Griffith
Aug 28, 2019 ⋅ 7 min read

You don’t need Babel with Node

Joel Griffith @browserless @elastic It only has to work.

Recent posts:

Build Full-Stack App React Goxygen

Build a full-stack app with React and Goxygen

We show how to use Goxgen to scaffold a full-stack React app. See how to integrate React with Go and modify Goxygen to suit your project requirements.

Clara Ekekenta
Dec 6, 2023 ⋅ 8 min read
Express Js Adoption Guide Overview Examples Alternatives

Express.js adoption guide: Overview, examples, and alternatives

Express.js is a Node.js framework for creating maintainable and fast backend web applications in JavaScript. In the fast-paced world of […]

Antonello Zanini
Dec 6, 2023 ⋅ 17 min read
Nesting web components in vanilla JavaScript

Nesting web components in vanilla JavaScript

Web components are underrated for the performance and ergonomic benefits they provide in vanilla JS. Learn how to nest them in this post.

Mark Conroy
Dec 5, 2023 ⋅ 10 min read
Using Defer In Angular 17 To Implement Lazy Loading

Using defer in Angular 17 to implement lazy loading

Angular’s new defer feature, introduced in Angular 17, can help us optimize the delivery of our apps to end users.

Lewis Cianci
Dec 4, 2023 ⋅ 10 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