@metalsadman sorry for that.

i found my mistake that i was not using meta tag view port

<meta name=“viewport”
content=“user-scalable=no, initial-scale=1, maximum-scale=1, minimum-scale=1, width=device-width<% if (htmlWebpackPlugin.options.ctx.mode.cordova) { %>, viewport-fit=cover<% } %>”>

https://quizzical-elion-736a43.netlify.com/

Follow the above link and open chrome dev tools to select mobile screen size.You will notice shrinking of everything.What i am doing wrong?

Instead of writing components required manually, can we tree shake framework:‘all’ at build time ?

Any comments on this?

@cata-orellana said in Firebase Push notification not working in quasar framework n Vue.js:

So, the only way is modifying the firebase node_module?
How can you handle that in different environments and buildings, nodes modules are installed each time a build is made with continuos integration strategy.

I would also like to know the solution in said case.

i would like to close expansion item programatically, but don’t know how to use below method.

https://v1.quasar-framework.org/vue-components/expansion-item
QExpansionItem API

show ([evt]) => void 0

Its common to have ‘export’ and ‘print’ table data. This is missing feature in q-table, can we have it?

I think workbox can not minify output service worker itself. Can we achieve this by quasar build command?

/node_modules/@firebase/messaging/dist/index.cjs.js

You will find index.esm.js, index.cjs.js.map and index.esm.js.map also at above location.Total 4 files.

var DEFAULT_SW_PATH = ‘/service-worker.js’;
var DEFAULT_SW_SCOPE = ‘/’;

Do above two changes wherever you find DEFAULT_SW_PATH and DEFAULT_SW_SCOPE
then build again, everything will work fine.