I found that I did not need to use this method.
Posts made by jmpmcmanus
-
RE: quasar and webpack-bundle-tracker
-
RE: popup-proxy window size
I found that if I used page container with the following style <q-page-container style=“padding: 0px;” > that it removed the unwanted space in the popup-proxy, making this method feasible.
-
popup-proxy window size
Is there a way to increase the popup-proxy window size? I’ve tried using window-height and full-height in a css class but have not had success in getting it to work. I’ve had success in increasing the size of the window by putting what I am displaying in a <q-page-container> and <q-page> container, but this method results in a window that is to large, and I have had difficulty in adjusting its size as well.
Jim
-
quasar and webpack-bundle-tracker
I’m trying to use webpack-bundle-tracker with quasar. I use extendWebpack, in my quasar.conf.js file, to run BundleTracker, which works (shown below). But the file it produces does not contain the publicPath I set in quasar.conf.js. webpack-bundle-tracker works with vue and the normal webpack config files. Has anybody tried using webpack-bundle-tracker with quasar, and found a solution?
extendWebpack (cfg) {
cfg.plugins.push(
new BundleTracker({filename: ‘…/webpack-stats.json’})
),
cfg.module.rules.push({
enforce: ‘pre’,
test: /.(js|vue)$/,
loader: ‘eslint-loader’,
exclude: /node_modules/,
options: {
formatter: require(‘eslint’).CLIEngine.getFormatter(‘stylish’)
}
})
}