In my job as a consultant, I often code review Vue applications. It is common to me to see views with a lot of business logic and computed values. This isn't necessarily a bad thing, but can incur technical debt.

I've worked with Progressive Web Application plug-ins with several SPA frameworks. Most of them are pretty simple to implement. But when I learned about Vite's plug-in, I was intrigued since that would work across different SPA frameworks.

I've been working on a new Microservice example and I'm writing the client in Vue.js. Due to the nature of the project, I needed to use Nested Routing. I thought this might be a good topic for a Coding Short.

I'm happy to see that instead, they've adopted Pinia as an alternative. I am not in love with Pinia (as I use reactive objects more often) but for complex scenarios it reminds me of something closer to the Composition API.

I went on the WebRush podcast (with John Papa and Dan Whalin (et al.)) and had a discussion about reactive() and ref() in the Composition API that resulted in this video.

I have two new Coding Shorts videos. Theh first is about Angular Template Forms and the latest is about using Vite for production builds.

I've only started to look into Custom Elements (e.g. Web Components) and my trip started with Vue 3.2. They have a new facility to support custom elements created as Vue Components.

When I first started using Vue, I liked the ability to just drop the vue library on a page, and create some simple interactivity. While this still works, most people use Vue for larger, compiled projects.