I recently evaluated a great Vue.js plugin (for Vue CLI v. 3.*), it is available in GitHub here. It turns out that among other things, the Vue.js ecosystem, (primarily its core libraries), are an excellent choice for building web/chrome extensions where the UI needs to be scalable in terms of future features and functionality. And so this post explores and investigates Vue ecosystem as a solution stack for building complex and maintainable, cross-browser web extensions.

This post is an introduction to Single Page Application (SPA) architecture with emphasis in REST, Microsoft’s Web API framework and Vue.js. The post references a small Todo application (available on GitHub) and also a live demo. It’s a high level look with links to well-written reference articles. Admittedly, it is written from a .NET and MS slant. The hope is to help those familiar with ASP.NET WebForms and MVC become more familiar with (and excited about) SPA. Ideally, it will help you get started on your own SPA proof-of-concept. This article assumes a basic understanding of Visual Studio and MVC concepts; models, views controllers and actions. An intermediate level in JavaScript and jQuery is also assumed.