I figured it out. I tried setting the <meta tags, but it never works.
It seems the issue is with the server setting cache headings. I made a change to the nginx sites-available file:

    location / {
            try_files $uri $uri/ =404;
            add_header Cache-Control "no-store, no-cache, must-revalidate";
    }

    location /static {
            expires 30d;
            add_header Cache-Control "public";
            access_log off;
    }

Thanks for your reply, but we don’t need PWA currently. anyone else have any ideas?

Hi there,

First of all, thank you very much for creating such an amazing framework! I deployed an awesome website, and I am having a lot of fun with it.

I have a question: Whenever I publish a new version of the site, the users still see the old site because it is cached in their browser.

Is there a way to instruct quasar to create version numbers when referencing each chunk file (i.e. chunk.js?v=###hash). This usually forces the browser to reload the resources. I know each chunk is named with a hash, but somehow this doesn’t force chrome to reload resources (I have to tell users to CTRL+F5).

I searched the form for this solution, but the answers were from 2017, and don’t apply.

Thanks!!
Pavel

@s-molinari Thanks for your help. I think I may have to rewrite the module that doesn’t work on IE11. It may be they are using a non-standard polyfill.

Doesn’t quasar compile all javascript into chunks, minify it, etc… I would imagine it runs polyfills on it. I am having trouble understanding how that particular import gets excluded. Am I missing something? If so, there must be a way of including it in the polyfills.

Thanks!

I removed the gauth boot file (the issue was with vue-google-oauth2) and it works!! thanks!

it required some fiddling to get it to look right on IE, for example col doesn’t work well.

This is the contents of my gauth.js boot file:

import GAuth from ‘vue-google-oauth2’
import Vue from ‘vue’
import config from ‘@/config/config.js’

const { gauthOption } = config.auth
// gauthOption.access_type = ‘offline’
gauthOption.scope = ‘profile email’
gauthOption.prompt = ‘select_account’
Vue.use(GAuth, gauthOption)

do you know how I can add it to the babel-polyfills that quasar uses? Or do I manually have to import polyfills and get it done?

Thanks!

Hi s.molinari,
thanks for your reply. router boot file is my check if user is authenticated.
So in router mappings I would have:
{ name: ‘groupAdmin’, path: ‘/admin/groupadmin’, component: () => import(‘pages/admin/GroupAdmin.vue’), meta: { private: true, admin: true } }

Here is the gist:
https://gist.github.com/apavel3458/c3b24daf037d0650df137a8894b6e8e0

It’s not very important since the more important check happens on server-side using the JWT token.
Let me know if you do this differently…

Hi there, thanks for your reply.
You are right, I meant quasar.conf.js
Here is the GIST:

https://gist.github.com/apavel3458/a0dcd6ea54029d17a8e63a0cb7df71f1

The IE11 just shows a blank page.
Thanks! looking forward to your thoughts.

Hi there,
I deployed a quasar app with the supportIE: true flag in quasar.dev, but it doesn’t run on IE11.
https://log.cardioguide.ca/ is the app.

Here is the error: SCRIPT1002: Syntax Error

Looking at the source on IE11, it doesn’t appear polyfills are employed… ?

Any thoughts on how I can fix this?
Thanks!
Pavel

@metalsadman that works well! I didn’t realize I should use the pagination object.

Awesome, thanks so much for your help, I really appreciate it.