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.

Automated Accessibility Tests with sa11y

Accessibility in today’s world is a must! Thus, in the past weeks I’ve spent some time implementing automated tests that check for accessibility issues in Sample Gallery apps. To check for accessibility issues I’ve used sa11y, a set of open source JavaScript libraries that detects machine knowable accessibility issues and that can be used with Jest, WebdriverIO or just generic JavaScript.

Continue reading “Automated Accessibility Tests with sa11y”

Blog at

Up ↑