It should now be clear to you that MVW is not a precise architectural pattern, but rather a paradigm in which you have a Model, a View, and a nebulous third component, or more components, depending on how fine-grained you decide to break down your separation of concerns. Everything falling within that gray area is based on what type of application you are building, what architectural components you are comfortable with as a developer, and what frameworks and libraries you are working with.
The complexity of your SPA should always be a factor in what technologies you use to build it. More to the point, you should not go into every project assuming you will always use a certain technology stack or framework. This rule goes for the MEAN stack as well.
Let's take the User Model example from earlier, and the accompanying Handlebars template View, and actually build it out as an SPA, complete with the AJAX request to retrieve the User...