I am now working on a project with http-vue-loader and Python jinja2 template for SSR reason. (I just quit NUXT, it is painful and inefficient.)
And I expected some difficulties but there isn’t amazingly. I use even vue-router for micro SPAs using http-vue-loader to build member pages or something that needn’t SSR.
(Micro SPA means relatively small scoped SPA for a part of your web services that not required SEO or authenticated user only area. You can have multiple MSPAs for your project, and it is also supported by vue-cli).
I think it is your one of reasons for under-rating your great project. But SFC is not just template but fully functional stand-alone component including style, script and template.
I am as a mainly backend developer on current project. And I work with traditional server side template but I can minimize server side rendering (just focus to SEO), and my coworker, frontend developer can maximize client side rendering (fully focus to UI AND UX) via http-vue-loader.
If it needn't to SSR, backend just routes to micro SPA, and frontend can have all charge for his app including sub routing.
And we can use session for authorization not like JWT token, and it makes our project more simpler. Client needn’t handle authorization any more. (But backend should still have capability for token authorization for native mobile apps or something doesn’t support http cookie).
I am not a good frontend developer and I am not sure it is good, but current my work is based on my template: https://gitlab.com/hansroh/http-sfc - but it is just alpha version and unstable.
hansroh
commented
4 years ago
I am now working on a project with http-vue-loader and Python jinja2 template for SSR reason. (I just quit NUXT, it is painful and inefficient.)
And I expected some difficulties but there isn’t amazingly. I use even vue-router for micro SPAs using http-vue-loader to build member pages or something that needn’t SSR.
(Micro SPA means relatively small scoped SPA for a part of your web services that not required SEO or authenticated user only area. You can have multiple MSPAs for your project, and it is also supported by vue-cli).
You recommend to use http-vue-loader for testing purpose only and linked to https://vuejs.org/2015/10/28/why-no-template-url/ .
I think it is your one of reasons for under-rating your great project. But SFC is not just template but fully functional stand-alone component including style, script and template.
I am as a mainly backend developer on current project. And I work with traditional server side template but I can minimize server side rendering (just focus to SEO), and my coworker, frontend developer can maximize client side rendering (fully focus to UI AND UX) via http-vue-loader.
If it needn't to SSR, backend just routes to micro SPA, and frontend can have all charge for his app including sub routing.
And we can use session for authorization not like JWT token, and it makes our project more simpler. Client needn’t handle authorization any more. (But backend should still have capability for token authorization for native mobile apps or something doesn’t support http cookie).
I have even found that performance is reasonable: https://www.reddit.com/r/vuejs/comments/c9r7gy/opinions_on_httpvueloaderjs_for_buildless_vuejs/ . Also I believe performance will be improved using PWA and http cache control.
I am not a good frontend developer and I am not sure it is good, but current my work is based on my template: https://gitlab.com/hansroh/http-sfc - but it is just alpha version and unstable.
Welcome anyone’s feedback.