@beets thanks for the input will try and report back

If someone can point me to the right place where to configure so that I can serve the js and css files from a static URL.
To elaborate
Once I build my app and deploy on server
website a.com and b.com can both access it. Here for e.g., Any js or CSS file will be served as ‘a.com/3edhf56.js’ or ‘b.com/3edhf56.js’ this duplicates the assets and CDN cost increases, if I can set these assets with ‘assests.c.com/3edhf56.js’ for both a.com and b.com it would be helpful. Any help on where I can make such a configuration?

Thanks

I usually build for prod locally using

quasar build -m ssr

I just noticed a bug where some old configuration ( some old constant values) still present in the final build output. I could not reproduce the issue locally as it happens only in the prod server. I found that the terser cache is not clear and had been stale for many builds e.g. paths

node_modules/.cache/terser-webpack-plugin/content-v2/sha512/57/35/70a7c3ce0b9687dd572f83d6adf9c46a9107ff7c13ac4f514a9caeeacfd397f61169b8d91eb989142a33c84dbe6307997b5c75ba9c45bdd5584ec7a331a6

Finally found out using grep that these files contained stale data and somehow become part of the build. I fixed my issue by clearing node modules folder. Want to know if this is common or we can do something to clear this on new builds.

Thanks

Re: How can I remove the default CSS?

I currently use quasar but not a lot of quasar component, still the bundled css is too much, any way to reduce that? I would greatly benefit my production performance.
I searched the forum but not find any concrete solutions, please point me in the right direction.

I too used this, but faced many issues of css getting deleted. so I would ask you to double-check if the css was purged if you face UI issues. I know I was not doing it right but just my experience.

if you have async methods, you can return a promise which resolves once your methods are run. as you can see in the redirect example, i believe that prefetch does not require any return value and still works.

just my opinion from working, i feel it better to always not have console log, statement even in dev, i use them to only identify any problems.

does it have something to do with this functions in meta.js?

function bodyFilter (name) {
  return ['class', 'style'].includes(name) === false
}

@s-molinari yes, i am using it throughout my app, only the style element seems to not work

I tried using meta like this

 style: {
          test: {
            innerHtml: `border: 10px solid #000`,
          },
        },

this does not seem to work, but the meta plugin docs say one should be able to add/remove/change <style> and <script> tags.
Am i doing something wrong here?