Quasar & Quasar CLI v0.17 aka SSR - Developer Preview

Scorpion

@rstoenescu Yeah I know, I’m actually focusing on a Full-stack Template mixing Quasar Framework for Frontend and Rails Backend, but as I just learnt how GraphQL was I’m spending a lot of time on Backend to make something nice so I didn’t get really focused on Quasar these last weeks. I’m however looking at all your commits to understand what’s really done overtime, and this beta made me really smile, it’s really awesome and hope that Quasar Community will be able to give the feedback you need to finish this release :). #RoadTo1.0

goopil

Great work has always. Thank you for your dedication !

amer1616

Really awesome as usual. Thank u very much. Is there future plans to add support for the new project vue native… https://vue-native.io/

rstoenescu

CLI beta.18 has been released. Enhancements and new features. PWA devs will be thrilled by this update as service-worker and manifest.json are now served during development too!

rstoenescu

CLI beta.19 & beta.20 has been released. Fixes and new features: Quasar Meta plugin; new preFetch params (currentRoute & redirect); preFetch() for App.vue too.

rstoenescu

The last beta (beta.21) has been released. New features:

SSR error page when developing and server encounters an error
SSR - dev & prod common code through src-ssr/extension.js

mesqueeb

Hello. Just trying a new build created with Beta.21.
I did:

npm i -g quasar-cli@next
quasar init ~~~~
run through the process, I had to npm i quasar-cli inside the project as well, as this was still on v0.16
quasar dev -m ssr -t ios

Then it says:

Dev mode.......... ssr
 Quasar theme...... ios
 Quasar CLI........ v0.17.0-beta.21
 Quasar Framework.. v0.17.0-beta.15

Question 1:

Is it normal that Quasar Framework beta and CLI beta is a different version?

Question 2:

With the new method of instantiating the vuex Store, it exports a function instead of the actual store. I used to import the store into several places of my app (js helper files etc.) and use it, however, how would I do this with the SSR version?

Question 3:

After building the app with quasar build -m ssr -t ios it didn’t seem to give me a folder that was compatible with static-site host services like Netlify. With Next I just need to do Nuxt generate and it gives me a public folder with an index.ssr.html and I can just drag that folder in Netlify and it’s hosted.

How to best do this with Quasar? The ssr folder in dist has index.js and template.html. Which is my main endpoint?

mesqueeb

To answer my own Question 3:
Quasar SSR only gives actual SSR not a pre-rendered site. Since you can do Nuxt generate and then upload a prerendered site to a static-website host, I thought this must have also been possible with Quasar as well. But this is not the case!

After everything cools down with v0.17 SSR, I’d love a pre-render build method for Quasar! : D as I realised, I need pre-rendered sites for my Netlify host!

Mohammed

@rstoenescu when the v0.17 will be released? just estimated expectations.

Max

@Mohammed the work in finalizing v17 is on full speed and will be be soon, once everything is done and the documentation is up to date.

would expect it next week or the one after that at most.

cheers max

rstoenescu

Released beta.22. At this point we’re ready to roll unless some major issue is detected on this beta.
Cool additions: QTable as grid; Many perf enhancements. Documentation is almost ready too.

mbrandeis

I may have missed a step. I have meta data for open graph and curl returns the html with the data empty, but when loaded in a browser the data gets populated. Which implies Javascript is running on the client to complete the rendering.

The app is getting data from firebase in the created() cycle. I can try putting it somewhere else

mbrandeis

Also, when I make changes to the code the result is always this error. I have to kill the server and restart it

Firebase: Firebase App named ‘[DEFAULT]’ already exists (app/duplicate-app).

mbrandeis

this app/duplciate-app didn’t occur in the previous version

mesqueeb

@rstoenescu I’d love to try out my other apps in the beta build, but wondering about the store:

With the new method of instantiating the vuex Store, it exports a function instead of the actual store. I used to import the store into several places of my app (js helper files etc.) and use it, however, how would I do this with the SSR version?

panstromek

@mesqueeb
Question 1: Yes, they differ. Only Major version should stay the same…
Question 2: I had a problem with that, too. You need to convert it to usage of Quasar plugins - store is injected in them. Once you create store, you can also name-export it, too… But I would try to avoid that, because you would need to do lot of null-checking.

mesqueeb

@panstromek
It’s usually these plugin files that become so long in my case, I extract parts into other JS files, import them on the top of the plugin file.

One solution is to change ALL these imports to functions, and pass the store as param. But not really beautiful imo…

Do you have any other advice for me?

mbrandeis

I think this is what is needed for prefetching data. There is much room for improvement here. Going to have to look at Quasar source to see if it can handle this https://ssr.vuejs.org/guide/data.html#data-store

rstoenescu

@mbrandeis it’s in the initial post… preFetch feature. https://github.com/quasarframework/quasar-framework.org/blob/dev/source/guide/app-prefetch-feature.md

rstoenescu

@mesqueeb

Question 1 --> perfectly normal. Quasar Framework is the core, and the CLI is the toolbox, so separate versions.
Question 2 --> read this as a starting point, to understand why you need a factory function for Vuex store: https://github.com/quasarframework/quasar-framework.org/blob/dev/source/guide/ssr-writing-universal-code.md
Question 3 --> https://github.com/quasarframework/quasar-framework.org/blob/dev/source/guide/ssr-deploying.md

No More Posting New Topics!

Quasar & Quasar CLI v0.17 aka SSR - Developer Preview

Question 1:

Question 2:

Question 3: