Some time ago I wrote an article about state management patterns in Vue. You may or may not know but I’ve been working with Composition API intensively for the past few months while building a new version of Vue Storefront and I thought it might be a good idea to share some of my learnings. The topic I found really interesting is how using Composition API has changed the way I’m managing my application state - both local and global. If you’re curious how different it is from the current mainstream approaches make yourself a coffee and feed your curiosity because today I will share with you how to use Composition API as a replacement for known state management patterns and libraries 🙂
What is Gridsome?
Gridsome is an open source VueJS framework used for building static generated sites. The main focus of Gridsome is that the final website will always be fast, really fast. This is achieved by adding performant features such as code splitting, asset optimization, progressive images, and link prefetching by default. With a Gridsome website you’ll get almost perfect page speed scores which is very important for SEO purposes and user experience nowadays.
Yesterday Evan You, the creator of Vue.js, announced the first beta version of Vue 3.
Vue 3 comes with great performance improvements and focuses on making developing enterprise applications even smoother and faster. Additionally, it introduces new components and developer-experience focused changes, to delight Vue.js developers of any kind.
In early 2020, there is a lot of discussion and anticipation for Vue 3. Thus I wanted to help the community prepare for the next version of our beloved framework.
Vue 3 brings in a lot of exciting features and changes. By the time of writing, Vue 3 is in alpha version and we expect a beta soon!
I gave a talk, "What you'll love in Vue 3", at Vue Amsterdam and VueConf US earlier this year, about the new features I am the most excited about.
Every Vue application has its state but managing it simply and predictably can be hard. There are many approaches to state management in modern front-end development and it’s easy to get lost in all the available patterns and libraries.
In this post I’ll try to go deep into state management patterns and tools as well as the reasoning behind their existence. This article is very in-depth but I guarantee you that there is at least one thing that you will learn from it.
It’s been a while since we published last part of Vue Performance series. I hope you had a chance to apply everything you already learned in your projects and make them faster! If you have read previous articles you already know perfectly how lazy loading works, how to code-split routes and components, and how to manage asynchronous loading in elegant way but we still haven’t covered the aspect that influences bundle size the most - third party libraries. This article is all about them!
While most of the dependencies are available through NPM, many of them also provide a link to a CDN (Content Delivery Network) version so it can be included in any project without additional efforts or build steps.
But there is also a fair amount of popular third-party libraries that don't provide an NPM package and rely fully on being implemented via the script tag. Common examples are newsletter integrations, contact forms, and the Stripe SDK to process payments.
The new version of Vue.js is right around the corner. As of today, Vue 3 is in pre-alpha version and the source code is available on GitHub, under the vue-next branch.
There's been a lot of fuss about the new version of Vue.js, and specifically about the new Composition API. If you have never heard of it, you can take a look at the slides from my talk, Vue 3 and the Composition API, that I presented at Vue Toronto recently. (video of the presentation is coming soon!)