Robert and Chris hop on the show to talk about choices we've had to make around <a href="https://babeljs.io/">Babel</a>. 



Probably the best way to use Babel is to just use the <a href="https://babeljs.io/docs/babel-preset-env">@babel/preset-env</a> plugin so you get modern JavaScript features processed down to a level of browser support you find comfortable. But Babel supports all sorts of plugins, and in our Classic Editor, all you do is select "Babel" from a dropdown menu and that's it. You don't see the config nor can you change it, and that config we use does not use preset env. 



So we're in an interesting position with the 2.0 editor. We want to give new Pens, which do support editable configs, a good modern config, and we want all converted Classic Pens a config that doesn't break anything. There is some ultra-old cruft in that old config, and supporting all of it felt kinda silly. We could support a "legacy" Babel block that does support all of it, but so far, we've decided to just provide a config that handles the vast majority of old stuff, while using the same Babel block that everyone will get on day one. 



We're still in the midst of working on our conversion code an verifying the output of loads of Classic Pens, so we'll see how it goes!



<h2 class="wp-block-heading">Time Jumps</h2>

Podurama

Home

Trending

Personal

Your Podcasts

New Episodes

My Files

Favourite Episodes

Tags (Folders)

Recently Played

Bookmarks

Followed Playlists

415: Babel Choices

CodePen Radio

AI Chapters

AI Insights

Reviews