— 3 min readEdit post on GitHub
Magento PWA Studio uses a Monorepo structure. For those reasons, after checkout, we already see ten subfolders. They packages are most likely unrelated, loosely connected, or connected. To give an example, venia-ui needs elements from peregrine. Let's take a look at which components we have in the current state.
Main Libraries If we start our a PWA-Project, we mostly change components from these two libraries to have our own PWA theme.
Elements for building
Currently, the PWA Studio offers a small collection of tools and components. For me, it is a library that allows building a custom PWA Theme for Magento.
PWA Studio 5.0.1 is a patch release to fix an Image loading issue. Also, a security fix prevents invalid mutation caching.
fetchPolicy: 'no-cache' it is possible to define mutation the should not be added to Apollo query cache.
For more Information see:
Although the project is still in an early stage of development, the PWA Studio already offers a toolkit for creating a PWA theme. Due to the lack of extension points and multilingualism, you will have to write many React extensions yourself, which can make large projects very complicated and expensive. With build things from scratch, it is possible to ignore legacy problems and create new great ideas. On the other hand, it takes a long time to get a stable software anyway with a production-ready feature set. From my point of view, it is good to now with a small project to gather experience with the new PWA Studio even there are already a few bigger projects live.