Hi @CristalT,
The way I have managed to successfully add my “plugins” is using the boot files, quasar’s boot files.
in quasar.conf.js my boot is loaded in such:

    boot: [
      { path: "axios" },
      { path: "i18n", server: false },
      { path: "bootstrap" , server: false},
      { path: "api", server: false },
      { path: "hello" , server: false},
      { path: "init-waelio" , server: false},
    ],

for example my bootstrap.js file looks as such:

import { Config, Storage, Note } from "src/plugins";

export default async ({ app, store, Vue }) => {

  Vue.prototype.$storage = Storage;
  app.storage = Storage;
  store.$storage = Storage;

  Vue.prototype.$config = Config;
  store.$config = Config;
  app.config = Config;

  Vue.prototype.$note = Note;
  app.note = Note;
  store.$note = Note;

  return;
};

export { Storage, Config, Note };

Maybe its more than what you need, but it is a working example
Good luck

So that means that storing values using $q.localStorage with winder them inaccessible for others using window.localstorage.getItem ?

@stukki Amazing!! I was stuck and now I am not. Thank you for sharing. This ought to be the number 1 question

I am having same issue.
The only thing I can suggest to help with the setup is sharing a link from Amplify https://aws.amazon.com/blogs/mobile/ssr-support-for-aws-amplify-javascript-libraries/
This might not solve the problem but it is a good start.
Please let me/us know if you can figure it out. I am stuck too

Hey! I already created my sitemap and have it copied to my dist folder under pwa, but it is not accessible by routing to https://mydomain/sitemap.xml
Where do I have to place it to make accessible?

@smellydogcoding The best way to insure that your boot file gets loaded in the right place such as Client/Server is in the Boot Section in your quasar.conf.js

boot: [“i18n”, “axios”, { path: “hello”, server: false }]

Read more … https://quasar.dev/quasar-cli/developing-ssr/configuring-ssr#Boot-Files