Skip to content
Note

Still targeting ES6 JavaScript in 2025?

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?

Earns Its Keep

Every Sunday, one post on Dataverse, .NET, and whether the tools we rely on still deserve to be there.