Reputation: 4267
At this moment, I am getting confused day by day. VueJs 2x was fun, we could use it as a library like react (just plug in and get going, on any existing multi page site) by setting up build tool prior to coding... Assuming we're choosing the build tool route.
Has VueJs3 taken the Angular route of focusing more on building a framework more than a library?
I am asking this question, as I have been trying to research on how to set it(VueJs 3x) up on my existing multi-page app as a library. All tutorials seem to inform about setting up a "Vue app" with build tool (vite) using npm init vue@latest
like one is building a complete SPA app.
My Multi-Page App is build on Asp.Net Core Razor pages, and all pages are Razor based .cshtml
, And npm init vue@latest
assumes one will load the app using the generated index.html
which is not ideal for my case as pages are .cshtml
.
Upvotes: 2
Views: 266
Reputation: 242
You are correct, they are moving towards a framework and you will have to have their CLI to use Vue 3x. You wouldn't be able to use Vue 3x unfortunately on asp.net but you can use Angular.js or Knockout.js (I prefer Angular.js when using asp.net razor pages)
Upvotes: 1