Book Image

Vue.js 2 and Bootstrap 4 Web Development

Book Image

Vue.js 2 and Bootstrap 4 Web Development

Overview of this book

In this book, we will build a full stack web application right from scratch up to its deployment. We will start by building a small introduction application and then proceed to the creation of a fully functional, dynamic responsive web application called ProFitOro. In this application, we will build a Pomodoro timer combined with office workouts. Besides the Pomodoro timer and ProFitOro workouts will enable authentication and collaborative content management. We will explore topics such as Vue reactive data binding, reusable components, routing, and Vuex store along with its state, actions, mutations, and getters. We will create Vue applications using both webpack and Nuxt.js templates while exploring cool hot Nuxt.js features such as code splitting and server-side rendering. We will use Jest to test this application, and we will even revive some trigonometry from our secondary school! While developing the app, you will go through the new grid system of Bootstrap 4 along with Vue.js’ directives. We will connect Vuex store to the Firebase real-time database, data storage, and authentication APIs and use this data later inside the application’s reactive components. Finally, we will quickly deploy our application using the Firebase hosting mechanism.
Table of Contents (19 chapters)
Vue.js 2 and Bootstrap 4 Web Development
Credits
About the Author
Acknowledgments
About the Reviewer
www.PacktPub.com
Customer Feedback
Preface
Index

Code splitting or lazy loading


When we build our application to deploy for production, all the JavaScript is bundled into a unique JavaScript file. It's very handy, because once the browser loads this file, the whole application is already on the client side and no one is worried about loading more things. Of course, this is only valid for SPAs.

Our ProFitOro application (at least at this stage) benefits from such bundling behavior – it's small, it's a single request, everything is in place and we don't need to request anything from the server for any of the JavaScript files.

However, this kind of bundling might have some downsides. I am pretty sure that you have already built or have already seen huge JavaScript applications. There'll always be some point when loading huge bundles will become unbearably slow, especially when we want these apps to run on both desktop and mobile environments.

An obvious solution for this problem would be to split the code in such a way that different chunks...