This is actually possible. If there is a better way to do this, somebody please let me know.

I put all of the files/folders in /src/rootFolder/ and this moves all of those during dev/build to the / folder when it builds or runs the dev server.

quasar.conf.js , require copy-webpack-plugin up top, then add a line to build.extendWebpack

const CopyWebpackPlugin = require('copy-webpack-plugin');
/// ...
extendWebpack(cfg) {
   cfg.plugins.push(new CopyWebpackPlugin([{ from: 'src/rootFolder/', to: '' }]));
  /// ...
}

v1.14.5 has been released to fix the “no css” issue.

@rstoenescu I’m not sure what may have triggered it, but when I upgrade to v1.14.4, quasar dev / quasar build compiles me an empty quasar.sass ( /* top comment only */ ), so I end up with completely unstyled components. Updating package.json to pin “quasar”: “1.14.3” and install fixes the issue… pin it back to “1.14.4” and no css again.

Pkg quasar… v1.14.4
Pkg @quasar/app… v2.1.7

Pkg quasar… v1.14.3
Pkg @quasar/app… v2.1.7

Just curious if anyone else is attending. I’d love to meet up and say hi, have someone else there to hang out with.

This is actually possible. If there is a better way to do this, somebody please let me know.

I put all of the files/folders in /src/rootFolder/ and this moves all of those during dev/build to the / folder when it builds or runs the dev server.

quasar.conf.js , require copy-webpack-plugin up top, then add a line to build.extendWebpack

const CopyWebpackPlugin = require('copy-webpack-plugin');
/// ...
extendWebpack(cfg) {
   cfg.plugins.push(new CopyWebpackPlugin([{ from: 'src/rootFolder/', to: '' }]));
  /// ...
}

Awesome. Thank you for all the hard work in making Quasar possible. It’s much appreciated.