Hi,

We have our quasar production builds scripted and the progress bar output on the console is intermixing with other outputs from the builds…

Is it possible to turn off the progress bar during builds?

I found articles on using ‘no-progress’ with the npm outputs and I tried

quasar build --no-progress

but that didn’t appear to work…

Thanks…

It’s been awhile…was just wondering if anyone has any ideas on this? We are doing our builds in parallel and the output of the quasar/npm build is interlacing with other output during the build…we’d like to either turn off all the output altogether or just the progress output.

Thanks…

Hi,

We’d like to pass in the ‘buildDir’ and ‘showProgress’ values from the commandline into the build section of quasar.conf.js

For example,

We’d like to do this:

WEB_BUILD_DIR=/someBuildDir
WEB_BUILD_SHOW_PROGRESS=false

and then run quasar build and have it NOT show the progress bar and build to the output directory we specify.

AND… if either of those values are not present then default to their default values.

I’m tried this in the build section of quasar.conf.js and I have partial luck. I don’t know how to tell the script to use default values IF those. values are not present on the command line or process.env. Javascript/Web UI isn’t my strong point. I’m a backend developer by trade.

// quasar.conf.js

{

build: {
      distDir: process.env.WEB_BUILD_DIR,
      showProgress: process.env.WEB_BUILD_SHOW_PROGRESS,
      scopeHoisting: true,
     ... // rest of config
    },
}

Thanks…

It’s been awhile…was just wondering if anyone has any ideas on this? We are doing our builds in parallel and the output of the quasar/npm build is interlacing with other output during the build…we’d like to either turn off all the output altogether or just the progress output.

Thanks…

Hi,

We have our quasar production builds scripted and the progress bar output on the console is intermixing with other outputs from the builds…

Is it possible to turn off the progress bar during builds?

I found articles on using ‘no-progress’ with the npm outputs and I tried

quasar build --no-progress

but that didn’t appear to work…

Thanks…

Hi,

Is it possible to force/require a selection be made in a q-select? I’d like to make sure a user selects a value from the dropdown and throw an error if they don’t…

I was thinking something like what the input fields support in terms of validation already.

I could add a entry in my options something like “Choose…” and use that as the default/initial value and then would like to make sure they pick something other than that word.

Thanks…

Hi,

Is it possible to change the color of the default icons used on the Input fields when the ‘clearable’ attribute it set?
I didn’t see any property to let me do that…

I know I can use a custom icon and mimic the same behaviour and color I want but I have a bunch of fields I’d like to apply the look and feel to without having to copy and paste.

Thanks,

• Tim