title: How to integrate inertiaJS with quasar framework?
body: <p>I would like to integrate intertiaJS into my Quasar app so that I can communicate with my Laravel backend. My problem now is that the general stuff is taken over by the Quasar CLI, which is good in principle, but in this case it takes away my entry point as described at <a href="https://inertiajs.com/client-side-setup" rel="nofollow noreferrer">https://inertiajs.com/client-side-setup</a>:</p>
  <pre class="lang-js prettyprint-override"><code>import { createApp, h } from 'vue'
  import { App, plugin } from '@inertiajs/inertia-vue3'
  
  const el = document.getElementById('app')
  
  createApp({
    render: () =&gt; h(App, {
      initialPage: JSON.parse(el.dataset.page),
      resolveComponent: name =&gt; require(`./Pages/${name}`).default,
    })
  }).use(plugin).mount(el)
  </code></pre>
  <p>My thought is that I could use a boot file like the offered in Quasar (<a href="https://quasar.dev/quasar-cli/boot-files" rel="nofollow noreferrer">https://quasar.dev/quasar-cli/boot-files</a>), but I have to admit that I don't have the right approach.
  When I look at the app.js that is automatically generated, I see that nothing special happens in the rendering:</p>
  <pre class="lang-js prettyprint-override"><code>/**
   * THIS FILE IS GENERATED AUTOMATICALLY.
   * DO NOT EDIT.
   *
   * You are probably looking on adding startup/initialization code.
   * Use &quot;quasar new boot &lt;name&gt;&quot; and add it there.
   * One boot file per concern. Then reference the file(s) in quasar.conf.js &gt; boot:
   * boot: ['file', ...] // do not add &quot;.js&quot; extension to it.
   *
   * Boot files are your &quot;main.js&quot;
   **/
  import Vue from 'vue'
  import './import-quasar.js'
  
  import App from 'app/src/App.vue'
  
  import createStore from 'app/src/store/index'
  
  import createRouter from 'app/src/router/index'
  
  export default async function () {
    // create store and router instances
    
    const store = typeof createStore === 'function'
      ? await createStore({Vue})
      : createStore
    
    const router = typeof createRouter === 'function'
      ? await createRouter({Vue, store})
      : createRouter
    
    // make router instance available in store
    store.$router = router
    
  
    // Create the app instantiation Object.
    // Here we inject the router, store to all child components,
    // making them available everywhere as `this.$router` and `this.$store`.
    const app = {
      router,
      store,
      render: h =&gt; h(App)
    }
  
    app.el = '#q-app'
    
    // expose the app, the router and the store.
    // note we are not mounting the app here, since bootstrapping will be
    // different depending on whether we are in a browser or on the server.
    return {
      app,
      store,
      router
    }
  }
  
  </code></pre>
  <p>I.e. in principle I should be able to link in without it causing any conflict situations. The question is, how would that look?</p>
  <p>I have to link into the rendering afterwards and overwrite it as described in the code example. I would like to stay with the Quasar Cli, because it is very useful and the situation described here is the only exception.</p>
  <p>p7</p>