Hacker News Reader

That is how I'm using Vue as well, new parts of the system are done Vue SFC style but old legacy parts are refactored to in page components mounted against the dom, eventually the amount of legacy jquery soup will approach a point where I can just transfer those components over a full 'Vue' style approach.

VueJS makes that all very clean and simple compared to everything else I looked at which wants you do to do it "our way or the highway".

View on HN

Exactly, it's awesome because if you eventually refactor the container page or section to a Vue comp, you can include the other child components straight without any further work. They already work as full blown components.

Plus:

- since we're mounting components and using SFC, we can use the "runtime only" build (though I keep the full one when I want to make something quick, because the savings in the minified Vye library were very small)

- it can be a small performance improvement in cases where we want to mount something in response to user input, whereas the template in the html page will be compiled on page load (afaik).

Reply on news.ycombinator.com