The long-awaited 2.0 Spartacus release is finally out. Read on to find out what it offers and why it is a very significant release.
Angular 9.0 was released on 6 February 2020. The Spartacus team promised to chase it and now, after four months, Spartacus 2.0 is out with all the benefits of Angular 9. What are these benefits? I encourage you to watch my colleague Stanisław Stanisławski explaining this:
This release is not spectacular in terms of new features; however, it is a breakthrough because it proves how the ecosystem works. In one of my previous posts, I wrote that Spartacus is meant to be upgradable, and this is the first major release to which we can actually upgrade and prove that statement. I think that the upgradability promise is met thanks to the Schematics, which automate part of the upgrade process and guide you through the rest. Core team members presented how it works during the last Sparta-Town online meeting. The recording should appear shortly on the Spartacus Project YouTube channel.
Besides refactoring and architectural updates the release also includes features like:
- Accessibility Keyboarding features
- This enables navigation throughout the site using a keyboard only
- Lazy loading of CMS components
- This gives a great performance optimization opportunity via loading components only when they are needed
- Event service
- It is an interesting concept that aims to simplify the events management in Spartacus. It might be used along with Google Tag manager for collecting analytics data. It also helps to decouple components without the need to mess with NgRx. For more information, watch the video by my colleague, Krzysztof Platis, working on Spartacus core
- State persistence
- A new way to persist state in localSotrage or sessionStorage. It is more sophisticated than the previous one (storageSync) but it gives you more control
- Custom Angular URL matching
- This is a routing module extension for managing more sophisticated URLs. You can find a video on that one here
As you can see, these are no user-facing features (besides accessibility keyboarding). However, the architectural changes enabled the team to speed up with the development of such features. For instance, in July we should see the first B2B features released.
At Divante, we have been using 2.0 pre-releases for some time already while implementing new projects. I’ve also provided my training sessions using it. We haven’t found any issues so far. Upgrading to 2.0 should be easy but if you hit any trouble, feel free to contact us. We’d be glad to help you out ;)