fix(devserver) Remove "prod" requirement for using publicPath

[EEParker]

This PR allows publicPath and the base tag to work on dev builds. It is used in conjunction with webpackDevServer publicPath.

What kind of change does this PR introduce? (check at least one)

• Bugfix
• Feature
• Documentation
• Code style update
• Refactor
• Build-related changes
• Other, please describe:

Does this PR introduce a breaking change? (check one)

• Yes
• No

Fixes #4840, #4687

quasar.conf.js

    build: {
      publicPath: '/path/to/app1/', 
      forceDevPublicPath: true, // this allows publicPath to work in dev and prod builds
      vueRouterMode: 'history',
    },

    devServer: {
      publicPath: '/app1/', // this can match the publicPath from above or be part of the subpath. If using a proxy, set it to match.
    },

[hawkeye64]

@EEParker I don't believe they shouild match. Very rarely does a developer computer match the same set up as a production server.

[EEParker]

@hawkeye64 perhaps not, and in my test case with aspdotnet I am using different paths. However, within my test project where quasar is a "child" application, the base tag does needs to match what aspdotnet expects the route to be to work. This patch allows it to work in development and hmr to function.

[hawkeye64]

@EEParker I am just saying don't assume they should match. Based on this:

// this should match the publicPath from above

[rstoenescu]

Hi @EEParker ,

Thanks for contributing!

I cannot merge this as it would break some Quasar modes. However, what we could do is setup a new Boolean flag under quasar.conf.js > build, name it "forceDevPublicPath", then scenarios like yours can be covered too.

I'm just wondering over the very large implications of this. Were you able to test the changes in this PR? Need help getting you up to speed on testing CLI changes?

Also, would need some doc updates for the new flag. Again, I can show you quickly how to do it (ping me on Discord) -- if this is unclear how to do. Should be a 1-2 minute thing to add this to docs.

[EEParker]

@rstoenescu Thanks for the feedback. I did test spa and pwa modes, however I did not test Electron or Cordova builds or really consider the implications. Your suggestion of a forceDevPublicPath would work for the use case I was targeting. In fact it sounds like it would effectively accomplish what is proposed by #4840. I will work on a PR for the flag and docs.

[EEParker]

I switched the logic here to match L478.

[rstoenescu]

Merged it and pushed a subsequent commit to bulletproofed it.

@EEParker Thanks for starting this and taking time for it for a PR! Much appreciate it.
Will be available in quasar/app 1.0.6 shortly.