Still targeting ES6 JavaScript in 2025?

by May 21, 2025Shorts

Still targeting ES6 JavaScript in 2025?

That’s like debugging with Notepad. 📝

If you’re building JavaScript for Dynamics 365 CRM and still targeting ES6… You’re skipping the modern tools that make your life way easier.

Here’s why I always target ES2020:

✅ Optional chaining: contact?.email?.address No more caption.

✅ Nullish coalescing: name ?? "Anonymous" Fallbacks that actually make sense.

✅ Promise.allSettled() Let all your async ops finish — even if one explodes 💥

✅ async/await Ditch .then() chains and write async code like a grown-up.

✅ This results in cleaner logic, fewer bugs, readable code. Which means more time for coffee ☕

If Dynamics 365 already forces modern browsers… Why are you still compiling like it’s 2015?

What’s your target? Still ES6? Or have you joined the future?

Remy van Duijkeren

Remy van Duijkeren

The Marketing Developer

I build automation and integrations that remove the annoying stuff—using Power Platform, Dynamics 365 & Azure.

Get My Thoughts on Automation & Development

Join my personal newsletter and get practical insights on building faster, integrating smarter, and removing friction in IT systems — especially on Power Platform and Dynamics 365.

Related

.NET 10: ZIP it. Smarter.

.NET 10: ZIP it. Smarter. Yes, you could already update entries inside ZIP files before... But now you can do it without rewriting the entire...

read more