Making the move from Aura to LWC

Making the move from Aura to LWC is an important step that everyone should be doing already. It will bring you a ton on benefits, while the effort is not that big. If you want to do some more reading about this topic, take a look at the following blog post. Bear in mind it’s targeted for an architect’s mindset. If you’re a video person, take a look at the next video – with more detail, more suitable for developers:

ESXX Features in Lightning Web Components

Some weeks ago I decided to talk about modern JavaScript features that you can use in LWC. Usually there’s a lot of confusion around this topic, as people believe that only certain JavaScript features, from versions < ES9 can be used in LWC. But this is not true! You can use features from newer versions as long as your browser supports them. The only caveat is that we don’t transform them to ensure backwards compatibility. But that shouldn’t be a problem if your customers use a modern browser (often the case). I explain everything about this topic in the next videos. Watch the series to understand the guts of LWC compilation and why it’s true what I just said, and also learn about some the most interesting features from ES9 to ES12 that will make your code much more professional! If you prefer some reading, take a look at this blog post on our developer site.

Lightning Web Components Communication

Lightning Web Components is the new programming model that Salesforce released early this year. If you don’t know what it is about, check this post I published some time ago.

One of the keys to learn how Lightning Web Components work is to understand how components can communicate between each other. The communication patterns are different from Aura, and are one of the culprits of Lightning Web Components superb performance.

Continue reading “Lightning Web Components Communication”

Blog at

Up ↑