@rjp Did you finally was able to compile a web component with Vue + Quasar embedded inside ? The closest I’ve been (with not success, unfortunately) was following this link instructions:
https://medium.com/@juanignaciogarzon/creating-a-web-component-with-vue-quasar-188007ec999e

@metalsadman thanks so much for upgrading your example. Questions:
1.- After launch quasar build, what folder should we use as entry point for our web server ? Here we are trying to keep both project togeter and maybe due to Laravel Views now support html as a file type in v5.8.18 ( https://github.com/laravel/framework/pull/28541 ) we can take advantages from this.

2.- In your quasar.conf filee, after detecting we are in prod env, can you please explain why do you use this lines:

cfg.plugins.push(new CopyWebpackPlugin([{
            from: path.resolve(__dirname, 'public_files'),
            to: ''
          }]))

I know this is not the best example, and again, frontend app (and repo) should be separated from API, but I guess this is the main point for the thread.

I suppose that the original question by @lucasfernog is not answered yet. Many workarounds are provided, because other users stands that having separated projects seems to be a better approach. What if we want to perform tests using laravel-dusk ? Having separated projects will make it work ? Thanks in advance for your time.