Vue.js on the server

[thelinuxlich]

Wouldn't be cool to require vue on node.js and use browserify to reuse viewmodels? :)

[yyx990803]

This is definitely something I'm interested in, could also be used for pre-rendering the page on server side for initial speed and SEO. But the way Vue is built assumes the presence of the DOM, so it requires a full DOM simulation in Node like jsdom, which can be quite heavy. I'll probably mess around to see how much work it would be when I have time, but at the moment I'm focusing more on consolidating the core API and plugin spec.

[duckbox]

One of my thoughts on this when this came in up in the roadmap, instead of jsdom being ran on runtime, it would be a task. You would execute the task during dev, compile a manifest object of how the data is intercepted in the DOM and output it as a bootstrap of sorts for the initial load. Obviously this would require a vue plugin to read the manifest contents and bind the data to the pre-rendered markup.

[zhang-ning]

At server side there is no necessary to manpulate dom with a data binding libary , but if you guys are talking and interesting in the prebuild process like what component did , I am one of you. And recently the riverjs wrote by me contains this feature and also data binding , there is a build to make the prebuild process worked , you can see it from my responstery or install riverjs -g from npm.

[yyx990803]

Tested and Vue can work with jsdom to provide a pre-rendered version of the page. However, making Vue being able to pick up an already rendered page seems to require too much internal hassle. It is probably easier to just use a service like prerender.io.

On the other hand - @thelinuxlich 's idea of reusing Components on npm is already feasible, because Component definitions do not have to assume the existence of Vue in most cases.

[jonatansberg]

@yyx990803 How much work would it be to adapt Vue to run without access to a full DOM?

[yyx990803]

@mrlundis Vue's template and compile mechanisms relies on an existing HTML parser and live DOM nodes, so pretty much it requires a half re-write, and I don't think that's feasible at the moment. But as I've tested, it does work with jsdom...

[ChrisCinelli]

"making Vue being able to pick up an already rendered page seems to require too much internal hassle." It is a shame., I really like vue.js and this will make it almost the perfect framework.

[robertleeplummerjr]

I was racking my brain thinking of how would be the best way to achieve prerendering, and @yyx990803 your comment on http://prerender.io ... WHAT A WINNER! In particular their bit on using hashes - found here: https://prerender.io/documentation . And, no I don't work for them, just building a single page app engine ( https://github.com/Enpowi/Enpowi ). I'm curious is combining your lib with a routing engine like http://millermedeiros.github.io/crossroads.js/ ideal in your opinion?

[yyx990803]

@robertleeplummerjr Vue can pair with pretty much any routing lib, it really depends on which routing lib you like the best ;)

[robertleeplummerjr]

*high fives @yyx990803 *
I don't want to brag... but javascript rules.

[Pines-Cheng]

before the SEO problem of the front side render templates is perfect solved,I really think server side render is worth to consider by vuejs.

[fullfs]

@Pines-Cheng Try this https://github.com/ngsru/vue-server